An InitialNode shall not have any incoming ActivityEdges, which means the InitialNodes owned by an Activity will always be enabled when the Activity begins execution and a single control token is placed on each such InitialNode when Activity execution sta

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
INCORRECT InitialNode no implicit fork
CORRECT InitialNode explicit fork
OPTION double InitialNode
Source
Unified Modeling Language 2.5.1
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
SEMANTIC
UML keywords
Activity
InitialNode
ControlNode
control token
ActivityEdge
An Activity may have more than one InitialNode.
Full quote
An InitialNode shall not have any incoming ActivityEdges, which means the InitialNodes owned by an Activity will always be enabled when the Activity begins execution and a single control token is placed on each such InitialNode when Activity execution starts.
Next snippet
The outgoing ActivityEdges of an InitialNode must all be ControlFlows. The control token placed on an InitialNode is offered concurrently on all outgoing ControlFlows.
Related snippets
An InitialNode is a ControlNode that acts as a starting point for executing an Activity.
An Activity may have more than one InitialNode.
If an Activity has more than one InitialNode, then invoking the Activity starts multiple concurrent control flows, one for each InitialNode. (Additional concurrent flows may begin at input ActivityParameterNodes and enabled ExecutableNodes ...
Related snippets (backlinks)
The outgoing ActivityEdges of an InitialNode must all be ControlFlows. The control token placed on an InitialNode is offered concurrently on all outgoing ControlFlows.
InitialNodes are an exception to the rule that ControlNodes cannot “hold” tokens, but only manage their flow.
Visit also
Visit also (backlinks)