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

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
UML keywords
Activity
Behavior
Action
Pin
ActivityEdge
ObjectFlow
ObjectNode
CentralBufferNode
ActivityParameterNode
Parameter
ForkNode
MergeNode
InitialNode
FinalNode
CallBehaviorAction
elided Pin notation
Parameter::isStreaming
SysML keywords
SysML Activity Diagram
«continuous»
Continuous
Rate
Slide kind
SysML Activity Diagram
A version of Figure D.36 with explicit Pins, thus avoiding this 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)
Click on the image to view it full size
For comparison, this trail diagram version uses the Name Display Mode 'Both' for the CallBehaviorAction symbols:

Prefer the Name Display Mode 'both' on CallBehaviorAction symbols (rather than 'Show Action Name', 'Show Behavior Name', or 'Show Both or Behavior Name')
That many of the Pins are both «continuous» and {stream} is implied by later diagrams such as Figure D.38.
Up next
Figure D.37 - Decomposition of “Accelerate” Function (Activity and Object Flow Breakdown)
Notes
[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, TOOL] [BUG: FIXED]: MagicDraw/Cameo SP193: Offers the display option to show the name and type label inside a Pin symbol, but it does not seem to work. [FIXED since 2022xRefresh2]
[NAMING, POLICY]{STRONG} Prefer anonymous Actions, or if they must be named, prefer code-like 'lowerCamelCase' or completely 'lower case' (if you do absolutely insist on having spaces in action names, but please no other punctuation).
[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
[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
[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
Snippets (quotes/extracts)
  [SysML-1.6] Figure D.36 shows the top level behavior of an activity representing acceleration of the HSUV.
  [SysML-1.6] 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.
  [SysML-1.6] 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).
  [SysML-1.6] Continuous rate is a special case of rate of flow (see Rate) where the increment of time between items approaches zero. It is intended to represent continuous flows that may correspond to water flowing through a pipe, a time continuous signal, or ...
  [SysML-1.6] Continuous ... It is independent from UML streaming, see clause 11.3.2.8. A streaming parameter may or may not apply to continuous flow, and a continuous flow may or may not apply to streaming parameters.
  [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.
Visit also
Visit also (backlinks)
The stereotype applies to all parameters corresponding to the pins notated by the object node.
Stereotypes applying to parameters can appear on object nodes in activity diagrams, as shown in Figure 11-7, when the object node notation is used as a shorthand for pins.
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)