If the Action is an invocation of a Behavior with streaming Parameters ... the Action execution may consume additional data supplied to InputPins corresponding to streaming input Parameters ... Otherwise ... any additional data on InputPins has no effect Source Unified Modeling Language 2.5.1
For structured Actions (StructuredActivityNodes ... ), data can remain on InputPins during Action execution, otherwise they are immediately removed from the InputPins by the ActionExecution. Source Unified Modeling Language 2.5.1
The Action execution consumes input data on all InputPins on the Action up to the upper multiplicity for each InputPin. Source Unified Modeling Language 2.5.1
However, if the Action is an invocation of a Behavior with streaming Parameters ... then the Action execution may also post data to OutputPins corresponding to streaming output Parameters before completion of the execution ... Source Unified Modeling Language 2.5.1
When completed, an Action execution provides any output data on the OutputPins of the Action, and it terminates. Source Unified Modeling Language 2.5.1
An Action continues executing until it has completed. The detailed semantics of the execution of an Action and the definition of its completion depend on the particular kind of Action being executed. Source Unified Modeling Language 2.5.1
The time at which an Action executes and what inputs are accepted by each execution are determined by the kind of Action it is, characteristics of its InputPins, and the Behavior in which it is used. Source Unified Modeling Language 2.5.1
When an Action in an Activity completes execution, object tokens for output data placed on its OutputPins may be offered on any outgoing ObjectFlows from those Pins ... In addition, control tokens shall be offered on any outgoing ControlFlows ... Source Unified Modeling Language 2.5.1
When the Action is enabled by other means, values are computed as specified for the ValuePins and ActionInputPins owned by an Action, and the results are provided as inputs to the Action when it begins execution. Source Unified Modeling Language 2.5.1
ValuePins and ActionInputPins are InputPins, but are not used in the determination of whether an Action is enabled for execution. If an Action has no other way to start execution, simply having ValuePins or ActionInputPins for its inputs will not enable.. Source Unified Modeling Language 2.5.1
An Action may not put more values into an output in a single execution than the [upper] multiplicity of that OutputPin. Source Unified Modeling Language 2.5.1
For each execution, an Action cannot terminate itself unless it can put at least as many values into its outputs as required by the multiplicity lower bounds on those OutputPins. Values that may remain on the OutputPins from previous executions are not... Source Unified Modeling Language 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 ...) Source Unified Modeling Language 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. Source Unified Modeling Language 2.5.1
An Action cannot start execution if one of its InputPins has fewer values than the lower multiplicity of that InputPin. Source Unified Modeling Language 2.5.1
ControlFlows are used to explicitly sequence execution of ActivityNodes, as the target ActivityNode cannot receive a control token and start execution until the source ActivityNode completes execution and produces the token. Source Unified Modeling Language 2.5.1
An ExecutableNode is an ActivityNode that carries out a substantive behavioral step of the Activity that contains it. Source Unified Modeling Language 2.5.1
Generally, the ControlNodes and ObjectNodes in an Activity are largely there to control the sequencing and to manage the flow of data between the ExecutableNodes of the Activity. Source Unified Modeling Language 2.5.1
An ExecutableNode is a kind of ActivityNode that may be executed as a step in the overall desired behavior of the containing Activity. Source Unified Modeling Language 2.5.1
The Driving behavior outputs a brake pressure continuously to the Braking behavior while both are executing, as indicated by the «continuous» rate and streaming properties (streaming is a characteristic of UML behavior parameters that supports ... Source OMG Systems Modeling Language (SysML) 1.6
Streaming is a characteristic of UML behavior parameters that supports the input and output of items while a behavior is executing, rather than only when the behavior starts and stops. The flow may be continuous or discrete ... Source OMG Systems Modeling Language (SysML) 1.6
One or more result values may be posted to a streaming output Parameter any time after the invocation of a Behavior up to or at its completion. These result values are then available to affect the further course of the execution of the invoking Behavior.. Source Unified Modeling Language 2.5.1
If an output Parameter is streaming, then a Behavior execution may provide result values for the Parameter during its course rather than just at completion. Source Unified Modeling Language 2.5.1
One or more argument values may be posted to a streaming input Parameter at or any time after the invocation of a Behavior and before its completion. These argument values are then available to affect the further course of the Behavior execution ... Source Unified Modeling Language 2.5.1
If an input Parameter is streaming, then argument values may be provided for the Parameter during the course of a Behavior execution rather than just at invocation. Source Unified Modeling Language 2.5.1
Parameters may also be marked as streaming (i.e., have the isStreaming property be true). Such Parameters allow values to be passed into and out of a Behavior execution any time during its course, rather than just on invocation and completion. Source Unified Modeling Language 2.5.1
... a copy is made of the removed object token, with the same value, and this is immediately placed back onto the DataStoreNode. Thus, the values held by a DataStoreNode appear to persist for the duration of each execution of its containing activity, even Source Unified Modeling Language 2.5.1
When the Activity is invoked, values may be passed into the Activity execution on input Parameters (i.e., those with direction in or inout) and values may be passed out .. on output Parameters (i.e., those with direction inout, out or return). Source Unified Modeling Language 2.5.1
If a matching Event occurrence for an AcceptEventAction is dispatched from the event pool, then the AcceptEventAction is enabled to continue. However, if the containing Behavior execution has more than one waiting Trigger that matches ... Source Unified Modeling Language 2.5.1
The context object for an AcceptEventAction is the context object of the Behavior execution within which the AcceptEventAction is executing (which may be the Behavior execution itself ...) Source Unified Modeling Language 2.5.1
