Figure D.24 - Defining Fuel Flow Constraints (Parametric Diagram)

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: HSUV sample
SysML keywords
ConstraintBlock
BindingConnector
constraint property
SysML Parametric Diagram
NestedConnectorEnd
Slide kind
SysML Parametric Diagram
Click on the image to view it full size
There are some differences compared with the spec version.

The context kind in the diagram shows as '[Subsystem]' because the custom stereotype keyword «subsystem» has been applied to PowerSubsystem

The «equals» keyword has been explicitly shown on the BindingConnectors.

The "secondary stereotype" keywords «valueType» and «constraint» from the underlying classifiers have been shown.

The value flow rate constraint parameter has been renamed flowRate according to Webel Best Practice:

DO NOT use spaces in Property names or Class/Block names! If you want to communicate familiar names of elements within an organisation use a custom stereotype and tagged values (such as 'aka')!
SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase

Elsewhere in the spec there are inconsistent name references:

SysML-1.6: Naming inconsistencies 'Figure D.24 is a parametric diagram showing how fuel flowrate is related to FuelDemand and FuelPressure value properties.'

The next slide shows an annotated version of the same figure.

Up next
Figure D.24 - Defining Fuel Flow Constraints (Parametric Diagram) [ANNOTATED]
Notes
[ISSUE] SysML-1.6: Figure D.24 does not explicitly show «equal» keyword or '=' on BindingConnectors [suggest this might be good to show this notation on at least one HSUV sample diagram]
[NAMING, POLICY]{STRICT} DO NOT use spaces in Property names or Class/Block names! If you want to communicate familiar names of elements within an organisation use a custom stereotype and tagged values (such as 'aka')!
[CAPABILITY, FEATURE, TIP, TOOL] In MagicDraw/Cameo an assigned stereotype of a Classifier that types an instance-like element (such as a part Property) "shines through" unless it has an instance-level stereotype assigned. This is sometimes called a "secondary stereotype".
[ASSERTION, TOOL] SysML: The «system», «subsystem», «external», «domain» and «system context» keywords are for "user defined" block Stereotypes (they are not part of core SysML); they are supported in MagicDraw/Cameo as Non-Normative Extensions.
[NAMING, POLICY]{STRICT} SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase
[ISSUE, NAMING] SysML-1.6: Naming inconsistencies 'Figure D.24 is a parametric diagram showing how fuel flowrate is related to FuelDemand and FuelPressure value properties.'
[TOOL] MagicDraw/Cameo: HOWTO Create a nested Property "shortcut" symbol with a dot property path in a Parametric Diagram or Internal Block Diagram
Snippets (quotes/extracts)
  [SysML-1.6] Figure D.24 is a parametric diagram showing how fuel flowrate is related to FuelDemand and FuelPressure value properties.
  [SysML-1.6] A Binding Connector is a connector which specifies that the properties at both ends of the connector have equal values.
  [SysML-1.6] If the properties at the ends of a binding connector are typed by a ValueType, the connector specifies that the instances of the properties shall hold equal values, recursively through any nested properties within the connected properties.
  [SysML-1.6] A constraint property is a property of any block that is typed by a constraint block. It holds a localized usage of the constraint block. Binding connectors may be used to bind the parameters of this constraint block to other properties of the block ...
  [SysML-1.6] Binding connectors, as defined in Clause 8 are used to bind each parameter of the constraint block to a property in the surrounding context.
  [SysML-1.6] A parametric diagram is defined as a restricted form of internal block diagram. A parametric diagram may contain constraint properties and their parameters, along with other properties from within the internal block context.
  [SysML-1.6] All properties that appear, other than the constraints themselves, shall either be bound directly to a constraint parameter, or contain a property that is bound to one (through any number of levels of containment).
  [SysML-1.6] A constraint property may be shown on a parametric diagram using a rectangle with rounded corners. This graphical shape distinguishes a constraint property from all other properties and avoids the need to show an explicit «constraint» keyword. Otherwise..
  [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.
  [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.
  [SysML-1.6] A constraint block is defined by a keyword of «constraint» applied to a block definition. Properties of this block define parameters of the constraint, with the exception of properties that hold internally nested usages of constraint blocks.
  [SysML-1.6] The usage of a constraint block is distinguished from other parts by a box having rounded corners rather than the square corners of an ordinary part.
  [SysML-1.6] A parametric diagram is a restricted form of internal block diagram that shows only the use of constraint blocks along with the properties they constrain within a context.
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)
Useful "user-defined" stereotypes for Blocks: «system context», «system», «subsystem», «external», «domain»