Webel: SysML: DO NOT sacrifice modelling naming conventions for the mere sake of carrying organisation-specific names! Instead use tagged values of custom stereotypes as metadata to carry alternative names in parallel with systematic model element names.

Icon class
far fa-sticky-note
far fa-sticky-note
Note kind
Policy level
Specification keywords
UML keywords

For example, you can use the custom stereotype Term with keyword «term» and tagged values such as 'localName', 'ourName', 'ourId' etc. (where 'our' of course might instead reference your organisation).

Dr Darren says:
This is one of the most important tips for fluent, enjoyable Model-Based Systems Engineering (MBSE) with SysML on this entire site! I use this approach all the time, have for years, and it works. It also DOES communicate to stakeholders fine. Try to use organisation-specific names directly on model element names throughout your model (instead of systematic ones like the Webel Best Practice items) and all you will get is a complete mess. It will NOT be easier for others to read. And you will sacrifice a heap of modelling power. Don't do it!
The Webel Best Practice items for SysML (and 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)