Book a Demo

Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

Join

Description

A Fork/Join used in UML Activity diagrams as modeled using Sparx Systems Enterprise Architect. A Fork/Join used in UML Activity diagrams as modeled using Sparx Systems Enterprise Architect.

The Join element is used by Activity and StateMachine diagrams. The example illustrates a Join transition between Activities. With respect to StateMachine diagrams, a Join pseudosate indicates multiple States concurrently transitioning into the Join and onto a single State. Unlike Choice or Junction pseudostates, Joins must not have triggers or guards. This diagram demonstrates a Fork pseudostate dividing into two concurrent Regions, which then return to the End State via the Join.

Using a Fork/Join in a StateMachine diagram modeled in Sparx Systems Enterprise Architect.

Learn more

OMG UML Specification:

The OMG UML specification (UML Superstructure Specification, v2.1.1, p. 538) states:

Join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.