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
MagicDraw/SysML vs SysPhS-1.1: Can't reproduce the "shortcut" property path representation of some properties nested within Ports as shortcut symbols fully inside the diagram frame. (Might be a specification diagram style issue.)
Parametric diagrams: Figure 62, Figure 63 Gallery Tutorial TRAIL: SysPhS-1.1 Annex A examples in MagicDraw SysML (or Cameo Systems Modeler) vs Modelica (Wolfram SystemsModeler) Section Annex A.4: Hydraulics Slide kind hybrid diagram SysML Parametric Diagram
Parametric diagrams: Figure 41, Figure 42, Figure 43, Figure 44, Figure 45 Gallery Tutorial TRAIL: SysPhS-1.1 Annex A examples in MagicDraw SysML (or Cameo Systems Modeler) vs Modelica (Wolfram SystemsModeler) Section Annex A.2: Electric Circuit Slide kind hybrid diagram SysML Parametric Diagram
Figure 25: Constraint block for signal flow in SysML Gallery Tutorial TRAIL: SysPhS-1.1 specification body figures in MagicDraw SysML (or Cameo Systems Modeler) vs Modelica [using Wolfram SystemsModeler] Section Slide kind hybrid diagram SysML Block Definition Diagram (BDD) SysML Parametric Diagram
parametric diagrams can make use of the nested property name notation to refer to multiple levels of nested property containment, as shown in this example. Source OMG Systems Modeling Language (SysML) 1.6
Figure D.32 shows the use of constraint properties on a parametric diagram. This diagram shows the use of nested property references to the properties of the parts; Source OMG Systems Modeling Language (SysML) 1.6
Figure 8-1: Nested property reference Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6 specification diagrams: 08 Blocks Slide kind SysML Block Definition Diagram (BDD)
The Allocate stereotype specializes DirectedRelationshipPropertyPath to enable allocations to identify their sources and targets by a multi-level path of accessible properties from context blocks for the sources and targets. Source OMG Systems Modeling Language (SysML) 1.6
MagicDraw/Cameo: HOWTO Create a nested Property "shortcut" symbol with a dot property path in a Parametric Diagram or Internal Block Diagram
If the property has no name, the property’s type name can be used instead. e.g., car:Engine:Cylinder:Piston.length car.e.c.p.length Source OMG Systems Modeling Language (SysML) 1.6
In other words, the internal property shown with a path name in the left-hand side of Figure 8-1 is equivalent to the innermost nested box shown at the right. Source OMG Systems Modeling Language (SysML) 1.6
This notation is purely a notational shorthand for a property that could otherwise be shown within a structure of nested property boxes, with the names in the dotted string taken from the name that would appear at each level of nesting Source OMG Systems Modeling Language (SysML) 1.6
If any of the properties named in the path name string identifies a reference property, the property box is shown with a dashed-outline box, just as for any reference property on an internal block diagram. Source OMG Systems Modeling Language (SysML) 1.6
A colon and the type name for the property may optionally be shown following the dotted name string. Source OMG Systems Modeling Language (SysML) 1.6
The name of the referenced property is built by a string of names separated by “.”, resulting in a form of path name that identifies the property in its local context. Source OMG Systems Modeling Language (SysML) 1.6
A property name shown inside or outside the property box may take the form of a multi-level name. This form of name references a nested property accessible through a sequence of intermediate properties from a referencing context. Source OMG Systems Modeling Language (SysML) 1.6
As with any connector owned by a SysML Block, the ends of a binding connector may be nested within a multi-level path of properties accessible from the owning block. The NestedConnectorEnd stereotype is used to represent such nested ends just as for ... Source OMG Systems Modeling Language (SysML) 1.6
