SOEN 341
System sequence diagrams
http://en.wikipedia.org/wiki/System_sequence_di
agram
Definition
System sequence diagrams are visual summaries of the
individual use cases.
All systems are treated as a black box; the diagram places
emphasis on events that cross the system boundary from
actors to systems.
A system sequence diagram should be done for the main
success scenario of the use case, and frequent or complex
alternative scenarios.
A system sequence diagram should specify and show the
following:
External actors
Messages (methods) invoked by these actors
Return values (if any) associated with previous messages
Indication of any loops or iteration area
Example
System Level Sequence Diagrams
http://oldresources.visualparadigm.com/uml_diagrams/sequence_diagram/synchronization_between_system_level_sequence_diagram_and_
flow_of_event.html
Sequence diagram, the most common kind of interaction
diagram, focuses on the Message interchange between a
number of Lifelines.
System level sequence diagram is the high-level of sequence
diagram which illustrates the sequence of interactions
between the Use Case and the Actor who is the user of the
system.
The system level sequence diagram can be transformed from
the flow of events in the use case description.
Defining Flow of Events
Generating the Sequence
Diagram
Given the use case:
Use case to system
sequence
Modify if necessary
Update the use case