Guidelines of control nodes within activity modeling.
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
An activity final node is a final node that stops all flows in an activity.
A control node is an abstract activity node that coordinates flows in an activity.
A decision node is a control node that chooses between outgoing flows.
A control node is an abstract activity node that coordinates flows in an activity.
A final node is an abstract control node at which a flow in an activity stops.
A flow final node is a final node that terminates a flow.
A control node is an abstract activity node that coordinates flows in an activity.
A fork node is a control node that splits a flow into multiple concurrent flows.
A control node is an abstract activity node that coordinates flows in an activity.
An initial node is a control node at which flow starts when the activity is invoked.
A control node is an abstract activity node that coordinates flows in an activity.
A join node is a control node that synchronizes multiple flows. Join nodes have a Boolean value specification using the names of the incoming edges to specify the conditions under which the join will emit a token.
A control node is an abstract activity node that coordinates flows in an activity.
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
Model Guidelines generated by Adocus MetaModelAgent version 4.2.0.007 | Tuesday, 14 February 2017 15:17 |