-
Key: SYSML17-39
-
Legacy Issue Number: 15003
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
Do parametric bindings observe derived and read-only constraints on properties?
.
In SysML if I bind a read-only property value to a parameter, I would expect that any evaluation of the parametric model would not be able to update the property value. If I wanted to have such a value calculated, I would expect to take off the read-only constraint
Similarly, if I bind a derived property value to a parameter, I would expect that any evaluation of the parametric model would not use that value as an input, but only as an output.
However, this is answered (and I hope it is answered positively), the SysML specification should clarify this behavior
-
Reported: SysML 1.4 — Fri, 22 Jan 2010 05:00 GMT
-
Disposition: Closed; No Change — SysML 1.7
-
Disposition Summary:
ConstraintBlock is a constraint no a mechanism
A ConstraintBlock is intended to represent a constraint that can happen to be met or violated. Tools vendors providing simulation facilities may want to implement a synchronization mechanism based on it but it's not required by this specification. If such a mechanism is provided, it is expected that either the tool will enforce the constraint or will notify a constraint violation if any. But again, this is not part of this specification.
-
Updated: Thu, 22 Dec 2022 13:45 GMT
SYSML17 — Do parametric bindings observe derived and read-only properties
- Key: SYSML17-39
- OMG Task Force: SysML 1.7 RTF