UML Sequence Diagram

Shahzaib Hassan, Atif Javeid, Fatima Sajjad

[email protected]

It gives high-level information about how a user should interact with the system. Class diagrams specify
the structure and the operations related to the data used by the system. A sequence diagram can help
specifying the link between a use case and the methods and classes defined in class diagram.

1. Introduction:
UML Stands for Unified Modeling Language. Unified Modelling Language (UML) is a modeling
language in the field of software engineering which aims to set standard ways to visualize the design of a
system. UML guides the creation of multiple types of diagrams such as interaction, structure and behavior
diagrams.

It is the general-purpose modeling language used to visualize the system. It is a graphical language that is
standard to the software industry for specifying, visualizing, constructing and documenting the artifacts of
the soft3ware systems [1].

A sequence diagram simply depicts interaction between objects in a sequential order i.e. the order in
which these interactions take place. These diagrams are widely used by businessmen and software
developers to document and understand requirements for new and existing systems.

UML has basically three building blocks:

• Thing: The basic building elements of model.

• Relationships - How the things are tied together.
• Diagrams - Graphical representation of element collection.[2]

UML Diagram Symbols

• + For public
• - For private
• # For protected
• / For derived
• ~ For package [3]

1
1.1. Importance:
Unified Modeling Language is used to specify, visualize, modify, construct and document the
artifacts of an object-oriented software-intensive system under development. During these different
diagrams are drawn according to need & the types of requirement. The need of this study is to find out
the importance of different diagrams (class, use-case, sequence, activity, component, deployment) during
software development. Whether all diagrams play vital role in s/w development or not; or we can focus on
specific diagrams rather than drawing all the diagrams.[2]

A complex enterprise application with many collaborators will require a solid foundation of planning
and clear, concise communication among team members as the project progresses. Visualizing user
interactions, processes, and the structure of the system you're trying to build will help save time down the
line and make sure everyone on the team is on the same page.[3]

1.1.1. Purpose:
The sequence diagram is used primarily to show the interactions between objects in the sequential order
that those interactions occur. An organization's technical staff can find sequence diagrams useful in
documenting how a future system should behave. During the design phase, architects and developers can
use the diagram to force out the system's object interactions, thus fleshing out overall system design.

One of the primary uses of sequence diagrams is in the transition from requirements expressed as use
cases to the next and more formal level of refinement. Use cases are often refined into one or more
sequence diagrams.

The purpose of activity diagram is to describe the procedural flow of actions as part of a larger activity. It
is used to model how activities are coordinated to provide a service; to show the events needed to achieve
some operation, and to illustrate how the events in a single use case relate to one another. [5]

2
1.1(a): Types of UML:
The UML diagrams are divided into two parts: Structural UML diagrams and Behavioral UML
diagrams which are listed below:[3]

Structural UML diagrams:

• Class diagram
• Package diagram
• Object diagram
• Component diagram
• Composite structure diagram
• Deployment diagram

Behavioral UML diagrams

• Activity diagram
• Sequence diagram
• Use case diagram
• State diagram
• Communication diagram
• Interaction overview diagram
• Timing diagram

3
1.2: Advantages of UML:

• Simplifies complex software design, can also implement OOPs like concept which is widely
used.
• It reduces thousands of words of explanation in a few graphical diagrams that may reduce time
consumption to understand.
• It makes communication more clear and real.
• It helps to acquire the entire system in a view.
• It becomes very much easy for the software programmer to implement the actual demand once
they have the clear picture of the problem.

1.2.1: Disadvantages of UML:

• Formal Notation is Not Necessary

• Ascending Degree of Complexity
• Not Necessary in ‘Architecture-Indifferent Design’

4
1.2. Scope:
• Provide users with a ready-to-use, expressive visual modeling language so they can develop and
exchange meaningful models.
• Provide extensibility and specialization mechanisms to extend the core concepts.
• Be independent of particular programming languages and development processes.
• Provide a formal basis for understanding the modeling language.
• Encourage the growth of the OO tools market.
• Support higher-level development concepts such as collaborations, frameworks, patterns and
components.
• Integrate best practices.[4]

1.3. Usage:
Lifeline represents typical instances of the components or classes in your system. Messages are
shown as arrows. They can be complete, lost or found; synchronous or asynchronous; call or signal.
Activate is used to denote participant activation. Once a participant is activated, its lifeline appears.
Objects are model elements that represent instances of a class or of classes. Classes in UML show
architecture and features of the designed system. Actor specifies a role played by a user or any other
system that interacts with the subject. [5]

5
Fig 1.3

1.3.1.Fields applying UML:

UML has been used in following areas

• Enterprise information systems

• Banking and financial services
• Telecommunications
• Defense
• Transportation
• Retail
• Science and Research
• Distributed Web-based services

UML can also be used to model non software systems, such as workflow in the legal systems, medical
electronics and patient healthcare systems, and the design of hardware. [6]

6
1.4 . Problem statement of Sequence diagram:
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. Don’t 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.[7]

1.4.1 Solution of problem statement

We can solve this issue by following these methods and make our sequence diagram
more efficient and easier to understand.
• Not adding to much data in the diagram. It makes the simple and easy to read.
• Don’t need to leaving space between the use case text and message arrow. It can
make the diagram easy to understand.
• Considering the origins of message arrow carefully.

1.5 Conclusion:
This report has introduced Sequence Diagrams as means to specify interactions between
structural elements of a system and the environment of a system. Sequence diagrams
therefore support the specification of sequences of events required to achieved user goals
and post-condition of use cases. Sequence diagrams must be kept consistent with both use
case diagrams and class diagrams.

7
Reference:

[1]. https://www.geeksforgeeks.org/unified-modeling-language-uml-sequence-diagrams/
[2]. https://www.researchgate.net/publication/322991992_Importance_of_UML_Diagrams_in_Software_Development
[3]. https://www.smartdraw.com/uml-diagram/
[4]. https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-uml/
[5]. https://www.edrawsoft.com/uml-introduction.php
[6]. https://en.wikipedia.org/wiki/Applications_of_UML
[7]. https://creately.com/blog/diagrams/sequence-diagram-tutorial/#Common