Scribd
Upload
68 views

Sequence Diagram August 15, 2017: Objective

The document describes the components and purpose of a sequence diagram for modeling an ATM system. A sequence diagram captures the time-ordered flow of messages between objects to visualize system interactions and validate scenarios. The key components include object lifelines, activation boxes, messages, and notation for different message types like synchronous, asynchronous, reply and self-messages. Sequence diagrams are useful for modeling dynamic system behavior, describing message flows and structural organization of objects, and understanding interactions between objects.

Uploaded by

sanober shahin
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
68 views

Sequence Diagram August 15, 2017: Objective

The document describes the components and purpose of a sequence diagram for modeling an ATM system. A sequence diagram captures the time-ordered flow of messages between objects to visualize system interactions and validate scenarios. The key components include object lifelines, activation boxes, messages, and notation for different message types like synchronous, asynchronous, reply and self-messages. Sequence diagrams are useful for modeling dynamic system behavior, describing message flows and structural organization of objects, and understanding interactions between objects.

Uploaded by

sanober shahin
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Sequence Diagram August 15, 2017

OBJECTIVE:
Generate a Sequence Diagram for ATM System.

DESCRIPTION:
We have two types of interaction diagrams in UML. One is sequence diagram and
the other is a collaboration diagram. The sequence diagram captures the time
sequence of message flow from one object to another and the collaboration
diagram describes the organization of objects in a system taking part in the
message flow.

Sequence diagrams describe interactions among classes in terms of an exchange of


messages over time. They're also called event diagrams. A sequence diagram is a
good way to visualize and validate various runtime scenarios. These can help to
predict how a system will behave and to discover responsibilities a class may need
to have in the process of modeling a new system.
So the following things are to identified clearly before drawing the interaction
diagram:

1. Objects taking part in the interaction.


2. Message flows among the objects.
3. The sequence in which the messages are flowing.
4. Object organization.

Purpose:
1. To capture dynamic behavior of a system.
2. To describe the message flow in the system.
3. To describe structural organization of the objects.
4. To describe interaction among objects.
Sequence Diagram August 15, 2017

Sequence Diagram Components


To understand what a sequence diagram is, you should be familiar with its
components. Sequence diagrams are made up of the following elements:

Class Roles or Participants or Object Symbol

Class roles describe the way an object will behave in context of the system. Use
the UML object symbol to illustrate class roles, but don't list object attributes.

Activation or Execution Occurrence


Activation boxes represent the time an object needs to complete a task. When an
object is busy executing a process or waiting for a reply message, use a thin gray
rectangle placed vertically on its lifeline.
Sequence Diagram August 15, 2017

Actor Symbol
Represented by a stick figure, actors are entities that are both interactive with and
external to the system.

Messages
Messages are arrows that represent communication between objects. Use half-
arrowed lines to represent asynchronous messages. Asynchronous messages are
sent from an object that will not wait for a response from the receiver before
continuing its tasks. For message types, see below
Sequence Diagram August 15, 2017

Lifelines
Lifelines are vertical dashed lines that indicate the object's presence over time.

Destroying Objects
Objects can be terminated early using an arrow labeled "<< destroy >>" that points
to an X. This object is removed from memory. When that object's lifeline ends, you
can place an X at the end of its lifeline to denote a destruction occurrence.
Sequence Diagram August 15, 2017
Loops
A repetition or loop within a sequence diagram is depicted as a rectangle. Place the
condition for exiting the loop at the bottom left corner in square brackets [ ].
Types of Messages in Sequence Diagrams:

Synchronous Message
A synchronous message requires a response before the interaction can continue. It's
usually drawn using a line with a solid arrowhead pointing from one object to
another.

Asynchronous Message
Asynchronous messages don't need a reply for interaction to continue. Like
synchronous messages, they are drawn with an arrow connecting two lifelines;
however, the arrowhead is usually open and there's no return message depicted.

Reply or Return Message


A reply message is drawn with a dotted line and an open arrowhead pointing back
to the original lifeline.

Self Message
A message an object sends to itself, usually shown as a U shaped arrow pointing
back to itself.
Sequence Diagram August 15, 2017
Create Message
This is a message that creates a new object. Similar to a return message, it's
depicted with a dashed line and an open arrowhead that points to the rectangle
representing the object created.

Delete Message
This is a message that destroys an object. It can be shown by an arrow with an x at
the end.

Found Message
A message sent from an unknown recipient, shown by an arrow from an endpoint
to a lifeline.

Lost Message
A message sent to an unknown recipient. It's shown by an arrow going from a
lifeline to an endpoint, a filled circle or an x.
Sequence Diagram August 15, 2017

You might also like