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. Activity Diagrams

Send Signal

PreviousFlow FinalNextAccept Signal

Last updated 7 months ago

A Send Signal in an Activity Diagram represents an action that transmits a signal or message to another part of the system or to an external entity. It's used to model asynchronous communication between different parts of a process or system.

With Send Signals in Modeldraw's Activity Diagram, you can:

  • Represent the transmission of information or triggers to other parts of the system

  • Model asynchronous communication in your processes

  • Show how one part of a system can initiate actions in another part

  • Illustrate event-driven behaviors in your workflows

  • Demonstrate interactions between different components or actors in your system

Understanding Send Signal

A Send Signal in Modeldraw's Activity Diagram tool is typically represented by a convex pentagon (a rectangle with a point on one side). Key points to understand about Send Signals include:

  • It represents sending a signal without waiting for a response.

  • The Send Signal doesn't wait for or expect an immediate reply.

  • It can initiate actions or processes in other parts of the system.

  • The signal being sent is usually named to indicate its purpose or content.

  • After sending a signal, the flow in the current activity typically continues.

  • Can be used to show communication across system or component boundaries.

Remember that Send Signals are often used in conjunction with Accept Signals in other parts of the diagram or in separate diagrams to show the complete communication.

A Send Signal and an Accept Signal