Modeldraw
  • Welcome to Modeldraw
  • Getting Started
    • Quickstart Guide
  • FAQ
  • UML Designer
    • Common Elements
      • Comment
      • Comment Link
      • Dependency
      • Realization
      • Frame
    • Class Diagrams
      • Class
      • Association
      • Generalization
      • Composition
      • Aggregation
      • Enumeration
      • Interface
      • Association Class Link
      • Ball (Interface Realization)
      • Socket (Required Interface)
    • Sequence Diagrams
      • Lifeline
      • Activation Bar
      • Synchronous Message
      • Asynchronous Message
      • Return Message
      • Found Message
      • Interaction Frame
    • Use Case Diagrams
      • Actor
      • Use Case
      • Association
      • System Boundary
      • Generalization
      • Include Relationship
      • Extend Relationship
    • State Machine Diagrams
      • State
      • Initial State
      • Final State
      • Transition
      • Superstate
      • Concurrent Boundary
      • History Pseudostate
      • History Transition
    • Package Diagrams
      • Package
    • Deployment Diagrams
      • Node
      • Communication Path
      • Deployed Artifact
      • Internet
    • Activity Diagrams
      • Initial Node
      • Activity Final
      • Action
      • Flow
      • Decision / Merge
      • Fork / Join
      • Partitions
      • Flow Final
      • Send Signal
      • Accept Signal
      • Time Signal
    • Component Diagrams
      • Component
      • Ball (Interface Realization)
      • Socket (Required Interface)
    • Communication Diagrams
      • Object
      • Link
  • Wireframes
    • Views
    • Layouts
    • Components
Powered by GitBook
On this page
  1. UML Designer
  2. Sequence Diagrams

Lifeline

PreviousSequence DiagramsNextActivation Bar

Last updated 7 months ago

A Lifeline in a UML Sequence Diagram represents an individual participant in the interaction. In Modeldraw, you can use Lifelines to model objects, actors, or processes that interact over time in your system.

Understanding Lifeline

A Lifeline represents a participant in a sequence of interactions. Key characteristics include:

  • It depicts an object, actor, or process in the system

  • It extends vertically to show the participant's existence over time

  • It can have activation bars to show when the participant is active or performing actions

  • It can be created or destroyed during the sequence

A Lifeline is represented in UML by a rectangle at the top (known as the "head") with a dashed line extending downwards.

Lifelines are fundamental elements in Sequence Diagrams and are used to:

  • Show the participants involved in a particular interaction

  • Indicate when participants are created or destroyed

  • Serve as sources and targets for messages

  • Display activation bars to show when a participant is active

Lifelines