UML2 Types of Pins - metaclasses This content has been marked as discussing an ADVANCED topic! Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 01:04: UML Behavior: Activities quick start Slide kind UML Profile Diagram
Claim: The ControlValue input to Monitor Traction without a Pin is invalid in 'Figure 11-10: Continuous system example 1' and multiple issues with ControlOperator
Tokens are placed on control OutputPins according to the same semantics as tokens placed on ControlFlows coming out of an Actions. Source Unified Modeling Language 2.5.1
Tokens arriving at a control InputPin have the same semantics as control tokens arriving at the Action, except that control tokens can be buffered in control Pins. Source Unified Modeling Language 2.5.1
Control Pins are ignored in the constraints that Actions place on Pins (including matching to parameters for InvocationActions ...). Source Unified Modeling Language 2.5.1
A control Pin (with isControl=true) must have a control type (isControlType=true), so that they may be used with ControlFlows. Source Unified Modeling Language 2.5.1
object_nodes ControlFlows may not have ObjectNodes at either end, except for ObjectNodes with control type. Source Unified Modeling Language 2.5.1
Control Pins are shown with the textual annotation {control} placed near the Pin symbol. Source Unified Modeling Language 2.5.1
isControl : Boolean [1..1] = false Indicates whether the Pin provides data to the Action or just controls how the Action executes. Source Unified Modeling Language 2.5.1
