What is Sequence Diagram? Definition and Sequence Diagrams in UML

Table of Contents

What is Sequence Diagram?

A sequence diagram is defined as a type of UML (Unified Modeling Language) diagram used in software engineering and systems design to visualize the interactions and communication between various components or objects within a system. Sequence diagrams are particularly useful for depicting the dynamic behavior of a system and how different components collaborate to achieve a specific task or goal. They are commonly used during the design and documentation phases of software development.

Key elements and concepts in a sequence diagram include:

• Lifelines: These represent the individual objects or components involved in the interaction. Each lifeline is typically depicted as a vertical line, and their names are often placed at the top of these lines.

• Messages: These are the horizontal arrows or lines that connect lifelines, indicating the order of messages passed between objects. Messages can be synchronous (blocking) or asynchronous (non-blocking), and they typically have labels that describe the action or method being invoked.

• Activation Bars: These represent the period during which an object is active and processing a message. They are depicted as a box or vertical rectangle on the lifeline and show the duration of the object’s involvement in the interaction.

• Return Messages: These indicate the response from an object to a message it received. They are usually represented by a dashed line and are labeled to show the result or value being returned.

• Optional Fragments: Sequence diagrams can also include optional fragments, such as loops, conditionals, and alternative paths, which help illustrate different scenarios and decision points within the interaction.

Sequence diagrams are helpful for various purposes, including:

• Understanding and visualizing the flow of interactions between objects or components.

• Designing and documenting the behavior of a system or a specific feature.

• Communicating and discussing system behavior with stakeholders, including developers, testers, and business analysts.

• Identifying potential issues, such as bottlenecks or synchronization problems in the system’s design.

Overall, sequence diagrams are a valuable tool in the software development process for modeling and understanding the dynamic aspects of a system’s operation. They complement other UML diagrams like class diagrams and use case diagrams, which focus on different aspects of system design and architecture.

Sequence Diagram Example

Let’s create a simple sequence diagram example to illustrate how it works. In this example, we’ll model the interaction between a customer and a bank’s ATM (Automated Teller Machine) when the customer withdraws cash.

Title: ATM Cash Withdrawal

Lifelines:

Customer

ATM

Messages:

1. Customer -> ATM: Insert Card
2. ATM -> Customer: Verify Card
3. Customer -> ATM: Enter PIN
4. ATM -> Customer: Verify PIN
5. Customer -> ATM: Request Cash Withdrawal
6. ATM -> Bank: Verify Funds
7. Bank –> ATM: Approved (or Denied)
8. ATM -> Customer: Dispense Cash
9. ATM -> Customer: Eject Card

Explanation:

1. The sequence diagram starts with two lifelines: “Customer” and “ATM.”
2. The “Activation Intervals” indicate when each lifeline is active during the interaction. The customer is active from the beginning, and the ATM becomes active when the customer inserts the card.
3. Messages are exchanged between the lifelines to represent the flow of the interaction. Here’s a breakdown:

• The customer inserts their card into the ATM.

• The ATM verifies the card.

• The customer enters their PIN.

• The ATM verifies the PIN.

• The customer requests a cash withdrawal.

• The ATM contacts the bank to verify if there are sufficient funds.

• The bank responds to the ATM with an approval or denial.

• If approved, the ATM dispenses cash to the customer.

• The ATM ejects the customer’s card.

4. The “Activation Intervals” at the end of the diagram show when each lifeline deactivates. The customer’s interaction ends after receiving cash and their card, while the ATM remains active.

This is a basic example of a sequence diagram depicting the interaction between a customer and an ATM during a cash withdrawal. Sequence diagrams can become more complex as you model interactions involving multiple objects or components, conditional branches, loops, and more.

Learn more: What is Activity Diagram?

Sequence Diagrams in UML

Sequence diagrams are a type of UML (Unified Modeling Language) diagram used to visualize and document the dynamic interactions and behaviors between objects or components within a system or a software application. They help model the sequence of messages exchanged during the execution of a use case or a specific scenario. Here are some key components and concepts commonly used in sequence diagrams:

• Lifelines: Lifelines represent objects or components participating in the interaction. They are typically depicted as vertical lines (often dashed) with the name of the object or component at the top.

• Activation Bars: These horizontal bars, often drawn on top of a lifeline, represent the time during which an object or component is actively processing a message. They show when an object is busy and when it is idle.

• Messages: Messages are the arrows or lines that connect lifelines and show the flow of communication between objects. Several message varieties exist, such as:

Synchronous Messages: These are depicted with solid arrows and indicate that the sender waits for a response before proceeding.

Asynchronous Messages: These are represented with dashed arrows and indicate that the sender continues without waiting for a response.

Return Messages: Shown with a dashed arrow and a labeled reference, they represent the response returned by the receiving object.

Self Messages: These are messages sent from an object to itself and are depicted as a loopback arrow.

• Activation and Deactivation: When an object is active (processing a message), the activation bar is active, and when it’s not processing a message, the activation bar deactivates.

• Optional Fragments: These are used to represent conditional and iterative behavior in a sequence diagram. For example, you can use “alt” (alternative) and “loop” fragments to show different scenarios or loops within the interaction.

• Object Destruction: The termination of an object or component is shown with a large “X” on the lifeline.

Sequence diagrams are useful for various purposes, including:

• Modeling the interactions between objects during a use case or scenario.

• Understanding the dynamic behavior of a system.

• Designing and documenting the order of message exchanges.

• Identifying potential issues, such as concurrency problems or bottlenecks.

• Communicating system behavior to stakeholders, including developers, testers, and business analysts.

These diagrams are a crucial tool in software development for specifying, designing, and documenting the dynamic aspects of a system or application’s behavior. They complement other UML diagrams, such as class diagrams (which describe the static structure) and use case diagrams (which show the system’s functionality from the user’s perspective).

Learn more: What is UML Diagram?