chap007 (1)

chap007 (1) - Sample Use-Case Model Diagram Basic Use-Case...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
Sample Use-Case Model Diagram
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Basic Use-Case Symbols Use case – subset of the overall system functionality Represented graphically by a horizontal ellipse with the name of the use case appearing above, below, or inside the ellipse. Actor – anything that needs to interact with the system to exchange information. Could be a human, an organization, another information system, an external device, or even time. Temporal event – a system event triggered by time. The actor is time.
Background image of page 2
Four Types of Actors Primary business actor The stakeholder that primarily benefits from the execution of the use case. e.g. the employee receiving the paycheck Primary system actor The stakeholder that directly interfaces with the system to initiate or trigger the business or system event. e.g. the bank teller entering deposit information External server actor The stakeholder that responds to a request from the use case. e.g. the credit bureau authorizing a credit card charge External receiver actor The stakeholder that is not the primary actor but receives something of value from the use case. e.g. the warehouse receiving a packing slip
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Use Case Association Relationship Association – a relationship between an actor and a use case in which an interaction occurs between them. Association modeled as a solid line connecting the actor and the use case. Association with an arrowhead touching the use case indicates that the use case was initiated by the actor. Association lacking arrowhead indicates a receiver actor. Associations may be bidirectional or unidirectional.
Background image of page 4
Use Case Extends Relationship Extension use case – a use case consisting of steps extracted from a more complex use case in order to simplify the original
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/22/2010 for the course ISOM 313 taught by Professor Mee during the Fall '10 term at Suffolk.

Page1 / 20

chap007 (1) - Sample Use-Case Model Diagram Basic Use-Case...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online