Webel's "super-relational" Note pages!

A Note is a short categorised statement, claim, policy, tip, or issue tracker Throughout this site, content is often related to supporting Notes, and each Note page links back to the content pages that reference it! The Note and Snippet concepts are very closely related and they support each other.
Look for "super-relational" Note page links at the bottom of most content pages!
Note kind Note Spec tag UML keywords SysML keywords Keywords
TIP UML2/SysML1.x: Property: derived vs derived union vs subsetted SysML-1.6, SysML-1.7, UML-2.5.1 Property::isDerived, Property::isDerivedUnion, Property::subsettedProperty UML, Unified Modeling Language, SysML, Systems Modeling Language, SysMLv1.x
CAVEAT, TOOL UML4SysML is a specification abstraction (concept) only, it does not find direct expression (such as via a namespace) in tools like MagicDraw/Cameo SysML-1.6 UML4SysML Cameo Systems Modeler, MagicDraw SysML
GOTCHA, ISSUE, TOOL, WARNING UML: Cameo Simulation Toolkit 19SP3: GOTCHA: CreateObjectAction ignores an Artifact as 'classifier' even though Artifact is a Classifier Alf-1.1, fUML-1.3, fUML-1.4, SysML-1.6, SysML-1.7, UML-2.5.1 DecisionNode, DecisionNode::decisionInput, DecisionNode::decisionInputFlow UML, Cameo Systems Modeler, Unified Modeling Language, Alf, fUML, Foundational UML
WARNING Until tool support for ~InterfaceBlock comes you have to make a decision: (1) Bake your own «~InterfaceBlock» then deal with clashes when tool support comes; (2) stick with the DEPRECATED UML conjugation (not nested-port friendly) and await migration. SysML-1.6 Port::isConjugated InterfaceBlock, ~InterfaceBlock, conjugation
NAMING, POLICY Use 'UpperCamelCase' (a.k.a. PascalCase) names for Classifiers such as UML Classes and SysML Blocks) to avoid confusion with 'lowerCase' Property names [see however special naming conventions for acronyms and SysML contract and flow Blocks] Classifier, Class Block UML, SysML
NAMING, POLICY Use of 'this-that' with a hyphen in Connector names is admissable (where 'this' and 'that' indicate Connector ends or their types) Connector Webel Best Practice
NAMING, POLICY Use singular Property names, let the multiplicity indicate plurality. Property, NamedElement::name, MultiplicityElement, multiplicity
ASSERTION, MODELLING Using Model-Based Systems Engineering with ANY version of Systems Modeling Language (SysML) is better than just doing drawings in a graphics tool or presentation tool SysML-1.6, SysML-1.7, SysMLv2 Systems Modeling Language, SysML, SysMLv1.x, SysMLv2, Model-Based Systems Engineering
ASSERTION Visual containment of the symbol for a UseCase in the rectangular symbol for a subject Classifier does NOT imply ownership! Packaging (ownership) of UseCases is separate from use within subjects, and a single UseCase may be used in more than one subject. UseCase, UseCase::subject, Package, Classifier, Element::owner
ASSERTION, WARNING Visual nesting of InstanceSpecification symbols has no meaning in the underlying model, only assignment to a Slot does! InstanceSpecification, instance MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML
WARNING WARNING: In natural language casual conversation one often hears people speaking of a digital twin "replicating" or "twinning" a physical entity. If you do it that way literally, you will NOT have anything to manage the control system loop! SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, Webel Best Practice
PATTERN, TIP, TOOL Webel + Mathematica + MTools + SysML SysML-1.6, SysML-1.7 Wolfram, Mathematica, Mathematica:MTools, Wolfram Language, Systems Modeling Language, MD SysML, CATIA Magic:v2021xR1, MagicDraw SysML, MagicDraw, Cameo Systems Modeler, Webel:MathematicaSysML
NAMING, PATTERN, POLICY Webel Best Practice: Mathematica: Options are encapsulated as a String variable with the prefix '$opt', and have a related '$info$opt$' String (help), '$lab$opt' String (label), a 'def$opt' default value expression, and an optional '$warn$opt' String. Webel Best Practice, Webel::SysML4Mathematica, Mathematica, Wolfram Language, naming, coding, Mathematica::option
ANTI-PATTERN, MODELLING, STYLE Webel Best Practice: SysML/SysPhS: DO NOT use overlapping Connector lines from/to one Port (can be misunderstood as "summed" flow and/or physical node/fork/junction). SysML-1.6, SysML-1.7, SysPhS-1.1 Connector, Port Webel Best Practice, SysPhS, SysML, Systems Modeling Language, physical interaction, signal processing
DISPLAY, MODELLING, TIP, TOOL Webel electronics modelling recipe for SysML: Diagrams can be made less verbose by using stereotype icon shape display mode, by not showing names and types on obvious Ports, by hiding context-specific values, and by omitting {net} tagged values. SysML-1.6, SysML-1.7 electronics, Webel Best Practice, SysML, Systems Modeling Language, MagicDraw SysML, Cameo Systems Modeler, micro-controller, Arduino
NAMING, STYLE Webel has a proposal for clearly revealing anonymous typed elements in SysML callouts and on derived Properties from operation queries. NamedElement::name, Type, TypedElement, TypedElement::type block property, value property, part property, AbstractRequirement::/satisfiedBy, AbstractRequirement::/tracedTo, Satisfy, Trace
PROPOSAL Webel has suggested primary/replica as an alternative to master/slave terminology for the SysML Copy relationship in future SysML versions SysML-1.6 AbstractRequirement::/master, Copy, Requirement
PROPOSAL Webel has suggested that SysMLv2 should support verification of each individual claim of more than one Element helping to Satisfy a Requirement. SysML-1.6 SysMLv2, Requirement, Satisfy, Verify, TestCase, «testCase» requirements engineering, test engineering
CAVEAT, EXPLANATION, MODELLING, TOOL Webel IT's summaries of MagicGrid® for SysML/MBSE with Cameo are offered for the interest of MagicGrid users for informative and educational purposes only. They are not recommendations to use (or not use) MagicGrid, and are not officially endorsed. SysML, Systems Modeling Language, MBSE, SysMLv1, Cameo Systems Modeler, MagicDraw SysML, CATIA Magic, Model-Based Systems Engineering, MagicGrid
ASSERTION Webel on Mathematica and the Wolfram Language vs Python. Python is not even close, not even vaguely close, it's not in the same league, as the Wolfram Language and Mathematica! python, Mathematica, Wolfram, Wolfram Language
ASSERTION Webel Parsing Analysis (with strict traceability of all elicited model elements) can be used side-by-side with "freestyle" modelling with incremental benefit the more it is used. Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«pa», WPA:«snippet»
POLICY Webel Parsing Analysis diagrams do their job once - namely traceable elicitation of model elements - and are then only kept as a reference! The elicited model elements are then used elsewhere in the final model. Webel Parsing Analysis, Webel Best Practice, WPA:«snippet», WPA:«pa»
PATTERN, TIP Webel Parsing Analysis for SysML - simplified profile Stereotype, custom Stereotype, Extension, Generalization, Actor ElementGroup Webel Parsing Analysis
EXPLANATION, MODELLING Webel Parsing Analysis for SysML: "Snippet trumps Requirement": A SysML Requirement element is just another model element that is elicited IN PARALLEL WITH other elements that a text description mentions in any way as being involved with or related to it. AbstractRequirement, SysML Requirements Diagram SysML, Systems Modeling Language, SysMLv1, MBSE, Model-Based Systems Engineering, Webel Best Practice, Webel Parsing Analysis, WPA:«snippet», WPA:Snippet::source, WPA:PAD
OPTION 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). SysML-1.6, SysML-1.7, SysMLv2 Stereotype, custom Stereotype, «keyword», user defined Stereotype parsing analysis, Webel Parsing Analysis, WPA:«pa:term», synonym
ASSERTION Webel Parsing Analysis is a "meta-process" that can be applied to general domain source documents to elicit Requirements (and related model elements) or to a Requirements Specification itself as a special case of a domain source document! Requirement requirements engineering, Webel Parsing Analysis, parsing analysis, WPA:«document»
POLICY, STYLE Webel Parsing Analysis «pa» diagrams are NOT intended as final presentation diagrams! They serve merely to traceably elicit model elements, which may then be shown in other (typically much tidier) presentation diagrams elsewhere. Webel Parsing Analysis, parsing analysis, WPA:«pa»
DISPLAY, MODELLING, POLICY Webel Parsing Analysis: A "focus" Parsing Analysis Diagram (PAD) for one or more Snippets SHOULD always show the /member tagged value of every Snippet. SysML-1.6, SysML-1.7 Diagram Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:PAD, WPA:«snippet»
POLICY Webel Parsing Analysis: A 'source' Document must have one (only) of a URL or a URN (includes ISBN or other unique identifier) for use as a URI Webel Parsing Analysis, parsing analysis, WPA:«document»
POLICY Webel Parsing Analysis: A custom Document stereotype (keyword «document») extends the UML standard profile Document that extends Artifact (which is NOT in the UML4SysML intersection). Such a Document may act as the 'source' of a «snippet». Artifact, «document» Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«snippet», WPA:Snippet::source
REQUIREMENT Webel Parsing Analysis: A Parsing Analysis Container MAY collect any other Element type as a member EXCEPT for another Parsing Analysis Container SysML-1.6, SysMLv2 Webel Parsing Analysis, WPA:«snippet», parsing analysis container, Systems Modeling Language
REQUIREMENT Webel Parsing Analysis: A Parsing Analysis Container MAY own other child Parsing Analysis Containers SysML-1.6, SysMLv2 ElementGroup Webel Parsing Analysis, WPA:«snippet», parsing analysis container, Systems Modeling Language
REQUIREMENT Webel Parsing Analysis: A Parsing Analysis Container MUST NOT be able to own the Elements it elicits SysML-1.6, SysMLv2 ElementGroup Webel Parsing Analysis, WPA:«snippet», parsing analysis container, Systems Modeling Language
POLICY Webel Parsing Analysis: A Snippet (keyword «snippet») MUST always have exactly one domain 'source' Document (keyword «document»). Webel Parsing Analysis, parsing analysis, WPA:«document», WPA:«snippet», WPA:Snippet::source
ASSERTION 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, SysML-1.7, UML-2.5.1 Package, Model, Dependency, Stereotype, custom Stereotype, «keyword» Webel Parsing Analysis, WPA:«pa», WPA:«pa:from», WPA:TargetModelZone, WPA:SourceInputZone
MODELLING, NAMING, POLICY Webel Parsing Analysis: Acronym: PAD = Parsing Analysis Diagram (may be nearly any diagram type, except those types that must be owned by an elicited model element) SysML-1.6, SysML-1.7 Diagram Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:PAD
DISPLAY, MODELLING, OPTION Webel Parsing Analysis: An "index" Parsing Analysis Diagram (PAD) showing a collection of Snippets may optionally (but need not always) show the /member tagged value of each Snippet. SysML-1.6, SysML-1.7 Diagram Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:PAD, WPA:«snippet»
MODELLING, NAMING, POLICY Webel Parsing Analysis: An anonymous Element may be collected as a /member of a Snippet (it is not important whether collected elements list with a clear name under /member, only that they are traceably elicited). SysML-1.6, SysML-1.7 Diagram ElementGroup, ElementGroup::/member Webel Parsing Analysis, parsing analysis, WPA:«pa»
MODELLING, POLICY, TOOL Webel Parsing Analysis: As StateMachine Diagrams are always owned by an element that is not eventually under the Source Input Zone they should not be used as «pa» diagrams. Elicit States instead via the /member section of the specification dialog. SysML-1.6, SysML-1.7 StateMachine Diagram, State, Element::owner SysML State Machine Diagram Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:PAD, MagicDraw SysML, Cameo Systems Modeler
POLICY Webel Parsing Analysis: Create a top-level 'source' or '0-source' Package/Model SEPARATE from your project model. All source «document» elements and «snippet» extracts and «pa» diagrams MUST be ultimately owned by that top-level Package/Model as ancestor! Package, Model Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:«document», WPA:«snippet»
OPTION 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'.) Stereotype, custom Stereotype, «keyword», user defined Stereotype parsing analysis, Webel Parsing Analysis, WPA:«pa:implied», WPA:«snippet»
DISPLAY, STYLE, TIP Webel Parsing Analysis: If the dashed-line "anchors" from your «snippet» ElementGroup symbols to elicited elements make a «pa» Parsing Analysis Diagram (PAD) too hard to read, try making them light grey using symbol properties. Webel Parsing Analysis
TIP, TOOL Webel Parsing Analysis: If you are processing lots of text from one source «document» create a STUB «snippet» with that «document» set as 'source' and just make copies of it in the model browser as needed. Big time saver! Webel Parsing Analysis, WPA:«pa», WPA:«snippet», WPA:«document»
CAPABILITY, FEATURE, NAVIGATION, TIP, TOOL Webel Parsing Analysis: If you have a unique URL for a domain source «document» you MAY additionally set it as an external hyperlink in the MagicDraw/Cameo tool (as well as setting it as the unique 'url' tagged value that acts as the '/uri'). Webel Parsing Analysis, parsing analysis, WPA:«document», MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
ASSERTION, DISPLAY, POLICY, SETTINGS, STYLE, TOOL Webel Parsing Analysis: If you wish to show a «snippet» comment symbol (with its body text) in a presentation diagram (that is NOT a «pa» diagram) remove the '/member' tagged value from display so the only visible tagged value is 'source'. ElementGroup::/member Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:Snippet::source
CONVENTION, MODELLING, TIP Webel Parsing Analysis: It does not matter whether you use a Package or a Model package. (The informal Webel convention is that Models are used for systems engineering analysis with SysML and Packages are reserved for code-related software engineering.) SysML-1.6, SysML-1.7, UML-2.5.1 Model, Package Webel Parsing Analysis, WPA:«pa», SysML, Systems Modeling Language
TIP Webel Parsing Analysis: It is not intended that you "parse and analyse" every sentence from every domain source document and map every word to your SysML model. The process adds incremental benefit; the more you use the WPA recipe, the better! Webel Parsing Analysis
DISPLAY, REQUIREMENT Webel Parsing Analysis: It MUST be possible to collect elicited members of a Parsing Analysis Container graphically in diagrams using relationship-like path drawing (not just via a specification dialog or other indirect modelling means) SysML-1.6, SysML-1.7, SysMLv2 Webel Parsing Analysis, WPA:«snippet», parsing analysis container, Systems Modeling Language
DISPLAY, REQUIREMENT Webel Parsing Analysis: It SHOULD be possible to relate one Parsing Analysis Container to another and stereotype that relationship as an RDF/OWL-like semantic triple SysML-1.6, SysML-1.7, SysMLv2 Webel Parsing Analysis, WPA:«snippet», parsing analysis container, Systems Modeling Language, parsing analysis, RDF, OWL, semantic web, semantic triple
TIP Webel Parsing Analysis: MagicDraw/Cameo: In parsing diagrams use the element compartment properties to only display the features relevant to the context of a particular snippet's text extract. Webel Parsing Analysis, MagicDraw SysML, Cameo Systems Modeler
DISPLAY, LIMITATION Webel Parsing Analysis: MagicDraw/Cameo: SysML1.6+: ElementGroup-based Snippets do not list in the compartment of Package/Model symbols because ElementGroup is based on the UML Comment, which does not list in Package/Model symbols. SysML-1.6, SysML-1.7, UML-2.5.1 Comment, Model, Package, symbol ElementGroup Webel Parsing Analysis, WPA:«snippet», MagicDraw SysML, Cameo Systems Modeler, SysML, Systems Modeling Language
DISPLAY, MODELLING, NAMING, POLICY, TIP Webel Parsing Analysis: Pseudo Semantic Triple: For «pa:triple» applied to a named one-to-one Dependency, the source is the subject, the name of the Dependency is the predicate, the target is the object. Association, NamedElement Webel Parsing Analysis, semantic triple, WPA:«pa:triple»
DISPLAY, MODELLING, NAMING, POLICY, TIP Webel Parsing Analysis: Pseudo Semantic Triple: For «pa:triple» applied to a named one-to-one or one-to-many uni-directional Association, the non-navigable end Property is the subject, the name is the predicate, the navigable end Property is the object. Association, NamedElement Webel Parsing Analysis, semantic triple, WPA:«pa:triple»
DISPLAY, MODELLING, NAMING, POLICY, TIP Webel Parsing Analysis: Pseudo Semantic Triple: When «pa:triple» is applied to a named uni-directional Association the name and a consistent direction arrow should be displayed on the Association symbol in diagrams. Association, NamedElement Webel Parsing Analysis, semantic triple, WPA:«pa:triple»
TIP Webel Parsing Analysis: Relationships between «snippet» items can be tracked using additional tagged values such as 'contradictedBy' and 'contradicts'. This is robust, but it can be verbose when Snippets have long names if the tagged values are displayed. ElementGroup Webel Parsing Analysis, WPA:«snippet»
MODELLING, POLICY Webel Parsing Analysis: SysML: Pseudo Semantic Triple: A «pa:triple» may be applied to a Dependency between SysML Blocks and/or Actors or Properties typed by them. Dependency, Actor Block Webel Parsing Analysis, semantic triple, WPA:«pa:triple»
MODELLING, POLICY Webel Parsing Analysis: SysML: Pseudo Semantic Triple: A «pa:triple» may be applied to a uni-directional Association between SysML Blocks and/or Actors. Association, Actor Block Webel Parsing Analysis, semantic triple, WPA:«pa:triple»
QUESTION Webel Parsing Analysis: SysMLv1.x: Q: "Instead of using a Snippet extension of an ElementGroup, can't I just use a Requirement and Trace to achieve the same thing?" A: No! The ElementGroup extended as the Snippet is far more powerful and fit for purpose. AbstractRequirement, AbstractRequirement::text Webel Parsing Analysis, WPA:«snippet»
TIP Webel Parsing Analysis: The absolute basics of the process (SysMLv1.x form) SysML-1.6, SysML-1.7, UML-2.5.1 Comment::annotatedElement ElementGroup, ElementGroup::/member WPA:«snippet», WPA:«pa», Webel Parsing Analysis, parsing analysis, parsing analysis container
MODELLING, NAMING, POLICY Webel Parsing Analysis: The name of a Parsing Analysis Diagram (PAD) may be drawn from a focus Snippet OR may simply indicate a topic of interest to the analysis SysML-1.6, SysML-1.7 Diagram, NamedElement, NamedElement::name Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:«snippet», WPA:PAD
DISPLAY, REQUIREMENT Webel Parsing Analysis: The symbol for a Parsing Analysis Container MUST be able to indicate the unique domain source document from which its analysed text extract was quoted. SysML-1.6, SysML-1.7, SysMLv2 Webel Parsing Analysis, WPA:«snippet», parsing analysis container, Systems Modeling Language, parsing analysis
DISPLAY, REQUIREMENT Webel Parsing Analysis: The symbol for a Parsing Analysis Container MUST be able to OPTIONALLY display a list of names of elicited model elements (a.k.a. members) SysML-1.6, SysML-1.7, SysMLv2 ElementGroup::/member Webel Parsing Analysis, WPA:«snippet», parsing analysis container, Systems Modeling Language, parsing analysis
DISPLAY, REQUIREMENT Webel Parsing Analysis: The symbol for a Parsing Analysis Container MUST be text-friendly and evocative of quoting a domain source text extract SysML-1.6, SysML-1.7, SysMLv2 Webel Parsing Analysis, WPA:«snippet», parsing analysis container, Systems Modeling Language
DISPLAY, REQUIREMENT Webel Parsing Analysis: The symbol for the relationship between a Parsing Analysis Container and elicited model elements SHOULD be a dashed line (like the anchor/handle line used with a UML Comment) SysML-1.6, SysML-1.7, SysMLv2 Comment, Comment::annotatedElement ElementGroup Webel Parsing Analysis, WPA:«snippet», parsing analysis container, Systems Modeling Language
MODELLING, REQUIREMENT Webel Parsing Analysis: The symbol of a Parsing Analysis Container MUST be usable on every possible diagram type SysML-1.6, SysML-1.7, SysMLv2 Webel Parsing Analysis, WPA:«snippet», parsing analysis container, Systems Modeling Language
CONVENTION, TIP Webel Parsing Analysis: typically the quoted extract text (body) of a «snippet» is a short phrase, a sentence, or a couple of short sentences (but not dozens of sentences). ElementGroup Webel Parsing Analysis, WPA:«snippet», parsing analysis
MODELLING, NAMING, POLICY Webel Parsing Analysis: Where too many dashed line "anchors" from Snippets to elicited members lead to clutter they may be selectively omitted from a Parsing Analysis Diagram (PAD) once each member has been collected. SysML-1.6, SysML-1.7 Comment, Comment::annotatedElement, MD:anchor Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:PAD, WPA:«snippet»
MODELLING, NAMING, POLICY Webel Parsing Analysis: While Associations may be collected as elicited members of a Snippet this can quickly lead to clutter in the /member list display. Often just collecting an end Property as member is sufficient. SysML-1.6, SysML-1.7 Generalization ElementGroup, ElementGroup::/member Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:«snippet»
MODELLING, NAMING, POLICY Webel Parsing Analysis: While Generalizations may be collected as elicited members of a Snippet this can quickly lead to clutter in the /member list display. SysML-1.6, SysML-1.7 Generalization ElementGroup, ElementGroup::/member Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:«snippet»
TIP Webel Parsing Analysis: You do not need to map every word of every snippet to the UML/SysML model! Extract only the information required for your domain modelling task to add incremental benefit. Webel Parsing Analysis
TIP Webel Parsing Analysis: You may create custom stereotypes applicable to a Dependency or a uni-directional Association to represent a «predicate» much like a semantic triple (subject-predicate-object) in OWL/RDF.
DISPLAY, STYLE, TIP Webel recommends (usually) display the header of a Package, Model, ModelLibrary, or Profile in the 'tab' (rather than 'top') Package, Model, ModelLibrary, Profile MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler, Webel Best Practice
DISPLAY, ISSUE, TOOL, WARNING Webel recommends when using MagicDraw/Cameo: AVOID the "elided Pin" abstract ObjectNode notation on Activity Diagrams, use explicit Pins! Pin, ObjectNode MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
NAMING, POLICY Webel suggests using a verbose 'name' for leaf (child) Requirements but NO 'text' to prevent Single Source of Truth issues and for improved callout vs relationships (but this might not always work when syncing with external requirements management tools) NamedElement::name AbstractRequirement::text, Requirement Webel Best Practice, requirements engineering
ASSERTION Webel Twin Pattern: A DigitalEntity (a.k.a. «digital» @Entity) used as a digital variant must not be directly bound to a «physical» PhysicalEntity (may not directly actuate/sense/affect) SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, digital twin, control system, sensor, WTP:DigitalEntity, WTP:PhysicalEntity
ASSERTION, POLICY Webel Twin Pattern: A DigitalTwin (even a "process twin" or "finance twin"), always, without exception, BY DEFINITION HERE either directly or indirectly involves at least one existing or anticipated PhysicalEntity (even if only via another DigitalTwin)! SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, Systems Modeling Language, digital twin, WTP:PhysicalEntity, WTP:DigitalTwin
POLICY Webel Twin Pattern: A DigitalTwin and PhysicalEntity must both be 'attached' to Sensors and/or Actuators under management of the DigitalTwin before the twinning control loop is fully entered. Webel Twin Pattern, digital twin, sensor, actuator, control system, control loop, WTP:PhysicalEntity, WTP:DigitalTwin
POLICY Webel Twin Pattern: A DigitalTwin manages a control loop including a PhysicalEntity and a DigitalEntity (a.k.a. @Entity) that «replicates» it. It typically includes at least one Sensor and at least one Actuator. SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, Webel Best Practice
POLICY Webel Twin Pattern: A DigitalTwin may use one or more variantEntity:@Entity[0..*] to explore the impact of changes (optimisation studies, trade off studies) and then use them to drive the PhysicalEntity into a desired state (via its ControlSystem). SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, WTP:DigitalEntity, WTP:«digital»
POLICY Webel Twin Pattern: A DigitalTwin must model processes and the entities they act on separately. SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, Webel Best Practice, WTP:DigitalTwin, WTP:PhysicalEntity, WTP:@Entity
POLICY Webel Twin Pattern: A LogicalProcess may only act on a PhysicalEntity via a PhysicalProcess Webel Twin Pattern, WTP:LogicalProcess, WTP:PhysicalProcess
POLICY Webel Twin Pattern: A PotentialPhysicalAsset is «digital», not «physical». It is used to acquire (an existing) or create (build, manifest, make) an «physical» ActualPhysicalAsset, which is a special case of «physical» PhysicalEntity. SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, Webel Best Practice
POLICY Webel Twin Pattern: A «digital» DigitalEntity (a.k.a. @Entity) encapsulates strictly geometrical, spatial, and material aspects of a «physical» PhysicalEntity only. BY DEFINITION of this pattern it DOES NOT encapsulate processes! SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, Webel Best Practice
POLICY Webel Twin Pattern: A «digital» DigitalEntity (a.k.a. @Entity) is NOT a representation! It is a digital encapsulation (it can only be perceived at the level of "bits and bytes"). It HAS many representations (such as views)! SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, WTP:DigitalEntity, WTP:@Entity, SysML, Systems Modeling Language
POLICY Webel Twin Pattern: An ActualPhysicalAsset is an asset that is also a «physical» PhysicalEntity. Webel Twin Pattern, WTP:ActualPhysicalAsset, WTP:PhysicalEntity, digital twin
ASSERTION Webel Twin Pattern: An AssetSpecification may contain ANY information or data of ANY kind in ANY format about how to acquire, manifest, build, or create a physical asset. This information may be distributed across an @Entity and a PotentialPhysicalAsset. Webel Twin Pattern, WTP:ActualPhysicalAsset, WTP:AssetSpecification
POLICY Webel Twin Pattern: Communication between the ControlSystem of a DigitalTwin and its digitalEntity:@Entity is via a dedicated protocol (ReadTwin, WriteTwin) distinct from the sensor reading or actuator driving signals. Webel Twin Pattern, digital twin, control system
CONVENTION 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. Property, Stereotype block property Webel Best Practice, Webel Twin Pattern
CONSTRAINT, POLICY Webel Twin Pattern: DigitalTwin: The multiplicity of 'digitalEntity:@Entity' and 'physicalEntity:PhysicalEntity' MUST be [1] when the DigitalTwin is in the state Attached, the @Entity is in the state Bound, and the PhysicalEntity is in the state Exists. State, oclInState, Constraint Webel Twin Pattern, WTP:PhysicalEntity, WTP:DigitalEntity, WTP:@Entity, WTP:DigitalTwin
POLICY Webel Twin Pattern: It is a DigitalEntity (a.k.a. @Entity) - not the DigitalTwin that owns it - that directly «replicates» geometrical, spatial, and material aspects (only) of a single PhysicalEntity. SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, Webel Best Practice, WTP:DigitalTwin, WTP:PhysicalEntity, WTP:@Entity
ASSERTION Webel Twin Pattern: Not every twinnable PhysicalEntity is worth treating as an asset. SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, digital twin, WTP:ActualPhysicalAsset, WTP:PhysicalEntity, asset
POLICY Webel Twin Pattern: Once a PotentialPhysicalAsset has been integrated with a real, existing (has mass) ActualPhysicalAsset under twinning control, its job is done forever (although it may be kept as an historical tracking record). SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, WTP:PotentialPhysicalAsset, WTP:ActualPhysicalAsset
POLICY Webel Twin Pattern: The information and data in AssetSpecification leveraged for creation of a new ActualPhysicalAsset need not necessarily only be «digital». Webel Twin Pattern, digital twin
POLICY Webel Twin Pattern: The primary aim of the digitalEntity:@Entity of a DigitalTwin is to replicate its physical:PhysicalEntity as closely as possible (not to explore variants). SysML-1.6, SysML-1.7, SysMLv2 Webel Twin Pattern, WTP:DigitalEntity, WTP:«digital»
POLICY Webel Twin Pattern: The sensor/actuator twinning control loop can involve automated devices (SensorDevice and/or ActuatorDevice) and or humans (SensorHuman and/or ActuatorHuman). Webel Twin Pattern, control system, actuator, sensor
CONVENTION, TIP Webel use editorial Sterotypes prefixed with ! and ? in and in CAPS in keywords such as: «!». «?», «!ERROR», «!ISSUE», «!CAUTION», «!WARNING», «!CAVEAT», etc. Stereotype Webel Best Practice
FEATURE, TIP, TOOL Webel vs Mathematica: The Very Good, The Bad, and The Ugly Mathematica, Wolfram, Wolfram Language, Mathematica:Dataset
ISSUE Webel vs SysML-1.6: There is no «port» stereotype keyword for Port or Property in UML-2.5.1 or SysML-1.6, it is introduced as a custom (user-defined) stereotype keyword here only to mimic the spec Figure 9-8. SysML-1.6 «keyword», Port SysML specification figure
ASSERTION Webel vs SysPhS-1.1: Annex A.5: Assume the conversion value property name 'SaturationVaporPressure::hPa2Pa' stands for 'hectopascal to pascal'. SysPhS-1.1 Property::redefinedProperty SysPhS
ASSERTION Webel vs SysPhS-1.1: Annex A.5: Assume the conversion value property names 'WaterTank::litpSec2mLitpHr' and 'EvaporationCalculation2::litPSec2mLitPHour' stand for 'litres per second to millilitres per hour' SysPhS-1.1 Property::redefinedProperty SysPhS