In MD SysML, UML-style "inline" {constraints} are displayed in the header, consistent with the SysML1.0 spec, which states:
8.3.1.1 Block Definition Diagram ..
Constraints compartment
'SysML defines a special form of compartment, with the label “constraints,” which may contain one or more constraints owned by the block. A constraint owned by the block may be shown in this compartment using the standard text-based notation for a constraint, consisting of a string enclosed in brace characters. The use of a compartment to show constraints is optional. The note-based notation, with a constraint shown in a note box outside the block and linked to it by a dashed line, may also be used to show a constraint owned by a block.'
Future versions of the MD SysML Plugin will support a 'constraints' compartment for nested constraints (constraint properties of constraint blocks):
'A constraints compartment may also contain declarations of constraint properties owned by the block. A constraint property is a property of the block that is typed by a ConstraintBlock, as defined in Chapter 10, “Constraint Blocks.”'
Visit also:
Concerning types of values in this diagram:
There is still some contention in the SysML community about the correct use of Unit and/or ValueType to type value properties and the spec samples are inconsistent in this regard.
In the MD SysML Plugin version of the Hybrid SUV sample these ValueTypes have been named like the kinds of domain quantities they represent, as in the Annex B of the sample, for use in parametric diagrams. Note however that in other diagrams in the SysML1.0 specification (not in Annex B) there are value types that are named after the symbol of their units, so that value properties typed by them read like most scientist and engineers would expect., namely as representations of quantities with measured or stated values relative to a Unit scale.
