Learn about Webel IT's new SysMLv2/MBSE Workshop Seminar course!

GOTCHA: Just because an InitialNode MAY have more than one outgoing ControlFlow and offers tokens on every outgoing ControlFlow does NOT mean that every outgoing edge takes a control token; InitialNode does NOT act like an implicit fork!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
WARNING
Policy level
STRICT
UML keywords
InitialNode
implicit fork
This does NOT alone tell the whole story:
UML-2.5.1: 'The outgoing ActivityEdges of an InitialNode must all be ControlFlows. The control token placed on an InitialNode is offered concurrently on all outgoing ControlFlows.'
In Magic Model Analyst® (Cameo Simulation Toolkit®) only one outgoing ControlFlow is taken (which is actually consistent with statements elsewhere in UML-2.5.1)! Therefore, use a single downstream Action as ExecutableNode with an implicit fork with multiple outgoing ControlFlows:
UML-2.5.1: 'When an ExecutableNode completes an execution, the control token representing that execution is removed from the ExecutableNode and control tokens are offered on all outgoing ControlFlows of the ExecutableNode. That is, there is an implicit fork ...'
Relates to
Related notes
Related notes (backlinks)
Related snippets (extracts)
  [UML-2.5.1] When an ExecutableNode completes an execution, the control token representing that execution is removed from the ExecutableNode and control tokens are offered on all outgoing ControlFlows of the ExecutableNode. That is, there is an implicit fork ...
  [UML-2.5.1] The outgoing ActivityEdges of an InitialNode must all be ControlFlows. The control token placed on an InitialNode is offered concurrently on all outgoing ControlFlows.
Visit also
Visit also (backlinks)