Webel: SysMLv1: Dr Darren for LinkedIn: On "Trusting The Type" and avoiding unnecessary verbose repetitive Property names ... unless you really, really need them and really do have reasons to use them, and then only use concise role indicators anyway!
SysML1.x: MagicDraw/Cameo: The block property concept is implemented using a vendor-specific stereotype extension BlockProperty
Webel: WISHLIST: MagicDraw/Cameo: UML/SysML: Ability to freeze the Feature lines shown on symbols under Edit Compartments so that the diagram does not "break" when new Features are added elsewhere (reduce graphical coupling)
SysML/SysPhS-1.1: Anonymous Property or Action names may not be an option if: You are exporting to Modelica or Simulink; You absolutely need names for generated query reports (such as generated Interface Control Documents).
SysPhS-1.1: Annex A.5: Humidifier: Naming not very consistent across parts, input/output Port name, value properties, or constraint parameters
MagicDraw/Cameo: You can drag a Class symbol onto a Class symbol (in a Class Diagram) or a Block symbol or ValueType symbol onto or Block symbol (in a Block Definition Diagram) to create a new part property or value property
MagicDraw/Cameo: You can drag out a Property (or Port) from a Class or Block symbol to create an Association with the Property (or Port) as one end
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
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.
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.
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"
REFERENCE CARD: Property cheat-sheet for Block Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 08:01: The building Blocks of SysML Slide kind SysML Block Definition Diagram (BDD)
Instances with part-carrying Slots Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 08:02: The SysML ValueType, Unit, and using values Slide kind SysML Block Definition Diagram (BDD)
SysML also allows each usage to define context-specific values and constraints associated with the individual usage, such as 25 psi for the front tires and 30 psi for the rear tires. Source OMG Systems Modeling Language (SysML) 1.6
For example, a block that represents the definition of a wheel can be used in different ways. The front wheel and rear wheel can represent different usages of the same wheel definition. Source OMG Systems Modeling Language (SysML) 1.6
A part belonging to a block, for example, may be typed by another block. The part defines a local usage of its defining block within the specific context to which the part belongs. Source OMG Systems Modeling Language (SysML) 1.6
A property can represent a role or usage in the context of its enclosing block. A property has a type that supplies its definition. Source OMG Systems Modeling Language (SysML) 1.6
Various notations for properties are available to distinguish these specialized kinds of properties on an internal block diagram. Source OMG Systems Modeling Language (SysML) 1.6
Constraint Properties are a special class of property used to constrain other properties of blocks... Source OMG Systems Modeling Language (SysML) 1.6
Ports are a special class of property used to specify allowable types of interactions between blocks ... Source OMG Systems Modeling Language (SysML) 1.6
The specific kinds of components, the kinds of connections between them, and the way these elements combine to define the total system can all be selected according to the goals of a particular system model. Source OMG Systems Modeling Language (SysML) 1.6
Blocks provide a general-purpose capability to model systems as trees of modular components. Source OMG Systems Modeling Language (SysML) 1.6
REFERENCE CARD: Types of Block Properties and Block compartments Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 08:01: The building Blocks of SysML Slide kind SysML Block Definition Diagram (BDD)
ExampleBlock in an Internal Block Diagram (BDD) Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 08:01: The building Blocks of SysML Slide kind SysML Internal Block Diagram (IBD)
ExampleBlock in a Block Definition Diagram (BDD) Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 08:01: The building Blocks of SysML Slide kind SysML Block Definition Diagram (BDD)
Webel has a proposal for clearly revealing anonymous typed elements in SysML callouts and on derived Properties from operation queries.
SysML: Non-anonymous (concise please) block property names and port names may help a little in tracing participation of properties and ports in requirements relationships and play nicely with current SysML callout style. Short role indicators are best!
FullPort::2_not_bound_to_fullport Binding connectors shall not link full ports (either directly or indirectly through other binding connectors) to other composite properties of the block owning the full port (or that blocks generalizations or specializati Source OMG Systems Modeling Language (SysML) 1.6
Provided behavioral features are invoked with the owning block as target, while required behavioral features are invoked with an external block as target (required). Source OMG Systems Modeling Language (SysML) 1.6
Provided non-flow properties are read and written on the owning block, while required non-flow properties are read or written on an external block Source OMG Systems Modeling Language (SysML) 1.6
Using non-flow properties means to read or write them, and using behavioral features means to invoke them. Source OMG Systems Modeling Language (SysML) 1.6
MagicDraw/Cameo: Does not seem to support showing a trailing colon ':' in labels of Properties or Connectors that are untyped OR are typed by anonymous Classes, Blocks, or Associations. (The notation is used in some SysML specification diagrams.)
The context for the usages of constraint blocks shall also be specified in a parametric diagram to maintain the proper namespace for the nested properties. Source OMG Systems Modeling Language (SysML) 1.6
This allows a value property (such as an engine displacement) that may be deeply nested within a containing hierarchy (such as vehicle, power system, engine) to be referenced at the outer containing level (such as vehicle-level equations). Source OMG Systems Modeling Language (SysML) 1.6
A pathname dot notation can be used to refer to nested properties within a block hierarchy. Source OMG Systems Modeling Language (SysML) 1.6
The constrained properties, such as mass or response time, typically have simple value types that may also carry units, quantity kinds, or probability distributions. Source OMG Systems Modeling Language (SysML) 1.6
The usage of a constraint binds the parameters of the constraint, such as F, m, and a, to specific properties of a block, such as a mass, that provide values for the parameters. Source OMG Systems Modeling Language (SysML) 1.6
If the properties at the ends of a binding connector are typed by a Block, the connector specifies that the instances of the properties shall refer to the same block instance. Source OMG Systems Modeling Language (SysML) 1.6
