TIP: Webel: SysML/UML: On the boundary of Action symbols in Activity Diagrams use any placement or "ordering" of Parameter symbols that works for the diagram. Ignore the Parameter ordering of Operation and Behavior signatures completely!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
MODELLING
TIP
Policy level
RECOMMENDED
UML keywords
Activity Diagram
Action
Activity
Behavior
Parameter
Operation
ActivityParameterNode
SysMLv1.x keywords
SysML Activity Diagram
Keywords

Activity Diagrams are 2-dimensional, and the placement (or "ordering") of Parameter symbols on the boundaries of Action symbols - and of ActivityParameterNode symbols on the framed boundary of the Activity context itself - need not be bound in any way by the ordering of the Parameters (arguments) of any related Operation or Behavior. They are completely different ways of thinking!

In MagicDraw SysML Plugin and Magic Cyber-Systems Engineer ® (Cameo Systems Modeler®) you can order Parameters on an Operation or Behavior using the specification dialog; such a 1-dimensional ordering need not have any bearing at all on how you organise the representation of those Parameters as symbols in a 2-dimensional Activity Diagram. None at all.

Dr Darren says:

Take advantage of 2-dimensional SysML and UML diagrams to represent networks and flows as best fits the modelling purpose.

For an example, visit:

SysML4Mathematica: Example 11 [B]: Total (qDotTot), sensible (qDotSen), and latent cooling (qDotLat) required for cooling air: Using Webel MPsy objects and SysML Activity Diagrams
Relates to
SysML4Mathematica: Example 11 [B]: Total (qDotTot), sensible (qDotSen), and latent cooling (qDotLat) required for cooling air: Using Webel MPsy objects and SysML Activity Diagrams
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)