Starting an Action that has a ControlPin

Please note that SysMLv1 extends UML2 with more flexible control capabilities. Please visit also the following slide (from the SysMLv1 topics section), which links to many other examples on this site:

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

Up next

Starting an Action that has a ValuePin - LIMITED SUPPORT

Notes

Snippets (quotes/extracts)

[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] 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] Control Pins are ignored in the constraints that Actions place on Pins (including matching to parameters for InvocationActions ...).

[UML-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.

[UML-2.5.1] An Action may accept inputs and produce outputs, as specified by InputPins and OutputPins of the Action, respectively. Each Pin on an Action specifies the type and multiplicity for a specific input or output of that Action.

[UML-2.5.1] An Action cannot start execution if one of its InputPins has fewer values than the lower multiplicity of that InputPin.

[UML-2.5.1] When completed, an Action execution provides any output data on the OutputPins of the Action, and it terminates.

[UML-2.5.1] The Action execution consumes input data on all InputPins on the Action up to the upper multiplicity for each InputPin.

[UML-2.5.1] Tokens consumed by an Action are immediately removed from its InputPins when the action begins an execution (except in some cases for StructuredActivityNodes, where tokens may remain on InputPins during the Action execution ...)

[UML-2.5.1] The upper multiplicity determines the maximum number of values that can be consumed from an InputPin by a single execution of its Action.

[UML-2.5.1] 16.4.3.5 Value Specification Actions - A ValueSpecificationAction is an Action that evaluates a ValueSpecification and places the resulting value on its result OutputPin.

Visit also

Visit also (backlinks)

Related slides (includes other tutorials)

UML2 Activity Diagram - essential metaclasses - ADVANCED REFERENCE ONLY

UML2 Actions - metaclasses - ADVANCED REFERENCE ONLY

Related slides (backlinks, includes other tutorials)

SysML Activity extension stereotypes - REFERENCE CARD

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

Flags