-
Key: UML14-382
-
Legacy Issue Number: 6454
-
Status: closed
-
Source: Anonymous
-
Summary:
14.3: StateInvariant and ExecutionOccurrence are both subclasses of InteractionFragment. "Each interaction fragment is conceptually like an interaction by itself." [14.3.9] And, indeed, "An ExecutionOccurrence is an instantiation of a unit of behavior..." [14.3.4] But, "A StateInvariant is a constraint on ... state..." [14.3.17] That's not like an interaction by itself, nor like any interaction at all. We've mixed models of behavior with specifications of constraints on state.
This is an example of a recurrent problem in the specification: subclasses that are not like their superclasses.
...Suggested resolution: Review the specification with this in mind and correct all improper subtyping
-
Reported: UML 1.5 — Fri, 7 Nov 2003 05:00 GMT
-
Disposition: Resolved — UML 1.4.2
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT