Fork / Join
Last updated
Last updated
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
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.
