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.

The Webel recipe for pragmatic SE with SysML is intended primarily to pragmatically introduce at least some separation of logical «blackbox» and «whitebox» modelling within a 'problem' analysis zone from design and implementation solution modelling within a separate 'solution' zone. For example:

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.)

The Webel recipe for pragmatic SE with SysML is NOT a fully-fledged systems engineering architecture framework. It intended for educational illustration of concepts such as logical subsystems and functional analysis and for use on relatively simple projects using SysML for MBSE.

It omits explicit treatment of all of the following, although these concerns can also by included: the SE architecture itself (in UAF terminology Architecture Management), strategic and capability management, separate service-oriented views, personnel, other enabling resources, security aspects and assets, project milestones and roadmaps, separate standards views, motivational elements, taxonomies.

Many of the above can be addressed on simpler projects pragmatically by introducing custom Sterotypes that relate to those concerns and extracting them using query view tables to create stakeholder views.

A single SystemContext block IBD is used as a proxy for ALL Views and ViewPoints.

Visit also:

[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

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: 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: 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.)

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

Relates to

Related notes