The sole mechanism for asynchronous invocation in fUML is via send signal action. This can be used to achieve the effect of broadcasting and sending objects.
Variables are excluded from fUML because the passing of data between actions can be achieved using object flows.
184.108.40.206 ActivityEdge  fuml_activity_edge_allowed_guards A guard is only allowed if the source of the edge is a DecisionNode.
ValuePin – Value pins are excluded from fUML because they are redundant with using value specifications to specify values.
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 ...
The values on such object tokens may be used to affect the control of ExecutableNodes that are the targets of such ControlFlows, though the specific meaning of such values is not defined in this specification
Figure D.19 shows how the parts of the PowerSubsystem block, as defined in the diagram above, are used. It shows connectors between parts, ports, and connectors with item flows.
The dashed borders on FrontWheel and BrakePedal denote the “use-not-composition” relationship depicted elsewhere in Figure D.16 and Figure D.18.
The dashed borders on Fuel denote a store, which keeps track of the amount and mass of fuel in the FuelTankAssy. This is also depicted in Figure D.18.
A part or shared association has a default multiplicity of [0..1] on the black or white diamond end. A unidirectional association has a default multiplicity of 1 on its target end.