UML14 — Adding events to the class definition

The proposal is to add an optional fourth compartment to the
class artifact that lists events that are accepted by that
class.

If a class is 'Active', it will have an associated
state/activity model. This state/activity model will respond to
events sent to that class. At the moment the only way to
determine what events can be accepted by a class is to observe
its state/activity model. Very clumsy!

A workaround is to list events in the operations compartment
and label them with an appropriate stereotype <<event>> for
example. This should only be a temporary solution, since events
are no more operations than they are attributes.

Events need to be part of the class definition.

No Data Available