It is the intent of the systems engineer in this example to allocate this behavior to parts of the PowerSubsystem. It is quickly found, however, that the behavior as depicted cannot be allocated, and must be further decomposed.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Figure D.36 - Behavior Model for “Accelerate” Function (Activity Diagram) {ELIDED PINS}
Figure D.36 - Behavior Model for “Accelerate” Function (Activity Diagram) {EXPLICIT PINS}
Source
OMG Systems Modeling Language (SysML) 1.6
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
EXAMPLE
INFO
UML keywords
Activity
Behavior
Keywords
Figure D.36 shows the top level behavior of an activity representing acceleration of the HSUV.
Full quote
It is the intent of the systems engineer in this example to allocate this behavior to parts of the PowerSubsystem. It is quickly found, however, that the behavior as depicted cannot be allocated, and must be further decomposed.
Next snippet
The stereotypes on the object nodes between actions in the figure apply to parameters of the behaviors or operations called by the actions (see the notation for object nodes described in 11.3.1.4, ObjectNode, Variables, and Parameters).
Related snippets
Figure D.36 shows the top level behavior of an activity representing acceleration of the HSUV.
Related snippets (backlinks)
Visit also
Visit also (backlinks)