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

Synchronous Message

PreviousActivation BarNextAsynchronous Message

Last updated 7 months ago

A Synchronous Message in a UML Sequence Diagram represents a call where the sender waits for a response before continuing. In Modeldraw, you can use Synchronous Messages to show method invocations or requests that block the sender until a response is received.

Understanding Synchronous Message

A Synchronous Message represents a call where the sender waits for the receiver to handle the message. Key characteristics include:

  • It shows a call that blocks the sender until a response is received

  • It is drawn as a solid line with a filled arrowhead

  • It typically triggers the start of an Activation Bar on the receiving Lifeline

  • It is usually paired with a return message

A Synchronous Message is represented in UML by a solid line with a filled arrowhead pointing from the sender to the receiver.

Synchronous Messages are crucial in Sequence Diagrams for:

  • Representing method calls or function invocations

  • Showing interactions where the sender waits for a response

  • Indicating the flow of control between objects

Creating a Synchronous Message

To create a Synchronous Message in Modeldraw:

  1. Select the Synchronous 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 Synchronous 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).

A Synchronous Message and a Self-Call