Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Content layer
id727781504
Content column
id727781506
Content block
id727781505

The fork vertices Fork Vertices are used to split an incoming transition into two or more transitions terminating on the orthogonal target vertices (i.e., vertices in different regions of the composite state). The segments going out of a fork vertex Fork Vertex must not have guards or triggers.

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

  1. A Fork Node can have exactly one incoming Activity Edge (or Transition), though it may have multiple outgoing Activity Edges (or Transitions).
  2. A Join Node can have exactly one outgoing Activity Edge (or Transition) but may have multiple incoming Activity Edges (or Transitions).

The Fork and Join are represented by the same symbol. Although, you can set the Use different Fork/Join and Decision/Merge notations project option to draw different notations for the Fork and Join.

Image Removed

An example shows the different Fork and Join notations
  1. Join Vertex must have at least two incoming Transitions and exactly one outgoing Transition.
  2. A Fork Vertex must have at least two outgoing Transitions and exactly one incoming Transition.
Content block
id727781503

Related pages