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).

Icon class

icon_class

far fa-sticky-note

icon_class_computed

far fa-sticky-note

Note kind

Policy level

UML keywords

Keywords

UML
SysML

The usual Webel Best Practices for SysML recommendation is to 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).

And remember, for a CallBehaviorAction you can always just "Trust The Type" and show the Behavior name if there is only one action for that Behavior in a particular owning Behavior/Activity context.

However, one area this can cause minor display issues in the MagicDraw/Cameo tool is in Note callouts and Element Property compartments when usage level allocation mode is used:

Webel: SysMLv1: MagicDraw/Cameo: CON: Using anonymous property and/or action names is not ideal for Element Compartment and Note callout displays when Usage level allocation is used. But allocation table and matrix views are better anyway.

SysML/SysPhS-1.1: Anonymous Property or Action names may not be an option if: You are exporting to Modelica or Simulink; You absolutely need names for generated query reports (such as generated Interface Control Documents).

Relates to

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

Figure 15-4: Behavior Allocation

Figure 15-5: Example of flow allocation from ObjectFlow to Connector

Figure 15-6: Example of flow allocation from ObjectFlow to ItemFlow

Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty

Related notes