Learn about Webel IT's new SysMLv2/MBSE Workshop Seminar course!
VIDEO: The Webel SysMLv2/MBSE course has landed! Take a quick tour!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!

The Action execution consumes input data on all InputPins on the Action up to the upper multiplicity for each InputPin.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Starting an Action that has an InputPin with multiplicity
Starting an Action that has a ControlPin
Starting an Action that has a ValuePin - LIMITED SUPPORT
UML2 Types of Pins - metaclasses
Source
Unified Modeling Language 2.5.1
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
UML keywords
Activity
Activity Diagram
Action
execution
InputPin
Action::/input
MultiplicityElement::/upper
Full quote
The Action execution consumes input data on all InputPins on the Action up to the upper multiplicity for each InputPin.
Next snippet
For structured Actions (StructuredActivityNodes ... ), data can remain on InputPins during Action execution, otherwise they are immediately removed from the InputPins by the ActionExecution.
Related snippets
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.
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.
When completed, an Action execution provides any output data on the OutputPins of the Action, and it terminates.
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 ...
Related snippets (backlinks)
For structured Actions (StructuredActivityNodes ... ), data can remain on InputPins during Action execution, otherwise they are immediately removed from the InputPins by the ActionExecution.
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
Visit also
Visit also (backlinks)