Keywords
The Webel Best Practice items for SysMLv1 (and for supporting UML2) - 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 SysMv1.
Looking for the Webel Best Practices for the newer SysMLv2? Go here!
Dr Darren says:
In order to improve your way, you have to first have a way!Yes, you've arrived at the right place! Learn how to do Model-Based Systems Engineering and model-based graphical software engineering, surgically, methodically, reliably, systematically, and most enjoyably, from Dr Darren, the MagicDraw® UML (aka Magic Software Architect), MagicDraw SysML Plugin, and Magic Cyber-Systems Engineer® (Cameo Systems Modeler®) graphical engineering wizard.
These Webel Best Practice tips really work! They have been refined over decades and have been used on major engineering projects such as neutron beam instruments, radio telescopes, optical telescopes, astronomical instrument projects, particle accelerators, large scale building and construction projects, green building schemes, health informatics, electronics, air conditioners, designing of inventions, and for modelling and encapsulating all sorts of systems from industry and science.
Each Webel Best Practice Note page is linked to annotated diagram Slide examples showing exactly the DOs and DON'Ts. And they are of course tuned to work together with the amazing Webel Parsing Analysis recipe for SysMLv1.
And please note:Learn more about SysMv1 for MBSE at our unique hands-on workshop course (still available and for years to come)
NEW: Policy note overview pages by topic
Webel's Best Practice items index (mostly SysML1.x and some supporting UML2)
Currently NOT ordered or prioritised. The format is:
[NOTE_TYPE_TAG, ...]{POLICY_LEVEL_TAG} LINKED_TITLE
You can also use this filtered search through all Notes on this site.
- [DISPLAY, POLICY, SETTINGS, STYLE, TOOL]{STRONG} Webel: SysMLv1: Symbol colour styles: Recommend use black symbol borders and no symbol fill (or white symbol fill) EXCEPT for special highlighting. Recommend DO NOT use the default VENDOR-SPECIFIC line and fill colours for symbols! [TIP IS MOSTLY IGNORED]
- [ASSERTION, DISPLAY, FEATURE, MODELLING, SETTINGS, TIP, TOOL]{STRONG} Webel: MagicDraw/Cameo: Set EVERY element properties & symbol properties filter to 'All' (yes, not just 'Expert', to 'All', even if you are a "novice" on your first project) in EVERY dialog and every project option setting. Use the search filters!
- [ASSERTION, DISPLAY, FEATURE, MODELLING, SETTINGS, TIP, TOOL]{STRONG} Cameo/MagicDraw: The Classifier specification setting 'isAbstract' is (for reasons that beggar belief or engineering reason) not by default visible in the Element specification dialog. Enable expertise level 'All' (and for always everwhere).
- [CONVENTION, MODELLING, NAMING, TIP]{RECOMMENDED} Webel: SysML: Use concise Package and Model naming to provide "context aware" owner paths that reflect a systems engineering strategy. Extremely so-called "human friendly" verbose Package/Model names with spaces DO NOT make the model easier to understand!
- [MODELLING, NAVIGATION, PATTERN, TIP, TOOL]{STRONG} Webel: UML/SysML: Navigation: ALWAYS offer a way out of a diagram (usually up a hierarchy, but possibly across) using a navigable symbol (linked to a diagram) and/or a diagram symbol. Avoid "cul-de-sacs"! [But beware of shared package cross-dependencies]