Figure D.37 - Decomposition of “Accelerate” Function (Activity and Object Flow Breakdown)

Gallery

Tutorial

TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]

Section

Section: SysML-1.6: HSUV sample

Tags and keywords

UML keywords

Activity

SysML keywords

SysML Block Definition Diagram

Block

Slide kind

SysML Block Definition Diagram (BDD)

Click on the image to view it full size

SysML-1.6: The spec version of Figure D.37 does not show the breakdown from the top-level Accelerate activity

It is included in this trail diagram version. There are some naming differences here (consistent with the Actions in the Activity Diagram here): pa:PushAccelerator , mvc:MeasureVehicleConditions, pp:ProvidePower. The Property correspond with the spec's ActivityParameterNode transModeCmd_imported:ModeCmd is just called transModeCmd:ModeCmd.

Up next

Figure D.38 - Detailed Behavior Model for “Provide Power” {ELIDED PINS}

Notes

[ISSUE] SysML-1.6: The spec version of Figure D.37 does not show the breakdown from the top-level Accelerate activity

Snippets (quotes/extracts)

[SysML-1.6] Figure D.37 defines a decomposition of the activities and objectFlows from the activity diagram in Figure D.36.

[SysML-1.6] Associations can be used between activities and classifiers (blocks or value types) that are the type of object nodes, variables, or parameters in the activity, as shown in Figure 11-5.

[SysML-1.6] Activities as blocks can have associations between each other, including composition associations. Composition means that destroying an instance at the whole end destroys instances at the part end.