Legacy Issue Number: 3243
Source: OpenModeling ( Jos Warmer)
The metaclass ClassifierInState is unneccesary and can be replaced by
In a number of cases a specific ClassifierInState is not needed. When e.g.
a ClassifierRole always has certain restrictions, these restrictions can be
modeled with a Constraint (stereotypes as <<invariant>>) on the
The use of ClassifierInState in activity graphs is to show the output or input
parameter to actions. The same concept can be modeled in a unified way by
using existing preconditions and postconditions.
To denote that an object must be in a state after the action can be modeled
<<postcondition>> Constraint attached to the action state.
To denote that an object must be in a state before the action can be
modeled by a
<<precondition>> Constraint attached to the action state.
An action is a piece of behavior and can have pre- and postconditions attached
to it. using that, the ClassifierInState might turn out to be superfluous.
Remove ClassifierInState metaclass and replace it by a description how
metaclasses can be used to solve the same modeling problem.
Reported: UML 1.2 — Thu, 24 Feb 2000 05:00 GMT
Disposition: Resolved — UML 1.3
Updated: Fri, 6 Mar 2015 21:37 GMT
UML14 — ISSUE FOR UML, SECTION ActivityGraphs
- Key: UML14-983
- OMG Task Force: UML 1.4 RTF