Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
| Prev | Next |
Fork
Description
The Fork element is used in both Activity and StateMachine diagrams. With respect to StateMachine diagrams, a Fork pseudostate signifies that its incoming transition comes from a single state, and it has multiple outgoing transitions. These transitions must occur concurrently, requiring the use of concurrent regions, as depicted here in the Composite State. Unlike Choice or Junction pseudostates, Forks 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 pseudostate.
Learn more
OMG UML Specification:
The OMG UML specification (UML Superstructure Specification, v2.1.1, p.538) states:
Fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e. vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.