LoopNode: running loopVariable example

Gallery
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
Section
01:04: UML Behavior: Activities quick start
Topic level
ESSENTIAL
UML keywords
Activity
Activity Diagram
LoopNode
LoopNode::setupPart
LoopNode::bodyPart
LoopNode::test
LoopNode:decider
LoopNode::result
LoopNode::bodyOutput
LoopNode::isTestedFirst
LoopNode::loopVariable
LoopNode::loopVariableInput
ReadStructuralFeatureAction
OpaqueAction
CallBehaviorAction
OpaqueBehavior
AddStructuralFeatureValueAction
Keywords
Slide kind
UML Activity Diagram
This shows a LoopNode with loopVariable running in Magic Model Analyst® (Cameo Simulation Toolkit®) (see also the mini video below):
Click on the image to view it full size
Watch simulation
While setting it up is rather fiddly, it's not too bad once you have the hang of it. Nevertheless, consider using UML-friendly Action Language for Foundational UML (Alf) instead.
Up next
ExpansionRegion: running «iterative» example
Notes
[CAVEAT] Cameo Simulation Toolkit 19SP3 DOES NOT support 'setupPart' in LoopNode (because fUML does not)
[TIP]{OPTION} Not every task in Activity Diagrams is well-suited to graphical modelling and LoopNode and ConditionalNode are notoriously fiddly to setup; consider using Action Language Helper (ALH) or Action Language for Foundational UML (Alf)
[ISSUE] UML-2.5.1 refers to 'isTestFirst' in 16.11.3.4 but to isTestedFirst in the attributes list for LoopNode under 16.14.30.4 Attributes
Snippets (quotes/extracts)
  [UML-2.5.1] A LoopNode may also define a set of loopVariable OutputPins used to hold intermediate values during each loop iteration. These OutputPins may have outgoing ActivityEdges, in order to make the values they hold available within the test and bodyPart ...
  [UML-2.5.1] If a LoopNode has loopVariable OutputPins, then it must also have matching sets of loopVariableInput InputPins, bodyOutput OutputPins (owned by Actions within the bodyPart), and result OutputPins.
  [UML-2.5.1] When the LoopNode begins executing, the tokens on the loopVariableInput InputPins are moved to the corresponding loopVariable OutputPins before the first iteration of the loop.
  [UML-2.5.1] After the completion of each execution of the bodyPart of the LoopNode, any remaining tokens on the loopVariable OutputPins are destroyed and tokens on the bodyOutput OutputPins are copied to the corresponding loopVariable OutputPins so that they are ...
  [UML-2.5.1] Once the test fails and the loop is completed, the tokens on the bodyOutput OutputPins from the last iteration are moved to the result OutputPins and offered on any edges outgoing from those OutputPins.
  [fUML-1.4] 7.11.2.7 LoopNode [1] fuml_loop_node_no_setup_part no setupParts in fUML self.setupPart->isEmpty()
Visit also
Alf zone
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)