The use of an «InitialValues» stereotype as illustrated in this trail is completely optional. It is there to support education and illustration, and to indicate that a given InstanceSpecification is "reserved" for use as a Property.defaultValue of a Property of the same or compatible Type.
Users can choose to assign an «InitialValues» stereotype to an InstanceSpecification using the standard stereotype assignment mechanisms.
The Block of a Property that the «InitialValues» InstanceSpecification initialises will know the «InitialValues» InstanceSpecification simply as the Property.defaultValue of the owned Property (which can be achieved in MD SysML by dragging the InstanceSpecification onto the Property in an IBD, or via the Property specification box default value field).
It does not matter at all:
- which element owns the «InitialValues» instance
- OR how many properties the «InitialValues» instance is assigned to
- OR which blocks own the targeted properties.
(*) It has been suggested that the SysML1.0 defaultValue compartment on a part in an IBD should be renamed initial values
