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
  • Understanding Asynchronous Message
  • Creating an Asynchronous Message
  • Creating a Self-Call
  1. UML Designer
  2. Sequence Diagrams

Asynchronous Message

PreviousSynchronous MessageNextReturn Message

Last updated 7 months ago

An Asynchronous Message in a UML Sequence Diagram represents a call where the sender doesn't wait for a response before continuing. In Modeldraw, you can use Asynchronous Messages to show non-blocking method invocations or requests that allow the sender to continue processing immediately.

Understanding Asynchronous Message

An Asynchronous Message represents a call where the sender continues processing immediately after sending the message. Key characteristics include:

  • It shows a call that doesn't block the sender

  • It is drawn as a solid line with an open arrowhead

  • It may or may not trigger the start of an Activation Bar on the receiving Lifeline

  • It typically doesn't have an immediate return message

An Asynchronous Message is represented in UML by a solid line with an open arrowhead pointing from the sender to the receiver.

Asynchronous Messages are crucial in Sequence Diagrams for:

  • Representing non-blocking method calls or events

  • Showing interactions where the sender doesn't wait for a response

  • Indicating parallel or concurrent processing

Creating an Asynchronous Message

To create an Asynchronous Message in Modeldraw:

  1. Select the Asynchronous Message tool from the toolbox.

  2. Click on the Activation Bar of the sending Lifeline where you want the message to start.

  3. Move your cursor to the receiving Lifeline.

  4. Click on the Activation Bar of the receiving Lifeline where you want the message to end.

  5. The Asynchronous Message will be created between the two Activation Bars.

Creating a Self-Call

To create a Self-Call in Modeldraw:

  1. Select either the Synchronous Message or Asynchronous Message tool from the toolbox, depending on the type of Self-Call you want to create.

  2. Click once on the Activation Bar where you want the Self-Call to start.

  3. Click again on the same Activation Bar where you want the Self-Call to end.

  4. The Self-Call will be created, represented by a looping arrow (solid for Synchronous, dashed for Asynchronous).

An Asynchronous Message and a Self-Call