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.

This page identifies a possible issue, inconsistency, concern, error, or bug!
One of the ways Webel IT Australia helps promote tools, technologies, and languages is by donating a lot of time identifying, tracking, and reporting potential issues, in order to help vendors and developers improve the tools and technologies. In some cases, we also offer workarounds and advice for users. All issues tracked on our public site are offered most constructively and with sincerest gratitude to the tool vendors and technology developers.
DISCLAIMER: Vendors do not officially endorse issue analysis by Webel IT Australia.
Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
GOTCHA
ISSUE
TOOL
Policy level
INFORMATIVE
Specification keywords
SysML-1.6
SysML-1.7
UML keywords
NamedElement::name
Action
CallBehaviorAction
Property
element property
Note
SysMLv1.x keywords
Allocate
ActivityAllocatePartition
allocation
SysML callout style
Keywords
Click on the image to view it full size
The usual Webel Best Practices for SysML recommendation is to use anonymous block properties and anonymous actions where possible:
Webel Best Practice: SysML: Webel: "Trust the Type!" - Often the name of the Type of an anonymous Property or instance-level element is completely sufficient to indicate its role - unless multiple Properties of the same Type have different roles within the same owner context!
Webel Best Practice: 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).

One place this causes a minor display problem in the MagicDraw/Cameo tool is in Element Properties for 'allocateTo' and 'allocatedFrom' in compartments and in callouts to Notes when usage level allocation from CallBehaviorActions to part properties of a Block is being used, in which case it may not be clear which elements are involved in the allocation.

The display option Show Element Type in compartments does not actually show the Type (for allocatedTo) or the Behavior (for allocatedFrom) for anonymous elements for Note callouts or Element Properties compartments

For the sake of comparison, the Element Compartments are using SysML Callout Style and the Note callout is not.

In practice, it's not a big issue, and certainly not sufficient to overrule the benefits of using anonymous actions and anonymous properties (where practical). You can use the context menu items to navigate in the tool. And in any case, Allocate tables and matrices offer a better bigger picture view anyway.

Relates to
Related notes
[NAMING, POLICY]{STRONG} "Trust the Namespace" - DO NOT repeat information in names of owned elements that can be gleaned from the owner or ancestor (and is usually easily shown using display options). It is WET, it breaks the DRY principle!
[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).
[NAMING, POLICY]{STRICT} SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase
[NAMING, POLICY, STYLE]{STRONG} SysML: Webel: "Trust the Type!" - Often the name of the Type of an anonymous Property or instance-level element is completely sufficient to indicate its role - unless multiple Properties of the same Type have different roles within the same owner context!
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)