Legacy Issue Number: 12353
Source: No Magic, Inc. ( Darren Kelly)
As discussed at the OMG TM SysML RTF on Th 13Mar2008. Assumes the property-specific 'defaultValue' compartment has been renamed to 'initialValue' (or perhaps 'initialValues'), as suggested in a previous issue submission. The case of a property-specific 'initialValues" compartment (as in Table 8.3 - Graphical nodes defined in Internal Block diagram) and also deeply nested "initial values" is well complemented by a "values" or "currentValues" compartment, as illustrated for the test results in Figure 8.11 - SUV EPA Fuel Economy Test. Together, the "initialValues" and "values" compartments illustrate usefully the evolution of the value state of a system used within an additional top-level "value slice" context. Tool vendors would be free to show one, both, or none of these two complementary compartment in part Properties of an IBD. This strategy promotes progress towards animation of systems, and also enables comparison of special configurations with an "initial" configuration/state. This suggestion represents a useful unification of concepts already present in the SysML specification.
Reported: SysML 1.0 — Fri, 21 Mar 2008 04:00 GMT
Disposition: Resolved — SysML 1.1
This issue was raised prior to the SysML 1.1 adoption of the "initialValues"
compartment on properties on an ibd to specify context-specific initial property
values, and the SysML 1.2 adoption of UML instance specifications to specify
current or sample property values of specific block instances. Full support of
UML instance specifications was chosen by SysML 1.2 to support more complete
specification of instances, including links between instances, than a
"currentValues" compartment could directly support. The suggested capability
would be redundant with the capability already adopted by SysML 1.1 and
Disposition: Closed, no change
Updated: Fri, 6 Mar 2015 20:58 GMT