Webel: SysML: "Really long human friendly element names with spaces make my diagrams easier to read". Dr Darren says "No they don't! Prefer code-like naming (or anonymous for typed elements) wherever possible. Use custom tagged values for other names!"

Icon class
far fa-sticky-note
far fa-sticky-note
Note kind
Policy level
Specification keywords
UML keywords
Dr Darren of Webel IT Australia hears you say:
"But really long human friendly element names with spaces make my Diagrams easier to read".
Dr Darren says:
"No they don't! Prefer code-like naming conventions and adopt anonymous for typed elements wherever possible. Use tagged values METADATA for carrying "human friendly" names to optionally display on symbols on Diagrams! Pull that "human-friendlier" METADATA out in table view queries!"
By using long so-called human-friendly names in Blocks and Package names (in particular) you are completely undermining a heap of really powerful modelling strategies that leverage short names (no spaces) to provide semantic context and ownership context efficiently. Anyone who tries to convince you otherwise is proving one thing to me:
They haven't yet discovered some of the most powerful SysML/MBSE modelling strategies used in the Webel modelling recipe for SysML!

Such as this:

Do the advocates of so-called "human friendly" extremely long SysML element names have a set of tried-and-tested well recording policies like the Webel Best Practices for SysML policy note pages in this site (cross linked to many examples)? No. Are their SysML diagrams as nice and compact and presentable and legible as the Webel ones? No. Can they model as quickly and as efficiently in SysML as I do with the Webel approach? No. Tried it out on heaps of real world SysML for MBSE projects for decades? Mostly, no. Do they make examples of their SysML modelling of truly substantial real world problems and domain realistic models available in public like the Webel IT Australia site? Mostly, no.

Do the advocates of such cluttering long verbose so-called "human friendly" naming have an actual recipe for traceable elicitation of SysML model elements such as the  Webel Parsing Analysis recipe for SysML®? Very likely no.

Really long element names with spaces also run the risk of becoming too WET not DRY

As for the argument that such verbose naming is required for alignment with older pre-MBSE systems engineering methodologies:

You can progressively introduce Webel-style concise naming!

In any case, the naming conventions of the Webel Best Practices for SysML can be adopted incrementally, and thanks to the wonders of Single Source Of Truth modelling with SysML (with propagation of changes throughout all Diagrams), they can be introduced selectively if and as and when you wish with incremental benefit:

Please be aware also that the SysML spec figures and sample problems are NOT intended to act as "templates" for modelling in SysML! And the authors have special pedagogical reasons for including some quite verbose naming and adornments in those figures:

The Webel Best Practice items for SysML (and for supporting UML) - tuned for the MagicDraw/Cameo tools - represent the world's most comprehensive guide to robust, fluent, enjoyable, consistent modelling for Model-Based Systems Engineering (MBSE), developed over two decades, and proven to work on extremely demanding real-world projects! Learn more by attending the Webel IT Australia course for MBSE with SysML.
Visit also:
Relates to
Related notes
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)