-
Key: UML14-987
-
Legacy Issue Number: 3274
-
Status: closed
-
Source: NIST ( Mr. Conrad Bock)
-
Summary:
States currently do not model the conditions required for an
object to be in a particular state. A constraint note can be
linked to a state, but there is no specification of when the
constraint should be tested. It could be tested when the object
enters the state, leaves the state, or at any other time. Even if
this were unambiguous, the consequence of violating the constraint
is not defined, namely, to transition the machine to a state that
has a constraint satisfied by the object. This might be modeled
as a change-event trigger on an exiting transition, but it would
be redundant with the constraint recorded on the state and with
triggers on other transitions leaving the state, thereby impairing
maintainability. -
Reported: UML 1.2 — Sat, 5 Feb 2000 05:00 GMT
-
Disposition: Resolved — UML 1.3
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 21:37 GMT
UML14 — UML RTF 1.4 Issue: State constraint on host object
- Key: UML14-987
- OMG Task Force: UML 1.4 RTF