SysMLv1: Cameo Simulation Toolkit: Comparison of a Fork then a Merge with a Fork then a Join [with mini video]

Gallery
Tutorial
TRAIL: SysMLv1/UML: Cameo Simulation Toolkit® (Magic Model Analyst®): Some basics for beginners and some more advanced cases [with mini videos]
Section
Topic level
BASIC
UML keywords
Activity
Parameter
ParameterDirectionKind::inout
ActivityParameterNode
Pin
InputPin
OutputPin
CallBehaviorAction
SysML keywords
Block
Keywords
Slide kind
SysML Activity Diagram
SysML Block Definition Diagram (BDD)

Demonstrates a the basic difference between a UML2/SysMLv1 Merge and a Join in Magic Model Analyst® (Cameo Simulation Toolkit®) .

A basic MergeNode does not wait for tokens to be available on all incoming flows; a basic JoinNode (one without a joinSpec) waits for tokens to be available on all incoming flows.

UML2.5.1: 'A MergeNode is a control node that brings together multiple flows without synchronization.'
UML2.5.1: 'All tokens offered on the incoming edges of a MergeNode are offered to the outgoing edge. There is no synchronization of flows or joining of tokens.'
UML2.5.1: 'A JoinNode is a ControlNode that synchronizes multiple flows. A JoinNode shall have exactly one outgoing ActivityEdge but may have multiple incoming ActivityEdges.'
UML2.5.1: 'If a JoinNode does not have a joinSpec, then this is equivalent to a joinSpec Expression with the Boolean operator “and.” That is, the implicit default joinSpec condition is that there is at least one token offered on each incoming ActivityEdge.'
Note that the mini video uses the UML style symbols for a JoinNode and MergeNode, which are visually the same for ForkNode and DecisionNode respectively; The slide diagram uses the distinguishing JoinNode and MergeNode symbol forms offered by Cameo Systems Modeler:
SysMLv1: TIP: SysMLv1: Cameo: JoinNode and MergeNode distinguishing notations option
Click on the image to view it full size
Watch simulation
Up next
SysMLv1: Cameo Simulation Toolkit: CallBehaviorAction vs CallOperationAction and Pins [with mini video]
Notes
[TIP, TOOL] SysMLv1: TIP: SysMLv1: Cameo: JoinNode and MergeNode distinguishing notations option
Snippets (quotes/extracts)
  [UML-2.5.1] A MergeNode is a control node that brings together multiple flows without synchronization.
  [UML-2.5.1] A JoinNode is a ControlNode that synchronizes multiple flows. A JoinNode shall have exactly one outgoing ActivityEdge but may have multiple incoming ActivityEdges.
  [UML-2.5.1] All tokens offered on the incoming edges of a MergeNode are offered to the outgoing edge. There is no synchronization of flows or joining of tokens.
  [UML-2.5.1] If a JoinNode does not have a joinSpec, then this is equivalent to a joinSpec Expression with the Boolean operator “and.” That is, the implicit default joinSpec condition is that there is at least one token offered on each incoming ActivityEdge.
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)
Visit also
ActivityParameterNode cases - REFERENCE CARD
Parameter vs ActivityParameterNode vs Pin
Course: Model-Based Systems Engineering with the OMG's Systems Modeling Language® (v1) and the MagicDraw/Cameo (CATIA Magic™) tools for SysML
SysMLv1: Cameo Simulation Toolkit: HOWTO: Send a Signal via a nested Port using InvocationOnNestedPortAction and 'onNestedPort' together with 'onPort' [with mini video]
SysMLv1: Cameo Simulation Toolkit: HOWTO handle sending and receiving families of related Signal types with reuse of send/receive and processing logic [with mini video]
SysMLv1: Cameo Simulation Toolkit: HOWTO send a Signal via a Port to an intended recipient via a mediating secure RoutingHub [with mini video]
TRAIL: UML Behavior: Activities and Actions
01:04: UML Behavior: Activities quick start
UML2 Activity Diagram - essential metaclasses - ADVANCED REFERENCE ONLY
UML2 Actions - metaclasses - ADVANCED REFERENCE ONLY
Semantics of a Foundational Subset for Executable UML Models 1.4
StateMachine diagram for comparing action language access to an operation for a guard
SysMLv1: Cameo Simulation Toolkit: An Activity with two ActivityParameterNodes corresponding to a single inout Operation Parameter [with mini video]
OR with DecisionNode and MergeNode
Loop: running example using DecisionNode and MergeNode and an Integer property in a context
AND with ForkNode and JoinNode
ForkNode and JoinNode with optional ControlFlow guards - LIMITED SUPPORT
Visit also (backlinks)
External links
HIGH RESOLUTION on Vimeo