Unified Compliance NextGen
  • UCF NextGen
    • On-Boarding
    • PlantUML
      • Diagrams as Code
        • Why use diagrams as Code tools?
        • Use Cases
        • Introduction to PlantUML
        • Syntax
          • Basic PlantUML Syntax
          • Sequence Diagram
            • Lifelines
            • Messages
            • ExecutionSpecification
            • Autonumber
            • Notes
            • Interactions
            • Organization
          • Use Case Diagram
            • Use Case
            • Actor
            • Associations
            • Organization
            • Notes
          • Class Diagram
            • Classes and Other Entities
            • Attributes and Methods
            • Relationships
            • Organization
            • Notes
          • Object Diagram
            • Objects
            • Relations and Associations
            • Organization
            • Notes
          • Work Breakdown Structure Diagram
            • OrgMode Syntax
            • Arithmetic Notation
            • Styling
          • Activity Diagram
            • Actions and Other Objects
            • Arrows
            • Conditionals
            • Loops
            • Forks, Splits, and Merges
            • Notes
          • Text Formatting
          • Skin Parameters
    • Control Workspace
      • My Frameworks
        • Authority Document Details
        • Common Control Details
      • List Manager
      • Compare
      • Exports
    • UCF Catalog
    • Profile
    • Administration
      • Account Settings
        • General
        • Team
        • Organization
        • Industry
        • Groups
        • Initiatives
      • API Manager
      • Billing
    • API Gateway
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. UCF NextGen
  2. PlantUML
  3. Diagrams as Code
  4. Syntax

Sequence Diagram

PreviousBasic PlantUML SyntaxNextLifelines

Last updated 1 year ago

Was this helpful?

A UML sequence diagram is an interaction diagram that shows messages passing between different participants over time. Sequence Diagrams allow you to describe the flow of interactions between different components or actors in your system or even manual processes.

Sequence Diagrams can be a useful tool for understanding and communicating how different parts of a system interact with each other. They provide a visual representation of the order in which messages are sent between objects or components, making it easier to understand the sequence of events in a system.

Sequence diagrams also support features like declaring participants, allowing for more control over their representation and display order. Participants can be declared using keywords like “participant,” “actor,” “boundary,” “control,” and so on. Each participant is represented by a lifeline that spans the length of the diagram from top to bottom. Time also flows from top to bottom. The messages are represented by different arrows moving left and right between the participants’ lifelines.

Below is a basic example of three participants communicating with each other.

Sequence Diagram