IS 401 System Sequence Diagram Flashcards
system sequence diagram (SSD)
is used to describe this flow of information into and out of the automated system. Thus, an SSD documents the inputs and the outputs and identifies the interaction between actors and the system.
An SSD is a type of interaction diagram.
.
stick figure
actor - a person (or role) that interacts with the system
the emphasis in an SSD is on how the actor “interacts” with the system by entering input data and receiving output data.
The box labeled :System is an object that represents
the entire automated system.
object notation
In SSDs and all other interaction diagrams, analysts use object notation instead of class notation. In object notation, a box refers to an individual object, not the class of all similar objects. The notation is simply a rectangle with the name of the object underlined. The colon before the underlined class name is a frequently used but optional part of the object notation. In an interaction diagram, the messages are sent and received by individual objects, not by a class. In an SSD, the only object included is one representing the entire system.
Underneath the actor and :System are vertical dashed lines called lifelines
A lifeline, or object lifeline, is simply the extension of that object—either actor or object—during the use case.
The arrows between the lifelines represent
the messages that are sent by the actor. Each arrow has an origin and a destination. The origin of the message is the actor or object that sends it, as indicated by the lifeline at the arrow’s tail.
Similarly, the destination actor or object of a message is indicated by the lifeline that is touched by the arrowhead. The purpose of lifelines is to indicate the sequence of the messages sent and received by the actor and object. The sequence of messages is read from top to bottom in the diagram.
A message is labeled
to describe its purpose and any input data being sent. The message name should follow the verb-noun syntax to make the purpose clear. The syntax of the message label has several options
In a sequence diagram, a message is an action that is invoked on the destination object, much like a command
A dashed arrow indicates
a response or an answer
Because it is a response, only the data that is sent on the response is noted
There is no message requesting a service—only the data being returned.
Solid arrow
The syntax is simply the name of the message followed by the input parameters in parentheses.
A note
can be added to any UML diagram to add explanations.
loop frame
In a smaller rectangle at the top of the frame is the descriptive text to control the behavior of the messages within the larger rectangle. The condition loop for all items indicates that the messages in the box repeat many times or are associated with many instances.
true/false condition
brackets
The asterisk (*) preceding the true/false condition indicates
that the message repeats as long as the true/false condition evaluates to true.
EX: *[another item]
Analysts use this abbreviated notation for several reasons
First, a message and the returned data can be shown in one step.
Second, the true/false condition is placed on the message itself