SysMLv1: When using model queries (such as tables) for compliance with some older systems engineering docs you may not always be able to use anonymous Property names and anonymous instance level element names. Or try the owner context or the ID!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
CAVEAT
Policy level
OPTION
Keywords

Often in query view reports including a column with the owner context is completely adequate, and in MagicDraw/Cameo you can even include the generated Element ID.

Dr Darren says:
The documentation requirements of some older "obligatory" pre-MBSE systems engineering methodologies address problems that simply don't exist anymore with modern SysML for MBSE and Single Source of Truth (SSOT) systems!

Names like longTypeName for a Property typed by LongTypeName are not useful; use short role indicators names when there is more than one Property of the same Type in the one owner context, otherwise, unless you have very special report extraction requirements, anonymous Properties are your modelling friend:

In SysMLv1, whenever and wherever you can, always "Trust The Type" to do the talking for the Property!

Visit also some cross-linked examples here:

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!

And a full discussion here:

Webel: SysMLv1: Dr Darren for LinkedIn: On "Trusting The Type" and avoiding unnecessary verbose repetitive Property names ... unless you really, really need them and really do have reasons to use them, and then only use concise role indicators anyway!
Relates to
Related notes
[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
[ASSERTION]{STRONG} Webel: Dr Darren says: "Many aspects of older Document-Intensive Systems Engineering methodologies and the reporting obligations they impose on their users were intended to address problems that simply DO NOT EXIST ANYMORE with modern MBSE with SysML!"
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)