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
ISSUE, TOOL MagicDraw SysML/Cameo: 19SP3: Export to Modelica from SysPhS sample for HumidifierSystem does not execute in Wolfram SystemModeler Simulation Centre SysML-1.6, SysML-1.7, SysPhS-1.1 Wolfram SystemModeler, MagicDraw SysML, MD SysML, Cameo Systems Modeler, Modelica, SysPhS
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
TIP MagicDraw SysML/Cameo: For export of more complex physical interaction and flow cases to Modelica or Simulink/Simscape/Stateflow load the SysPhS ModelLibrary using SysPhSLibrary.mdzip as a shared project. SysML-1.6, SysPhS-1.1 SysPhS, Modelica, Stateflow, Simulink, Simscape, MD SysML, SysML, Systems Modeling Language, Cameo Systems Modeler, simulation, execution, MagicDraw SysML
TIP MagicDraw SysML/Cameo: You do not always need to load the entire SysPhS ModelLibrary for simpler black box exports to Modelica or Simulink/Simscape/Stateflow (sometimes the sysphs_profile within the MD Customization for SysML is enough) SysML-1.6, SysPhS-1.1 Profile SysPhS, Modelica, Stateflow, Simulink, Simscape, MD SysML, SysML, Systems Modeling Language, Cameo Systems Modeler, simulation, execution, MagicDraw SysML
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
MODELLING, TIP UML/SysML: A Boolean "state flag" attribute corresponding to a State can be useful for indicating states in some diagram types (but must be synchronised with Transitions to States carefully). SysML-1.6, SysML-1.7, UML-2.5.1 State, Boolean Webel Best Practice, UML, Systems Modeling Language, SysML, Unified Modeling Language, state flag
SysMLv2 will have a completely new way of dealing with instances. SysMLv2 instance, InstanceSpecification SysMLv2 SysML, Systems Modeling Language
CAVEAT CAVEAT: The UML-2.5.1 InstanceSpecification does not support Ports! UML-2.5.1 instance, InstanceSpecification, Port UML, Unified Modeling Language, Systems Modeling Language, SysML
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
TIP UML/SysML: During modelling it can really help to create little instance (object) diagrams as you go! This can also help communicate with non-SysML stakeholders. SysML-1.6, SysML-1.7, UML-2.5.1 instance, InstanceSpecification Webel Best Practice
POLICY UML/SysML: If you have a Boolean "state flag" attribute corresponding to a State you MUST set it on an 'entry' of the State, not on the 'effect' of a Transition into the State (otherwise with multiple incoming Transitions it could be WET and breaks SSoT). fUML-1.3, fUML-1.4, SysML-1.6, SysML-1.7, SysMLv2, UML-2.5.1 StateMachine, State::entry, Transition, attribute value property Webel Best Practice, Systems Modeling Language, Unified Modeling Language, DRY, WET, SSoT, Single Source of Truth, state flag
TIP UML/SysML: When you use an AddStructuralFeatureValueAction to set one end of a bi-directional Association it also sets the other end. fUML-1.3, fUML-1.4, SysML-1.6, SysML-1.7, UML-2.5.1 AddStructuralFeatureValueAction, Association, Property Unified Modeling Language, Systems Modeling Language
TIP Not every task in Activity Diagrams is well-suited to graphical modelling; consider using Action Language Helper (ALH) or Action Language for Foundational UML (Alf) Alf-1.1 LoopNode, ConditionalNode, StructuredActivityNode Alf, Action Language Helper, Cameo Systems Modeler, Magic Model Analyst [Cameo Simulation Toolkit]
POLICY Webel Twin Pattern: An ActualPhysicalAsset is an asset that is also a «physical» PhysicalEntity. Webel Twin Pattern, WTP:ActualPhysicalAsset, WTP:PhysicalEntity, digital twin
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
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
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
FEATURE, TIP, TOOL Cameo Simulation Toolkit matches the Parameters of an effect Behavior and a trigger Operation on a Transition under the hood. SysML-1.6, SysML-1.7, UML-2.5.1 Transition::trigger, Transition::effect, Behavior, Activity, StateMachine Magic Model Analyst [Cameo Simulation Toolkit]
In some slides some Comments in UML/SysML diagrams are verbosely marked with the stereotype keyword «webel» to distinguish them from «snippet» domain source document text extracts. Webel Parsing Analysis, WPA:«snippet», WPA:«webel»
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 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
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
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
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
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: 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
WARNING CAVEAT: The current Font Awesome icon used for 3D views is in fact actually a Unity branding icon [as a placeholder] that WILL change. WTP:EntityView
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: 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: 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
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
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 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: 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
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 «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
CONVENTION Webel: Convention: [MIGHT CHANGE]: An '@' prefix in a DigitalTwin model indicates a «digital» Block that maps a non-digital «mappable» Block. Webel Best Practice, Webel Twin Pattern
DISPLAY, FEATURE, OPTION, TIP, TOOL Cameo Simulation Toolkit: GOTCHA: In the Variable pane reference properties are hidden by default (show them using the Options pulldown menu) SysML-1.6, UML-2.5.1 Property, AggregationKind::none, AggregationKind::shared reference property, MD:ReferenceProperty Cameo Systems Modeler, Magic Model Analyst [Cameo Simulation Toolkit], Unified Modeling Language, Systems Modeling Language
PROPOSAL, WISHLIST Webel: SysMLv2: WISHLIST: Ability to relate one ElementGroup to another SysMLv2 ElementGroup SysMLv2:WISHLIST, Webel:WISHLIST, Systems Modeling Language, SysML
ISSUE SysML-1.6: Figure 8-17: Redefined properties in Vehicle Model 1 and Vehicle Model 2 break constraint: 'BoundReferences shall not be applied to properties that are related by redefinition to other properties with BoundReference applied' SysML-1.6 BoundReference, HSUV sample problem Systems Modeling Language, SysML
ASSERTION, MODELLING, NAMING, TIP [HISTORICAL] SysML: Some users employed the ~ tilde prefix for a conjugated Port type long before it was introduced for ~InterfaceBlock and you MAY use it to name a regular Block that is not an ~InterfaceBlock SysML-1.6 Block, ~InterfaceBlock, InterfaceBlock Systems Modeling Language, SysML, Webel Best Practice
MODELLING, PATTERN, TIP SysML: Electronics: When modelling ground (GND) use a Port type that has an inout FlowProperty Port FullPort, ProxyPort, FlowProperty, FlowProperty::direction, FlowDirectionKind::inout, InterfaceBlock, ~InterfaceBlock electronics, Systems Modeling Language, port-based engineering, SysML
MODELLING, TIP 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) Signal, InformationFlow, Stereotype, custom Stereotype ItemFlow electronics, Systems Modeling Language, wiring, GND, signal flow, signal processing
ANTI-PATTERN, MODELLING, PATTERN, TIP Webel: SysML: Electronics: DO NOT represent a jack/socket as a dumb proxy. Imagine it can introduce some signal noise or other effect (such as buzz) to test it is a physical model. Connector, Port, Port::isBehavior ProxyPort, BindingConnector, FullPort, "standard" Port, ParticipantProperty, AssociationBlock electronics, Systems Modeling Language, proxy, port-based engineering, jack, socket, SysML
CONSTRAINT, PROPOSAL, WISHLIST Webel: SysML-1.7/SysMLv2: WISHLIST: Constraint: A BindingConnector used for pure proxying MUST NOT be typed by an AssociationBlock by definition, because the associated information can be mis-appropriated to undermine the proxy equality! SysML-1.7, SysMLv2 SysMLv2, AssociationBlock, BindingConnector, ProxyPort SysMLv2:WISHLIST, Webel:WISHLIST, Systems Modeling Language, SysML, Webel Best Practice
PROPOSAL, WISHLIST Webel: SysMLv2: WISHLIST: Manage "cascading" Satisfy claim vs Block inheritance hierarchy with redefined properties SysMLv2 Generalization Satisfy, AbstractRequirement, Requirement, SysMLv2, Block Webel:WISHLIST, Systems Modeling Language, SysMLv2:WISHLIST
PROPOSAL, WISHLIST Webel: SysMLv2: WISHLIST: Suggest declare an custom Stereotype as 'cascading' then behave likes constraint rules for Block SysMLv2 user defined Stereotype, Constraint, Stereotype, custom Stereotype SysMLv2, Block Webel:WISHLIST, Systems Modeling Language, SysMLv2:WISHLIST
PROPOSAL, WISHLIST Webel: SysMLv2: WISHLIST: Ability to show more of an AssocationBlock on a Connector in an IBD SysMLv2 Connector SysML Internal Block Diagram, SysMLv2, AssociationBlock Webel:WISHLIST, Systems Modeling Language, SysMLv2:WISHLIST
PROPOSAL, WISHLIST Webel: SysMLv2: WISHLIST: Verify each Satisfy claim rather than Verify a Requirement SysMLv2 Verify, Satisfy, AbstractRequirement, Requirement, SysMLv2 Webel:WISHLIST, Systems Modeling Language, SysMLv2:WISHLIST
WARNING SysML does NOT distinguish between 'assembly' and 'delegation' Connector kinds (because of its more complex support for nested ports). These Connector type classifications are only relevant in UML. ConnectorKind::assembly, ConnectorKind::delegation nested Port, NestedConnectorEnd Unified Modeling Language, Systems Modeling Language, UML, SysML, MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
ISSUE, TOOL BUG: Cameo Simulation Toolkit 19SP3: StateMachine: Crashes with an irrelevant "memory error" report if you fire a signal Trigger during execution of an 'entry' Activity with a timer fUML-1.3, fUML-1.4, UML-2.5.1 StateMachine, State::entry, Activity, AcceptEventAction, TimeEvent::isRelative, completion, completion transition Cameo Systems Modeler, Magic Model Analyst [Cameo Simulation Toolkit]
ISSUE, TOOL, WARNING UML-2.5.1 does NOT permit a trigger or guard on a Transition from an initial pseudostate in a StateMachine but Cameo/MagicDraw does (please avoid). PseudostateKind::initial, Transition, Transition::trigger, Transition::guard, StateMachine, StateMachine Diagram Magic Model Analyst [Cameo Simulation Toolkit], MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
COMPLICATION UML/SysML: When sending a Signal (message) via a Port the 'target' is the owner of the Port through which the message will be sent, it is NOT the final recipient! So the 'target' is essentially the "sender"! SysML-1.6, UML-2.5.1 SendSignalAction::target, InvocationAction::onPort
ASSERTION Cameo: UML: When sending a Signal via a Port with a SendSignalAction, Cameo does not care whether the Port is conjugated (even if it should). UML-2.5.1 SendSignalAction, Signal, Port, Interface Magic Model Analyst [Cameo Simulation Toolkit], Cameo Systems Modeler, Unified Modeling Language
TIP One of the most important reasons to use a Port to send a Signal is that only the connection context, not the sender, knows the ultimate recipient (at the end of a specific Connector). SysML-1.6, UML-2.5.1 Port, InvocationAction::onPort, SendSignalAction::target
ASSERTION Cameo: SysML: When sending a Signal via a Port with a SendSignalAction, Cameo does not care what the directed feature directions of the Signal receptions on the Type of the Port are (even if it should). SendSignalAction, Signal, Port ~InterfaceBlock, InterfaceBlock Magic Model Analyst [Cameo Simulation Toolkit], Cameo Systems Modeler, Systems Modeling Language
FEATURE, TIP, TOOL Cameo: You can create a Simulation Configuration element in a Simulation Configuration Diagram (and you may then copy it to a BDD or Package Diagram if desired). Magic Model Analyst [Cameo Simulation Toolkit], Cameo Systems Modeler, simulation
FEATURE, TIP, TOOL MagicDraw/Cameo: You can import excel spreadsheets with data into instance tables easily! instance, InstanceSpecification, Slot, InstanceSpecification::slot MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
ASSERTION The SysML InterfaceBlock can be used for general contracts (it is NOT just for use as the Type of a ProxyPort)! InterfaceBlock design-by-contract, contract
MODELLING, NAMING, TIP 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 Property, Stereotype, custom Stereotype, «keyword» constraint parameter, ConstraintBlock, value property, MD:ConstraintParameter Webel Best Practice
TIP, TOOL MDSysML/Cameo: Unless a custom ValueType is otherwise specified through specialisation it is behaves like a Real for the purposes of data entry for value properties typed by that ValueType ValueType, value property, Real Cameo Systems Modeler, MagicDraw SysML
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»
POLICY In the Webel Parsing Analysis recipe you are not obliged to map every single part of a Snippet's text extract to a UML or SysML model, just traceably elicit model elements of immediate or anticipated interest to your task or goal. Webel Parsing Analysis
TIP, TOOL MagicDraw/Cameo: A structured ValueType can have value properties (each typed by a ValueType), but they list in an 'attributes' compartment (not a 'values' compartment) SysML-1.6 ValueType, Block, value property, structured ValueType MagicDraw SysML, Cameo Systems Modeler
OPTION Computed category membership test values are sometimes adequate and can prevent Class/Block explosion. However, a dedicated Class/Block encapsulating a clear domain concept offers a clear documentation point and can carry other characterising features. Class Block, value property, Boolean Webel Best Practice
PATTERN, TIP Webel Parsing Analysis for SysML - simplified profile Stereotype, custom Stereotype, Extension, Generalization, Actor ElementGroup Webel Parsing Analysis
TIP In Webel Parsing Analysis tutorials, Wikipedia pages are often used as a placeholder sources to represent authoritative domain source documents from which text extract "snippets" are sourced, and from which SysML model elements are traceably elicited. Webel Parsing Analysis, Wikipedia
TIP In professional applications of the Webel Parsing Analysis recipe for SysML, a robust reusable profile for «part»/«assembly»/«leaf» components is used, along with stereotypes keywords like «assembles» for indicating physical composition hierarchies. AggregationKind Block, block property Webel Best Practice, WPA:«assembles», WPA:«part», WPA:«leaf», WPA:«assembly», composition hierarchy
PATTERN In the Webel recipe for UML/SysML, the pattern of progressive redefinition of end Properties of Associations between progressively more specialised pairs of Blocks at the same level of abstraction is informally called a "redefinition ladder" Generalization, Association, Property::redefinedProperty, Association::memberEnd Block, block property Webel Best Practice
TIP Do export your UML/SysML presentation diagrams (only, not every diagram) regularly as static images; it will help you develop diagrams that are better balanced and communicate well with stakeholders. Webel Best Practice
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»
PROPOSAL Webel: WISHLIST for SysML: explicit support for showing "secondary" stereotype keywords on Connectors typed by Associations with stereotypes applied. Systems Modeling Language, Webel:WISHLIST
POLICY, STYLE A "staging" BDD for defining the flows, ports, and item properties on blocks to be used in an IBD does not have to be a "work of art" if it is not intended as a final presentation diagram. Port SysML Block Definition Diagram, Block, InterfaceBlock, ~InterfaceBlock, FlowProperty Webel Best Practice
PROPOSAL WISHLIST: Webel has suggested that future SysML should support the display of Classifier-level :features in compartments on a rectangular itemProperty symbol on an ItemFlow on a Connector in an IBD. SysML-1.6, SysML-1.7, SysMLv2 ItemFlow, ItemFlow::itemProperty SysML, Systems Modeling Language, Webel:WISHLIST, SysMLv2:WISHLIST
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»
CAPABILITY, FEATURE, TOOL MagicDraw/Cameo supports embedding images in diagrams Magic Model Analyst [Cameo Simulation Toolkit], MagicDraw SysML, MagicDraw UML
DISPLAY, STYLE, TOOL In Package Diagrams and Block Definition Diagrams use the owner indicator display option for Classifier symbol headers to indicate the owner (except where a containment operator suffices). The mode 'Below Element Name' is preferred. Element::owner, owner path display SysML Block Definition Diagram, SysML Package Diagram Webel Best Practice, Cameo Systems Modeler, MagicDraw SysML
CAVEAT, ISSUE The markup of Snippet page titles on this CMS web site is sometimes restricted (especially concerning subscripts and superscripts such as used in mathematical and scientific notation). Visit the linked Snippet page for the quote with full markup. Drupal8
OPTION TIP: If you use the name '0-source' instead of 'source' for the top-level Package/Model for containing Parsing Analysis elements it will list nicely at the top of the containment tree. Package, Model Webel Parsing Analysis, parsing analysis, WPA:«pa», WPA:«document», WPA:«snippet»
DISPLAY, ISSUE, TOOL MagicDraw/Cameo: The tagged values HTML editor can't handle overlines or all macrons. MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
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
CAVEAT One limit of the SysML-1.6 ElementGroup for use as a Snippet in the v1.x version of Webel Parsing Analysis for SysML is that an ElementGroup is not directly relatable. SysML-1.6 ElementGroup Webel Parsing Analysis
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, TOOL GOTCHA: Cameo: If you run a parametrics calculation from an instance symbol in a diagram it will just show computed values in the simulation window; if you run from an Instance Table diagram it will populate the instance Slots with the computed values. SysML Parametric Diagram Magic Model Analyst [Cameo Simulation Toolkit], Cameo Systems Modeler, calculation, simulation
DISPLAY, FEATURE, TOOL MagicDraw/Cameo: TIP: tagged values with no specified type or String types optionally support HTML. tagged value Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
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 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
ASSERTION In Webel Parsing Analysis elicited model elements MUST eventually be moved out of the 'source' (or '0-source') Package/Model zone and under a main project Package/Model area. (Use the owner display option to check.) Webel Parsing Analysis, WPA:«pa», WPA:TargetModelZone, WPA:SourceInputZone
NAMING, TIP Suffix the "focus" BDD for a Block with .bdd so that it won't clash with a corresponding IBD on diagram export. Webel Best Practice
TIP In Webel Parsing Analysis every Package, Model, or Diagram used to perform Parsing Analysis MUST have the stereotype keyword «pa» applied, and MUST live under a top-level Model or Package 'source' separate from the rest of the project model. Webel Parsing Analysis, WPA:«pa»
DISPLAY, ISSUE, TOOL MagicDraw/Cameo: HOWTO share a "Block-to-Block" ItemFlow - that was created by 'Between Part Types' mode - between two Connectors. (FYI only, not a Webel-recommended technique.) InformationFlow ItemFlow Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
ASSERTION, TIP, TOOL, WARNING Webel: SysMLv1: MagicDraw/Cameo: AVOID the "default" SysML Item Flow Creation Mode 'Between Part Types' completely. Use 'Direct' mode, change it as soon as you start any SysML project under Options → Project → General → SysML [Helps prevent a clash/issue] SysML-1.6, SysML-1.7, UML-2.5.1 InformationFlow ItemFlow Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML
DISPLAY, ISSUE, TOOL SysMLv1: MagicDraw/Cameo: If redisplay of an Association with an InformationFlow or ItemFlow creates a strange extra dashed line with «ItemFlow» keywords (separate from the Association) just remove (only) that extra dashed line from the diagram. InformationFlow, InformationFlow::conveyed, InformationFlow::realization ItemFlow, SysML Block Definition Diagram Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
ASSERTION, DISPLAY, FEATURE, SETTINGS, TIP, TOOL Webel: MagicDraw/Cameo: STRONGLY RECOMMEND: On EVERY project of ANY kind set the Environment Perspective to 'Full Featured' and check the Expert box, even if you are a "novice". For SysML use 'Full-Featured' not just 'System Engineer'! Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML, SysML, Webel Best Practice
ASSERTION, DISPLAY, FEATURE, MODELLING, SETTINGS, TIP, TOOL 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). SysML-1.6, SysML-1.7, UML-2.5.1 Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML, Webel Best Practice
ASSERTION, DISPLAY, FEATURE, MODELLING, SETTINGS, TIP, TOOL 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! SysML-1.6, SysML-1.7, UML-2.5.1 Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
DISPLAY, FEATURE, SETTINGS, TIP, TOOL MagicDraw/Cameo: HOWTO turn off verbose context information in SysML-style diagram frames Diagram, Element, frame MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML, drag-n-drop
DISPLAY, FEATURE, SETTINGS, STYLE, TIP, TOOL 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). Diagram, Element, symbol, Stereotype, icon MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML
DISPLAY, FEATURE, SETTINGS, STYLE, TIP, TOOL 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. Diagram, Element, symbol, Stereotype, tagged value MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML
FEATURE, TIP, TOOL 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 Diagram, Element, symbol, Stereotype MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML