System Sequence Diagrams
System Sequence Diagrams
System Sequence Diagrams
Sequence Diagram
Sequence Diagrams depict the objects and classes involved in the scenario and the
sequence of messages exchanged between the objects needed to carry out the
functionality of the system.
Sequence diagrams can be used to drive out testable user interface requirements.
IT310-OOAD Page 1
IT310- OBJECT ORIENTED ANALYSIS AND DESIGN
System Sequence Diagrams should be done for the main success scenario of the use-case,
and frequent and alternative scenarios.
Notations
Object:
Objects are instances of classes. Object is represented as a rectangle which contains the
name of the object underlined.
Because the system is instantiated, it is shown as an object.
:Object1
Actor: An Actor is modeled using the ubiquitous symbol, the stick figure.
actor 1
Lifeline: The LifeLine identifies the existence of the object over time. The notation for a
Lifeline is a vertical dotted line extending from an object.
Examples of SSD
Following example shows the success scenario of the Process Sale use case.
IT310-OOAD Page 2
IT310- OBJECT ORIENTED ANALYSIS AND DESIGN
Events generated by cashier (actor)-
makeNewSale, enterItem, endSale and makePayment.
IT310-OOAD Page 3
IT310- OBJECT ORIENTED ANALYSIS AND DESIGN
IT310-OOAD Page 4