[STUB] TRAIL: Webel's ultimate guide to simplified yet adequate pragmatic systems engineering with functional analysis in SysMLv1 for smaller scale MBSE projects in the MagicDraw/Cameo/CATIA Magic tools

Icon class

icon_class_computed

fas fa-chalkboard-teacher

Quick start

Webel SE: pragmatic tool-friendly functional analysis: 2-level drill-down from a single Use Case via a «scenario» Activity with allocation to «logical» subsystems first then crossing to the «design» Blocks zone.

Keywords

Every heard that you "should" be using at least some classic systems engineering functional analysis and logical breakdown of blackbox vs whitebox and associated logical components (have many names) to describe WHAT your system should do before designing exactly HOW it is done and by which design (or implementation) components, but the full defence frameworks like MoDAF and DODAD, or frameworks like ToGAF or UAF are massive overkill for your projects?

Tried MagicGrid®, learned a lot from it, but found it a bit clunky and inflexible?

Or maybe you already have some SysML modelling of an existing design or implementation and you wish to "retrofit" your SysML model with some improved traceability from stakeholder needs through a simplified operational view with cleaner separation of the problem and solution modelling.

Then this new Webel IT Australia guide is for you! A truly slick minimalist recipe for including at least some classic systems engineering in MagicDraw/Cameo, with concise Webel style naming and Webel Best Practices for SysML modelling.

WORK-IN-PROGRESS: MORE COMING SOON!

This is so far mostly just a list of Webel policies and modelling and naming conventions supporting the Webel recipe for pragmatic SE with SysML. Full tutorial coming soon! Many of the linked Note page already have detailed Diagrams and explanations.

While you are waiting you might like to visit this:

HOWTO "cheat" with two-level white-boxing and tracking stereotypes because you just don't want that darn "extra" logical subsystem (conceptual subsystem) Block the systems engineers reckon you are supposed to use (and why it's easier to actually use one)

The Webel recipe for pragramatic SE with SysML omits many of the concerns addressed by fully-fledged systems engineering frameworks. Many of these can be partially addressed by using custom Stereotypes for extraction using query view tables.

Webel Best Practice: Webel: SysML: SE: Naming convention: '0' used for a Package/Model name indicates a zone dedicated to a formal systems engineering breakdown (functional analysis, blackbox, whitebox, logical vs design or implementation etc.)

The Webel recipe for pragramatic SE with SysML adopts the MagicDraw/Cameo tool friendly approach of using a SystemContext as 'subject' of top-level UseCases (although using a System as 'subject' can also be used).

Webel Best Practice: Webel: SysML: SE: Stereotype keyword convention: BY DEFINITION HERE «blackbox» and «whitebox» refer specifically to the 'problem' zone and NEVER the 'solution' zone (as opposed to more general uses of the terms 'black-box' and 'white-box').

Webel Best Practice: Webel: SysML: SE: «blackbox»: The custom Stereotype keyword «scenario» indicates a Behavior (Interaction as Sequence Diagram or Activity) that Refines a top-level UseCase within the 'problem' zone.

Webel Best Practice: Webel: SysML: SE: The custom Stereotype keyword «whitebox» applied to an Activity indicates that it is part of the functional analysis breakdown serving a «whitebox» «scenario» Activity (directly or indirectly) for a UseCase.

Webel Best Practice: Webel: SysML: SE: Naming convention: «whitebox»: A '$' prefix indicates a «logical» system, «logical» subsystem (aka conceptual subsystem) or «logical» handler Block (which is a more specific form of «logical» subsystems Block).

Webel Best Practice: Webel: SysML: SE: Terminology: '«logical» handler' is used for a specific kind of «logical» subsystem (aka 'conceptual subsystem') that is a SPECIFIC collaboration of parts that handle one Activity usage in a higher level «whitebox» Activity.

Webel Best Practice: Webel: SysML: SE: The custom stereotype keyword «design» covers elements involved with BOTH design and/or implementation aspects in the 'solution' zone. (In more comprehensive SE methodologies design and implementation are often treated separately.)

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!

Visit also: Webel: SysMLv1: Functional analysis (isolation of white-box Activities identified via «blackbox» scenario Activities of UseCases). Recommend custom stereotype them. Candidate: «whitebox» (or a recommended SE methodology stereotype).

Visit also: Webel: SysMLv1: Overview of annotated Diagram Slides and Note pages related to UseCases and their combination with a System (of interest), SystemContext, and drill-down to scenario Sequence Diagrams (Interactions) and Activity Diagrams.

Visit also: List of some formal systems engineering methodologies, standards, and guides [EXTERNAL LINKS]

Start here

Sections

Slides in this trail

If you want to navigate the entire tutorial including the additional explanatory text, click on the title link of the first slide to view the full slide page, then use the next links to move through the slides pages. If you just want to view the slide images only in sequence, click on any slide to view it larger in a viewer, then click again to move through each slide in the tutorial trail.

Learn SysML for MBSE with the Webel IT Australia Live Online web seminar or On-Site course!

Please email or phone Webel IT Australia on +61 405 029 008 to arrange On-Site, Off-Site, or Live Online remote web training seminars and workshops.

Course: Model-Based Systems Engineering with the OMG's Systems Modeling Language® (v1) and the SysML Plugin for MagicDraw® and Cameo™ (CATIA Magic)