Creately

Home diagrams

Sequence Diagram Tutorial: Complete Guide with Examples

27 January 2017

This sequence diagram tutorial is to help you understand sequence diagrams better; to explain
everything you need to know from how to draw a sequence diagram to the common mistakes you
should avoid when drawing one.

There are 3 types of Interaction diagrams; Sequence diagrams, communication diagrams, and timing
diagrams. These diagrams are used to illustrate interactions between parts within a system. Among the
three, sequence diagrams are preferred by both developers and readers alike for their simplicity.

In this sequence diagram tutorial you will learn about;

What is a Sequence Diagram

Sequence Diagram Notations

Sequence Diagram Best Practices

How to Draw a Sequence Diagram

Sequence Diagram Common Mistakes

Sequence Diagram Templates and Examples

Sequence Diagram SlideShare Presentation

Feedback on the Sequence Diagram Guide

What is a Sequence Diagram?

Sequence diagrams, commonly used by developers, model the interactions between objects in a single
use case. They illustrate how the different parts of a system interact with each other to carry out a
function, and the order in which the interactions occur when a particular use case is executed.

In simpler words, a sequence diagram shows different parts of a system work in a sequence to get
something done.

Sequence Diagram Notations

A sequence diagram is structured in such a way that it represents a timeline which begins at the top and
descends gradually to mark the sequence of interactions. Each object has a column and the messages
exchanged between them are represented by arrows.

A Quick Overview of the Various Parts of a Sequence Diagram

Lifeline Notation

Sequence diagram - LifelineA sequence diagram is made up of several of these lifeline notations that
should be arranged horizontally across the top of the diagram. No two lifeline notations should overlap
each other. They represent the different objects or parts that interact with each other in the system
during the sequence.

A lifeline notation with an actor element symbol is used when the particular sequence diagram is owned
by a use case.

lifeline with an actor element symbolActivation Bars

Activation bar is the box placed on the lifeline. It is used to indicate that an object is active (or
instantiated) during an interaction between two objects. The length of the rectangle indicates the
duration of the objects staying active.
In a sequence diagram, an interaction between two objects occurs when one object sends a message to
another. The use of the activation bar on the lifelines of the Message Caller (the object that sends the
message) and the Message Receiver (the object that receives the message) indicates that both are
active/is instantiated during the exchange of the message.

Sequence Diagram - Activation Bars

Message Arrows

An arrow from the Message Caller to the Message Receiver specifies a message in a sequence diagram.
A message can flow in any direction; from left to right, right to left or back to the Message Caller itself.
While you can describe the message being sent from one object to the other on the arrow, with different
arrowheads you can indicate the type of message being sent or received.

The message arrow comes with a description, which is known as a message signature, on it. The format
for this message signature is below. All parts except the message_name is optional.

attribute = message_name (arguments): return_type

Synchronous message

As shown in the activation bars example, a synchronous message is used when the sender waits for the
receiver to process the message and return before carrying on with another message. The arrow head
used to indicate this type of message is a solid one, like the one below.

Synchronous Message Arrow

Asynchronous message
An asynchronous message is used when the message caller does not wait for the receiver to process the
message and return before sending other messages to other objects within the system. The arrow head
used to show this type of message is a line arrow like shown in the example below.

Asynchronous Message example

Return message

A return message is used to indicate that the message receiver is done processing the message and is
returning control over to the message caller. Return messages are optional notation pieces, for an
activation bar that is triggered by a synchronous message always implies a return message.

Tip: You can avoid cluttering up your diagrams by minimizing the use of return messages since the return
value can be specified in the initial message arrow itself.

Return Message Example

Participant creation message

Objects do not necessarily live for the entire duration of the sequence of events. Objects or participants
can be created according to the message that is being sent.

The dropped participant box notation can be used when you need to show that the particular participant
did not exist until the create call was sent. If the created participant does something immediately after
its creation, you should add an activation box right below the participant box.

Participant creation example

Participant destruction message

Likewise, participants when no longer needed can also be deleted from a sequence diagram. This is done
by adding an X at the end of the lifeline of the said participant. Participation Destruction Message
Reflexive message

When an object sends a message to itself, it is called a reflexive message. It is indicated with a message
arrow that starts and ends at the same lifeline like shown in the example below.

Reflexive message

Comment

UML diagrams generally permit the annotation of comments in all UML diagram types. The comment
object is a rectangle with a folded-over corner as shown below. The comment can be linked to the
related object with a dashed line.

Comment object example

Note: View Sequence Diagram Best Practices to learn about sequence fragments.

Sequence Diagram Best Practices

Manage complex interactions with sequence fragments

A sequence fragment is represented as a box that frames a section of interactions between objects (as
shown in the examples below) in a sequence diagram.

It is used to show complex interactions such as alternative flows and loops in a more structured way. On
the top left corner of the fragment sits an operator. This the fragment operator specifies what sort of
a fragment it is.

Alternatives
The alternative combination fragment is used when a choice needs to be made between two or more
message sequences. It models the if then else logic.

The alternative fragment is represented by a large rectangle or a frame; it is specified by mentioning alt
inside the frames name box (a.k.a. fragment operator).

To show two or more alternatives, the larger rectangle is then divided into what is called interaction
operands using a dashed line, like shown in the sequence diagram example above. Each operand has a
guard to test against and it is placed at the top left corner of the operand.

Alternative fragment example - sequence diagram tutorial

Options

The option combination fragment is used to indicate a sequence that will only occur under a certain
condition, otherwise, the sequence wont occur. It models the if then statement.

Similar to the alternative fragment, the option fragment is also represented with a rectangular frame
where opt is placed inside the name box.

Unlike the alternative fragment, an option fragment is not divided into two or more operands. Options
guard is placed at the top left corner.

(Find an example sequence diagram with an option fragment in the Sequence Diagram Templates and
Examples section).

Loops
Loop fragment is used to represent a repetitive sequence. Place the words loop in the name box and
the guard condition near the top left corner of the frame.

In addition to the Boolean test, the guard in a loop fragment can have two other special conditions
tested against. These are minimum iterations (written as minint = [the number] and maximum iterations
(written as maxint = [the number]).

If it is a minimum iterations guard, the loop must execute not less than the number mentioned, and if it
is a maximum iterations guard, the loop mustnt execute more than the number indicated.

(Find an example of a loop fragment below in the sequence diagram templates and example section)

Reference Fragment

You can use the ref fragment to manage the size of large sequence diagrams. It allows you to reuse part
of one sequence diagram in another, or in other words, you can reference part of a diagram in another
diagram using the ref fragment.

To specify the reference fragment, you have to mention ref in the name box of the frame and the name
of the sequence diagram that is being referred to inside the frame.

Reference fragment example

For more sequence fragments refer to Beyond the Basics of Sequence Diagrams: Part 1, Part 2 and Part
3.

Draw smaller sequence diagrams that capture the essence of the use case
Instead of cluttering your sequence diagram with several objects and groups of messages that will
confuse the reader, draw a few smaller sequence diagrams that aptly explain what your system does.
Make sure that the diagram fits on a single page and leaves space for explanatory notes too.

Also instead of drawing dozens of sequence diagrams, find out what is common among the scenarios
and focus on that. And if the code is expressive and can stand on its own, theres no need to draw a
sequence diagram in the first place.

How to Draw a Sequence Diagram

A sequence diagram represents the scenario or flow of events in one single use case. The message flow
of the sequence diagram is based on the narrative of the particular use case.

Then, before you start drawing the sequence diagram or decide what interactions should be included in
it, you need to draw the use case diagram and ready a comprehensive description of what the particular
use case does.

How to Draw a Sequence Diagram A sequence diagram represents the scenario or flow of events in one
single use case. The message flow of the sequence diagram is based on the narrative of the particular
use case. Then, before you start drawing the sequence diagram or decide what interactions should be
included in it, you need to ready a comprehensive description of what the particular use case does.

From the above use case diagram example of Create New Online Library Account, we will focus on the
use case named Create New User Account to draw our sequence diagram example.

Before drawing the sequence diagram, its necessary to identify the objects or actors that would be
involved in creating a new user account. These would be;

Librarian

Online Library Management system

User credentials database

Email system

Once you identify the objects, it is then important to write a detailed description on what the use case
does. From this description, you can easily figure out the interactions (that should go in the sequence
diagram) that would occur between the objects above, once the use case is executed.

Here are the steps that occur in the use case named Create New Library User Account.

The librarian request the system to create a new online library account

The librarian then selects the library user account type

The librarian enters the users details

The users details are checked using the user Credentials Database

The new library user account is created

A summary of the of the new accounts details are then emailed to the user

From each of these steps, you can easily specify what messages should be exchanged between the
objects in the sequence diagram. Once its clear, you can go ahead and start drawing the sequence
diagram.

The sequence diagram below shows how the objects in the online library management system interact
with each other to perform the function Create New Library User Account.

How to draw a sequence diagram - sequence diagram tutorial

Sequence Diagram Common Mistakes

When drawing sequence diagrams, designers tend to make these common mistakes. By avoiding these
mistakes you can ensure the quality of your diagram.
Adding too much detail. This clutters up the diagram and makes it difficult to read.

Obsolete and out of date sequence diagrams that are irrelevant when compared to the interfaces, actual
architectures etc. of the system. Dont forget to replace them or modify them.

Leaving no blank space between the use case text and the message arrow; this makes it difficult for
anyone to read the diagram.

Not considering the origins of message arrows carefully.

See these common mistakes explained in detail in Sequence Diagram Guide: Common Mistakes to Avoid
When Drawing Sequence Diagrams.

Sequence Diagram Templates and examples

Following are a few sequence diagram templates and examples that are drawn using Creately. Create
sequence diagrams online using Createlys online tool. Click on the template to open it in the editor.

Sequence Diagram of an Online Exam System

Online Examination - Sequence Diagram Template

Click the image to edit it online

Sequence Diagram Example of a School Management System

School Management System - Sequence Diagram Template

Example of an Option Combination Fragment

Example of an option fragment

Example of a Loop Sequence

Loops - Sequence Diagram Example

Here are some more sequence diagram templates and examples that you can edit right away.

Sequence Diagram Tutorial SlideShare Presentation

Sequence diagram guide Power Point (PPT) from Creately

Feedback on the Sequence Diagram Tutorial

This sequence diagram tutorial covers everything you need to know on sequence diagrams and drawing
them. If you have any suggestions or questions regarding the sequence diagram tutorial, feel free to
leave a comment.

More Diagram Tutorials

Business Process Modeling Tutorial (BPM Guide Explaining Features)

Ultimate Flowchart Guide ( Complete Flowchart Tutorial with Examples )

Use Case Diagram Tutorial ( Guide with Examples )

sequence diagram examples sequence diagram guide sequence diagram tutorial sequence diagrams

More related articles

Sequence Diagram Templates to Instantly View Object Interactions

ER Diagram Template

Ultimate Guide to ER Diagrams ( Entity Relationship Diagrams )

Use Case Diagram Tutorial ( Guide with Examples )

Author

Amanda

Amanda Athuraliya is the communication specialist/content writer at Cinergix, the team behind the
development of the online diagramming tool, Creately. She is an avid reader, a budding writer and a
passionate researcher who loves to write about all kinds of topics.

View all posts by Amanda

Comments

Tuges

thank you for putting the effort into this tutorial. You are helping so many such as me. God bless you and
your work..

16.08.2017 - reply

Mehwish Mehak

This is a complete and easy to understand article, thanks for such an awesome information and cleaver
delivery. <3 <3

25.06.2017 - reply

Akila Gardiye
This is a very clear tutorial with simple examples . I started viewing this blog not having a clue about
sequence diagrams and now im leaving with the knowledge of what it actually is and on how to draw
one. Thank you for such a good tutorial !!

13.04.2017 - reply

kasun

Admire the work..a great job

13.04.2017 - reply

Mier

Clear tutorial. Thanks!

07.03.2017 - reply

Leave a Comment

Confirm you are NOT a spammer

Notify me of replies to my comment

This blog uses premium CommentLuv which allows you to put your keywords with your name if you have
had 9 approved comments. Use your real name and then @ your keywords (maximum of 3)

Home

Plans

Features
Examples

Community

About

Cinergix Pvt. Ltd 2017 | All Rights Reserved