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

Gallery
Tutorial
Click on the image to view it full size
The Comment in the spec figure incorrectly refers to 'PwrSubSystem'
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:

(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:

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:

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:

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

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

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:

Up next
Notes
Snippets (quotes/extracts)
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)