Professional Documents
Culture Documents
USECASE DIAGRAM
Introduction
The use case concept was introduced by Ivar Jacobson in the object oriented software engineering (OOSE) method A use case corresponds to a sequence of transactions, in which each transaction is invoked from outside the system (actors) and engages internal objects to interact with one another and systems surroundings
Introduction
Use-case diagram is a graph of actors, a set of use cases enclosed by a system boundary, communication (participation) associations between the actors and the use cases, and generalization among the use cases
Do research
Return a call Support representative Use case diagram shows the relationship among actors and use cases within a system
A use case is shown as an ellipse containing the name of the use case. The name of the use case can be placed below or inside the ellipse. Actors names and use case names should follow the capitalization and punctuation guidelines of the model An actor is shown as a class rectangle with the label <<actor>>, or the label and a stick figure or just the stick figure with name of the actor
<<actor>> Customer
These relationships are shown in a use-case diagram 1. Communication : The communication relationship of an actor in a use case is shown by connecting the actor symbol to the use case symbol with solid path. The actor is said to communicate with the use case. 2. Uses : A uses relationship between the use cases is shown by a generalization arrow from the use case 3. Extends : used when you have one use case that is similar to another but does a bit more i.e like a subclass
Caller
Exchange
Receiver
Talk
Telephone Call
Object Caller 1: OffHook 2: DialTone Exchange 4: RingTone Receiver 5: OffHook Talk 6:OnHook Message 3: DialNumber
Telephone Call
Object Caller 1:1 OffHook 2:1: DialTone Exchange 2.2: RingTone Receiver 3.1: OffHook Talk 4.1:OnHook Message 1.2: DialNumber
State is represented as a rounded box which may contain one or more compartments Compartments are optional The name compartment and the internal transition compartment are two such components :
Name compartment holds the optional name of the state. State without names are anonymous and are distinct Internal transition compartment holds a list of internal actions or activities performed in response to events received while the object is in state without changing states
Two special events : entry and exit which are reserved words Statechart support nested state mechine with keyword do
Idle
State
Dial
Entry and number.append(n)
digit(n)