Figure D.26 - Defining Analyses for Hybrid SUV Engineering Development (Block Definition 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
UML keywords
AggregationKind::none
AggregationKind::composite
SysML keywords
HSUV sample problem
ConstraintBlock
nested ConstraintBlock
constraint property
constraint parameter
MD:ConstraintParameter
Block
SysML Block Definition Diagram
Verify
TestCase
Keywords
Slide kind
SysML Block Definition Diagram (BDD)
In the spec figure this diagram is called 'Analysis Context'.
Click on the image to view it full size
While for the sake of illustration in the spec names like PayloadEquation might serve a purpose, it is not Webel Best Practice:
Webel: SysML: You don't need to call every ConstraintBlock a 'SomethingEquation'
Webel: "Trust the Metaclass or Stereotype" of an Element to indicate what type of element it is (you don't have to repeat it in the name)

You can in any case display the «constraint» keyword.

In the spec figure, the name StraightLineVehicle Dynamics has a space, in the trail figure it's just StraightLineVehicleDynamics:

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')!

Rather than include the HSUV Structure Package and a containment operator to indicate ownership of AutomotiveDomain, this trail version uses the owner path indicator.

SysMLv1/UML: Prefer owner path indicators over Package containment operators (which are fragile).

This trail uses lower case constraint parameter names v1, v2, v3:

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
Up next
Figure D.27 - Establishing a Performance View of the User Model (Package Diagram)
Notes
[NAMING]{SUGGESTED} Webel: SysML: You don't need to call every ConstraintBlock a 'SomethingEquation'
[NAMING, STYLE]{STRONG} Webel: "Trust the Metaclass or Stereotype" of an Element to indicate what type of element it is (you don't have to repeat it in the name)
[DISPLAY, STYLE, TIP] As an alternative to composition Association "trees" consider instead using symbol resize to visually "bracket" composed items (can however be a bit fiddly).
[CAVEAT, DISPLAY, STYLE, WARNING] MagicDraw/Cameo tool support for Association composition "trees" is not good, and they end up being fiddly to maintain (and they can also cause issues for InformationFlows). Avoid them!
[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')!
[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] SysML-1.6: Figure D.31 has constraint parameter 'vc' on ':CapacityEquation', which is inconsistent w.r.t. parameters 'V1', 'V2', 'V3' and constraint {pcap=Sum(Vi)) shown in Figure D.26.
[ISSUE] SysML-1.6: Figure D.32 aggregation kind on 'delta-t' is inconsistent w.r.t. Figure D.26
Snippets (quotes/extracts)
  [SysML-1.6] Figure D.26 defines the various model elements that will be used to conduct analysis in this example. It depicts each of the constraint blocks/equations that will be used for the analysis, and key relationships between them.
  [SysML-1.6] A constraint block is a block that packages the statement of a constraint so it may be applied in a reusable way to constrain properties of other blocks.
  [SysML-1.6] A constraint block typically defines one or more constraint parameters, which are bound to properties of other blocks in a surrounding context where the constraint is used.
  [SysML-1.6] All properties of a constraint block are constraint parameters, with the exception of constraint properties that hold internally nested usages of constraint blocks.
  [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] Constraint blocks provide a mechanism for integrating engineering analysis such as performance and reliability models with other SysML models.
  [SysML-1.6] Constraint blocks can be used to specify a network of constraints that represent mathematical expressions such as {F=m*a} and {a=dv/dt}, which constrain the physical properties of a system.
  [SysML-1.6] A constraint block includes the constraint, such as {F=m*a}, and the parameters of the constraint such as F, m, and a.
  [SysML-1.6] Constraint blocks define generic forms of constraints that can be used in multiple contexts. For example, a definition for Newton’s Laws may be used to specify these constraints in many different contexts.
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)
Visit also
Visit also (backlinks)
SysMLv1: Cameo Simulation Toolkit: GOTCHA: In SysMLv1 it is "officially" recommended that an analysis context Block has a reference (only) to the subject of the analysis (but then you need to assign an instance as default value to make it run IN THE TOOL)