UML Diagrams Zicomi Systems publishes some UML example diagrams online from the world famous UML dictionary. more...
Version 2.5 Released Zicomi Systems is delighted to announce that version 2.5 of Zicomi Mentor is released. With support for UML 2.0 and all thirteen UML diagrams more...
Zicomi Systems' Director speaks about the UML at Objects by Design - an informative interview more...
Partner Programme Zicom Systems is delighted to announce a new world wide partner programme, become a partner today. more...
OMG Member Zicom Systems is made a member of the OMG!
Join (Vertical)
A join is a kind of pseudostate that re-unites two or more incoming transitions. All of the incoming transitions must have fired before the outgoing transition will fire.
Explanation
Many systems require that a number of actions are carried out or performed at the same time. A join reunites a number of transitions that have been divided by a fork. It is important that the concurrent behavior is reunited otherwise the executing system would not conclude in a predictable way. The fork should not be confused with a merge that also has a number of incoming transitions, the important difference being that a merge reunites the branches of a decision.
Important Points
Joins are not commonly named.
A join, like any UML element can be named, but they are commonly not named as it often adds little meaning. The meaning is expressed in the transitions that unite at the join and the parts of the diagram from which they have originated.
A fork is related to a join as a paired element. The fork "splits" a single flow into two or more flows, which can be re-united by one or more subsequent joins.