Stereotype

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Webel ADTs include inheritance (and aren’t actually formal ADTs)

Gallery

Tutorial

Section

SECTION: The Webel Abstract Data Type (ADT) stateless pseudo-classes with inheritance (with SysMLv1 models)

Webel Abstract Data Types (ADTs) vs the user-contributed MTools for OO

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: The Webel Abstract Data Type (ADT) stateless pseudo-classes with inheritance (with SysMLv1 models)

Introduction to Webel Abstract Data Types (ADTs) with SysMLv1 models

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: The Webel Abstract Data Type (ADT) stateless pseudo-classes with inheritance (with SysMLv1 models)

The sigsUp/Down functions as a SysML BDD: With Options Block and pseudo functional indicators

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

[TECHNICAL SLIDE TRAIL] The Webel libraries for Wolfram Mathematica: With SysMLv1 models.

Section

SECTION: Modelling the Wolfram Language in SysMLv1 and related Webel coding conventions

SysML: HOWTO Represent a person as an external block-based SysML «actor» in one lower context and as an internal participating «person» in another higher context, with traceability. For modelling systems of systems in a team with many modellers.

SysMLv1: TIP: You can strengthen the ill-defined semantics of Property 'aggregation' (an AggregationKind) by applying custom Stereotypes to a Property, documented with its intended use. Not perfect, but better than not. EXAMPLE: «assembled»

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: SysMLv1: TIP: Use semantically meaningful Association names and/or custom Stereotypes where applicable. They can also often be used as pseudo OWL/RDF semantic triples. But don't use Association names where an ItemFlow can capture an exchange item!

SysML Parametrics: You can use custom stereotypes keywords «i» and «o» on constraint parameters to indicate their intended use (causality) as (i)nputs and (o)utputs on ConstraintBlocks

Webel: On going beyond SysML (and UML) with additional modelling practices, policies, and additional semantics

REFERENCE CARD: Webel Parsing Analysis for SysML1.x: Snippet Customizations

Gallery

Tutorial

TRAIL: Theory and best practices for the Webel Parsing Analysis recipe for SysMLv1.6+

Section

Slide kind

TRAIL: Theory and best practices for the Webel Parsing Analysis recipe for SysMLv1.6+

MagicDraw/Cameo: Rule: Internal Block Diagram and Block structure compartment: only one symbol for a given Property may be shown.

MagicDraw/Cameo: Display option: You can choose whether to show Domain Specific Language (DSL) stereotypes: 'None', 'All', 'Only Last'

Webel: SysML: Electronics modelling: TIP: Use a custom Connector stereotype '<>' with the keyword '<>' to carry a 'net' property. (Use of punctuation in Stereotype names is not usually recommended and the keyword is not usually displayed.)

How to prounce Guillemet, those French-looking sideways double chevron quote thingies UML and SysML use to indicate a stereotype «keyword» (amongst other things).

Webel Parsing Analysis for SysML: Track and display alternative names, human friendly names, organisation-specific names, and identifiers using tagged values for a custom stereotype «pa:term» (adapt or extend as required).

REFERENCE CARD: Webel Parsing Analysis for SysML1.x: Auxiliary stereotypes

Gallery

Tutorial

Section

Slide kind

TRAIL: Theory and best practices for the Webel Parsing Analysis recipe for SysMLv1.6+

More on tracking contradictions: Optical telescope example

Gallery

Tutorial

Section

Slide kind

TRAIL: Theory and best practices for the Webel Parsing Analysis recipe for SysMLv1.6+

Indicating relationships between Snippets using tagged values: contradicts/contradictedBy

Gallery

Tutorial

Section

Slide kind

TRAIL: Theory and best practices for the Webel Parsing Analysis recipe for SysMLv1.6+

Webel Parsing Analysis as a meta-process: Snippets before Requirements!

Gallery

Tutorial

Section

Slide kind

This means that: Not all words appearing between guillemets are necessarily keywords, and words appearing in guillemets do not necessarily represent stereotypes.

Source

In addition to identifying keywords, guillemets are also used to distinguish the usage of stereotypes.

Source

For some kinds of Classifiers, optionally in the right hand corner an icon denoting the kind of Classifier can be displayed.

Source

If a role is typed by a classifier other than Class, the name compartment of the part box symbol contains the appropriate keyword (e.g., «component») above the name.

Source

Stereotypes applied to behaviors may appear on the notation for CallBehaviorAction when invoking those behaviors, as shown in Figure 11-2.

Source

The stereotype applies to all parameters corresponding to the pins notated by the object node.

Source

Stereotypes applying to parameters can appear on object nodes in activity diagrams, as shown in Figure 11-7, when the object node notation is used as a shorthand for pins.

Source

TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler]

Webel Parsing Analysis: Formally, if «pa:implied» has been applied to indicate an implied elicited Element, the 'snippet' tagged value should bet set using at least one Snippet that implies it. (Note, the Snippet should have identical 'name' and 'body'.)

Webel Parsing Analysis: A stereotype with keyword «pa:from» may be applied to a Dependency from a Package to another Package within the Source Input Zone to indicate that all of its Elements were directly or indirectly elicited from source Documents.

SysML-1.6/1.7: You can introduce a custom (user-defined) stereotype keyword «item» to indicate Properties that are to be used as "packets" for ItemFlows on Connectors. (SysMLv2 will have a formal way of treating such items/packets.)

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.

SysML: When using Property::defaultValue and Property::redefinedValue to carry a "shadow hierarchy" of redefinitions across an entire system hierarchy, considering using a user-defined keyword such as «configuration» or «scenario» on each redefining Block

The use of an additional «port» keyword on a Port is usually redundant and causes clutter. The use of an additional «port» keyword on a basic Property is an obsolete trick. Please don't imitate it even if you see it in some specification sample diagrams!

SysPhS-1.1: Apparent use of part Property with «port» keyword (instead of standard SysML Port) leads to property path symbols appearing inside the boundary of context blocks (instead of within a Port symbol on the boundary) in IBDs and Parametric Diagrams

Webel vs SysPhS-1.1: Recommend use standard SysML Ports instead of block part property with «port» keyword

SysPhS: MagicDraw/Cameo: In the sysphs_profile the properties for PhSVariable have multiplicity [1], so the defaults always appear explicitly (but may be overridden): isContinuous: Boolean = true, isConserved: Boolean = false, changeCycle: Real = 0

Figure 1: Simulation stereotypes

Gallery

Tutorial

Section

Slide kind

Webel Twin Pattern: Convention: [MIGHT CHANGE]: A '*' prefix in a Property name of a «digital» @Block in a DigitalTwin model indicates a mapped block property, which must be typed by a non-digital «mappable» Block, and must have the «@» keyword applied.

SysML: Electronics: When modelling electronics systems you should to decide and make clear (with ItemFlow and/or Stereotypes) whether you are modelling signals (information, does not care about GND) or a physical design with voltage (needs GND)

Block:8_specializations_are_blocks: Any classifier that specializes a Block shall also have the Block stereotype or one of its specializations applied.

Source

TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model

Webel: SysMLv2: WISHLIST: Suggest declare an custom Stereotype as 'cascading' then behave likes constraint rules for Block

SysML Parametrics: You can use custom stereotypes keywords «i» and «o» to indicate value properties that are intended to be used as (i)nputs and (o)utputs when bound to constraint parameters for SysML Parametrics

Webel Parsing Analysis for SysML - simplified profile

An eyepiece is a type of lens that is attached to a variety of optical devices such as telescopes and microscopes.

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model

The objective is the optical element that gathers light from the object being observed and focuses the light rays

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model

An optical telescope is a telescope that gathers and focuses light mainly from the visible part of the electromagnetic spectrum

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model

Many new types of telescopes were invented including radio telescopes and infrared telescopes

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model

The reflecting telescope uses mirrors to collect and focus light

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia

Mass and charge of electron and positron

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia

Modelling antiparticles, antileptons, and antimatter

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia

Leptons and interactions

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia

Spin for elementary particles and composite particles

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia

Mass of charged leptons and decay (Part 2)

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia

Mass of charged leptons and decay (Part 1)

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia

Use multiple snippets to bridge knowledge gaps

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia

Our first Parsing Analysis diagram about leptons

Gallery

Tutorial

Section

Slide kind

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

MagicDraw/Cameo: You can control how or whether applied Sterotypes are displayed on most Element symbols using the 'Show Stereotypes' display option (and in some cases this affects how the entire symbol is displayed).

MagicDraw/Cameo: You can assign values to 'tagged values' of Stereotypes via the Tags section in the specification dialog. Make sure you have one of the 'On Shape' or 'In Compartment' Show Tagged Values display options enabled.

MagicDraw/Cameo: You can assign or un-assign one or more Stereotypes to one or more selected Elements at once using the 'Stereotype' context menu item

MagicDraw/Cameo: You can drag-n-drop most applicable Stereotype types from the model browser onto an Element's symbol in a Diagram to apply it to that Element (does not work in all cases).

While SysML does not officially include the UML Profile Diagram, in practice in the MagicDraw/Cameo tool it is often used (rather than a Package Diagram) to afford access to all profile element menus and to make it clear that it involves profile elements.

Useful "user-defined" stereotypes for Blocks: «system context», «system», «subsystem», «external», «domain»

Gallery

Tutorial

Section

08:01: The building Blocks of SysMLv1

Slide kind

Just like a Class, a Stereotype may have Properties, which have traditionally been referred to as Tag Definitions. When a Stereotype is applied to a model element, the values of the Properties have traditionally been referred to as tagged values.

Source

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Example: Linking to an external JIRA issue tracking page using a Comment extension with tagged values metadata

Gallery

Tutorial

Section

17:01: Creating custom Comment stereotypes

Slide kind

hybrid diagram

MagicDraw/Cameo: supports HTML (including hyperlinks) in String based tagged value (Stereotype property) fields. Just activate HTML mode during tagged value editing.

A stereotype must be contained, directly or indirectly, in a profile.

Source

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

A custom Comment extension with tagged values metadata

Gallery

Tutorial

Section

17:01: Creating custom Comment stereotypes

Slide kind

hybrid diagram

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

The SysML Problem and Rationale extensions of Comment

Gallery

Tutorial

Section

17:01: Creating custom Comment stereotypes

Slide kind

hybrid diagram