Webel: SysML/UML: Dr Darren explains HOWTO use concise 'i'/'o' (input/output) Pin and Parameter naming conventions to promote a signal processing mindset in Activity Diagrams. And HOWTO get them compact.
The type, ordering, and multiplicity of the argument and result pins of a CallAction shall be the same as the corresponding Parameters. Source Unified Modeling Language 2.5.1
The argument Pins of a CallAction are matched, in order, to the sublist of input Parameters, while the result Pins are matched, in order, to the sublist of output Parameters. Source Unified Modeling Language 2.5.1
Behaviors and Operations have totally ordered lists of owned Parameters, and these Parameters are matched to Pins on a CallAction using that ordering. Source Unified Modeling Language 2.5.1
If the input object is an instantiated Behavior that is not already executing, then it begins executing. If the input object has a classifierBehavior that is not already executing, then it is instantiated and started. In either case ... Source Unified Modeling Language 2.5.1
A StartObjectBehaviorAction is a CallAction that starts the execution either of a directly instantiated Behavior or of the classifierBehavior of an object. The object to be started is taken from the object InputPin. Source Unified Modeling Language 2.5.1
A CallOperationAction is a CallAction that transmits an Operation call request message to the target object, where it may cause the invocation of an associated Behavior. The target object is taken from the target InputPin of the CallOperationAction. Source Unified Modeling Language 2.5.1
A CallBehaviorAction is a CallAction that invokes a Behavior directly, rather than calling a BehavioralFeature that, in turn, results in the invocation of a Behavior. Source Unified Modeling Language 2.5.1
A CallAction is an InvocationAction that calls a Behavior or an Operation. There are three kinds of CallActions Source Unified Modeling Language 2.5.1
