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

Fork / Join

PreviousDecision / MergeNextPartitions

Last updated 7 months ago

The Fork / Join element in an Activity Diagram serves a dual purpose. As a Fork node, it splits the flow into multiple concurrent paths. As a Join node, it synchronizes multiple concurrent paths back into a single flow.

With Fork / Join nodes in Modeldraw's Activity Diagram, you can:

  • Model parallel processing or concurrent activities in your workflow

  • Represent the start and end points of simultaneous actions

  • Show how multiple activities can occur independently and then synchronize

  • Illustrate complex processes with parallel and sequential elements

  • Simplify diagrams by using the same symbol for both forking and joining

Understanding Fork / Join

A Fork / Join node in Modeldraw's Activity Diagram tool is represented by a thick horizontal or vertical line. Key points to understand about Fork / Join nodes include:

  • The same symbol is used for both forking and joining points.

  • When used as a Fork, it has one incoming flow and multiple outgoing flows.

  • When used as a Join, it has multiple incoming flows and one outgoing flow.

  • In its Fork role, all outgoing flows represent paths that can be executed concurrently.

  • In its Join role, it waits for all incoming flows to complete before continuing.

  • Can be drawn horizontally or vertically, depending on the diagram's layout.

  • The role (Fork or Join) is determined by how it's used in the diagram.

Remember that the context and connections determine whether the node functions as a Fork or a Join.

A Fork