SysMLv1.7 Activity extensions: ControlOperator and ControlValueKind: ADVANCED REFERENCE CARD

Nearly everything you wanted to know (and maybe some things you didn't want to know) about control in UML2.5.1 and in SysMLv1 and the SysMLv1 ControlOperator and ControlValueKind extensions for data as control, all in one reference card.

Click on the image to view it full size

UML2/SysMLv1: A control Pin (a Pin with isControl = True) for a CallBehaviorAction does not have a corresponding Parameter

Up next

Next trail section

11:02: Activity Decomposition for functional allocation

Notes

[ISSUE, TOOL] MagicDraw/Cameo: ERROR: Incorrectly uses 2 ObjectFlow edges and a CentralBufferNode for "elided Pin notation" instead of an abstract ObjectNode _symbol_ and 2 arrow _symbols_ (notations that are supposed to represent together 2 Pins and 1 ObjectFlow edge)

[DISPLAY, ISSUE, TOOL, WARNING] Webel recommends when using MagicDraw/Cameo: AVOID the "elided Pin" abstract ObjectNode notation on Activity Diagrams, use explicit Pins!

Snippets (quotes/extracts)

[SysML-1.6] A control operator is a behavior that is intended to represent an arbitrarily complex logical operator that can be used to enable and disable other actions. ... The «controlOperator» stereotype also applies to operations with the same semantics.

[SysML-1.6] When the «controlOperator» stereotype is applied to behaviors, the behavior takes control values as inputs or provides them as outputs, that is, it treats control as data

[SysML-1.6] When the «controlOperator» stereotype is not applied, the behavior may not have a parameter typed by ControlValue.

[UML-2.5.1] isControl : Boolean [1..1] = false Indicates whether the Pin provides data to the Action or just controls how the Action executes.

[fUML-1.4] If isControlType=true for an ObjectNode, ControlFlows may be incoming to and outgoing from the ObjectNode, objects tokens can come into or go out of the ObjectNode along ControlFlows, and these tokens can flow along ControlFlows reached downstream ...

[UML-2.5.1] ObjectNode::isControlType : Boolean [1..1] = false Indicates whether the type of the ObjectNode is to be treated as representing control values that may traverse ControlFlows.

[UML-2.5.1] A control Pin (with isControl=true) must have a control type (isControlType=true), so that they may be used with ControlFlows.

[UML-2.5.1] The effect of object tokens accepted from ControlFlows is not specified (see isControlType for ObjectNodes ...), but the semantics above applies if the effect is to execute the ExecutableNode.

[UML-2.5.1] A ControlFlow is an ActivityEdge that only passes control tokens (and some object tokens as specified by modelers, see isControlType for ObjectNodes ...).

[UML-2.5.1] ObjectNodes hold object tokens accepted from incoming ObjectFlows and may subsequently offer them to outgoing ObjectFlows (with a modeler-specified exception for ControlFlows, see isControlType for ObjectNodes ...).

[UML-2.5.1] Control Pins are ignored in the constraints that Actions place on Pins (including matching to parameters for InvocationActions ...).

Visit also

Visit also (backlinks)

UML2/SysMLv1: A control Pin (a Pin with isControl = True) for a CallBehaviorAction does not have a corresponding Parameter

Related slides (includes other tutorials)

Figure 11-8: Abstract Syntax for SysML Activity Extensions

UML2 Activity Diagram - essential metaclasses - ADVANCED REFERENCE ONLY

UML2 Actions - metaclasses - ADVANCED REFERENCE ONLY

UML2 simplified key metaclass hierarchy (excluding relationships) - ADVANCED REFERENCE ONLY

UML2 simplified key "relationship" metaclasses hierachy - ADVANCED REFERENCE ONLY

UML2 StateMachine - metaclasses - ADVANCED REFERENCE ONLY

UML2 Types of Pins - metaclasses

Figure 11-9: Control values

Figure 11-10: Continuous system example 1 {ELIDED PINS}

Figure 11-10: Continuous system example 1 {EXPLICIT PINS}

Figure 11-11: Continuous system example 2 {ELIDED PINS}

Figure 11-11: Continuous system example 2 {EXPLICIT PINS}

Figure 11-12: Continuous system example 3 {EXPLICIT PINS}

Starting an Action that has a ControlPin

SysML Activity extension stereotypes - REFERENCE CARD

Related slides (backlinks, includes other tutorials)

Flags