-
Key: UML22-54
-
Legacy Issue Number: 8071
-
Status: closed
-
Source: GOO Tech ( Birol Berkem)
-
Summary:
In the UML 1.x, we have the notion of ClassifierInState. We used them for representing associations and methods of classes that are valid when instances of these classes are in the corresponding states.
Could you let me know how to do that using UML 2 ? If class-in-states are not supported in UML 2.0, I am afraid, we cannot represent these valuable information particularly for reifying business processes. For example Order[Delivery] , Order[Billing], etc.. with their operations and session attributes !
-
Reported: UML 1.4.2 — Tue, 4 Jan 2005 05:00 GMT
-
Disposition: Resolved — UML 2.2
-
Disposition Summary:
This is really a question of clarification of a misunderstanding of the submitter. The equivalent of ClassifierInState for activity modeling is supported in UML 2 by the ObjectNode inState association. UML 1 also allowed ClassifierInState to be used in instance and collaboration modeling. While there is no direct equivalent for this in UML 2, the same effect can be achieved by using an OCL constraint on an instance.
-
Updated: Fri, 6 Mar 2015 20:58 GMT