UML14 — ISSUE FOR UML, SECTION ActivityGraphs

Description:
------------
The metaclass ClassifierInState is unneccesary and can be replaced by
existing metaclasses.

Discussion
-----------
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
ClassifierRole.

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
by a
<<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.

Solution
--------
Remove ClassifierInState metaclass and replace it by a description how
existing
metaclasses can be used to solve the same modeling problem.

declined