Figure D.36 - Behavior Model for “Accelerate” Function (Activity Diagram) {ELIDED PINS}

This trail version uses "elided Pin notation", it does not show explicit Pins on PushAccelator, MeasureVehicleConditions, and ProvidePower, so it encounters this well known tool issue:

MagicDraw/Cameo: ERROR: Incorrectly uses 2 ObjectFlow edges and a CentralBufferNode in place of "elided Pin notation" instead of an abstract ObjectNode symbol and 2 arrow symbols (that are supposed to represent together 2 Pins and 1 ObjectFlow edge)

(The version here does, like the spec figure, show explicit output Pins on ProvidePower.) For a version using explicit Pins please visit the next slide.

In the spec version, the Parameter of the ActivityParameterNode drivePower should be set to be streaming, consistent with:

SysML-1.6: Each «continuous» Parameter (of each corresponding ActivityParameterNode) in Figure D.36 and Figure D.38 should be set to be streaming, because the Continuous Stereotype has a Generalization to Rate

SysML-1.6: 'Rate ... When the stereotype is applied to a parameter, the parameter shall be streaming, and the stereotype gives the number of objects or values that flow in or out of the parameter per time interval while the behavior or operation is executing.'

SysML-1.6: '1_streaming When the «rate» stereotype is applied to a parameter, the parameter shall be streaming.'

This is has been done in this trail version, and the setting appears also on the symbol for the ActivityParameterNode as {stream}.

And the same works for the drivePower OutputPin:

MagicDraw/Cameo: If the underlying Parameter of an InputPin or OutputPin on a CallBehaviorAction or CallOperationAction is set to streaming, the indicator {stream} optionally displays on the Pin

The SysML-1.6 spec does not - according to the figures and table (but does in the XMI) - permit Rate, Continuous, or Discrete to be applied to an ObjectNode like Pin and or ActivityParameterNode.

In the MagicDraw/Cameo tools this is not a problem for ActivityParameterNode:

MagicDraw/Cameo 19SP3: if Continuous or Discrete are applied to the Parameter of an ActivityParameterNode the keywords «continuous» or «discrete» can be optionally displayed on the ActivityParameterNode symbol

But it is a problem for Pins. The tool can't (it seems) show the «continuous» keyword from the underlying Parameter:

MagicDraw/Cameo 19SP3: If Continuous or Discrete are applied to the underlying Parameter of an InputPin or an OutputPin the keywords «continuous» or «discrete» can't be displayed

But does seem to have a workaround, which has been used in the trial diagram here:

MagicDraw/Cameo 19SP3: Continuous and Discrete have metaclass [ActivityEdge, ObjectNode, Parameter] not just [ActivityEdge, Parameter] (via Rate), so may be applied directly to Pin and ActivityParameterNode

To mimic the spec figure, the Name Display Mode for the CallBehaviorAction symbols is set here to 'Show Behavior Name', but that is not Webel Best Practice:

Webel: SysMLv1/UML: Prefer the Name Display Mode 'both' on CallBehaviorAction symbols (rather than 'Show Action Name', 'Show Behavior Name', or 'Show Both or Behavior Name')

Up next

Figure D.36 - Behavior Model for “Accelerate” Function (Activity Diagram) {EXPLICIT PINS}

Notes

[NAMING, VARIATION] The Webel trail versions of the Activity Diagrams D.36 and D.38 use the name 'transMode' for the output Parameter and corresponding ActivityParameterNode (consistent with the spec figure D.38) NOT 'transMode_imported' (as in spec figure D.36)

[ISSUE, TOOL] MagicDraw/Cameo: ERROR: Incorrectly uses 2 ObjectFlow edges and a CentralBufferNode in place of "elided Pin notation" instead of an abstract ObjectNode symbol and 2 arrow symbols (that are supposed to represent together 2 Pins and 1 ObjectFlow edge)

[ISSUE, TOOL, WARNING] MagicDraw/Cameo: DO NOT use the ObjectNode menu item on Activity Diagrams ever!

[DISPLAY, ISSUE, TOOL, WARNING] Webel recommends when using MagicDraw/Cameo: AVOID the "elided Pin" abstract ObjectNode notation on Activity Diagrams, use explicit Pins!

[ISSUE] SysML-1.6: Each «continuous» Parameter (of each corresponding ActivityParameterNode) in Figure D.36 and Figure D.38 should be set to be streaming, because the Continuous Stereotype has a Generalization to Rate

[ISSUE] MagicDraw/Cameo 19SP3: Continuous and Discrete have metaclass [ActivityEdge, ObjectNode, Parameter] not just [ActivityEdge, Parameter] (via Rate), so may be applied directly to Pin and ActivityParameterNode

[DISPLAY, TOOL] MagicDraw/Cameo: If the underlying Parameter of an InputPin or OutputPin on a CallBehaviorAction or CallOperationAction is set to streaming, the indicator {stream} optionally displays on the Pin

[DISPLAY, FEATURE, TIP, TOOL] MagicDraw/Cameo 19SP3: if Continuous or Discrete are applied to the Parameter of an ActivityParameterNode the keywords «continuous» or «discrete» can be optionally displayed on the ActivityParameterNode symbol