-
Key: UML14-80
-
Legacy Issue Number: 4734
-
Status: closed
-
Source: Anonymous
-
Summary:
According to the UML 1.4 standard, an Event is defined as "...a
specification of a type of observable occurrence" [UML 1.4, pp. 2-150]. It
is used exclusively in the context of state machines, as triggers of state
transitions [UML 1.4, pp. 2-147, fig. 2-24].Because Event is a direct subclass of ModelElement - and because no other
composite containments are specified for Event or any of its subclasses - it
must be compositely contained as an ownedElement in a ClassifierRole, Model.
Package, Artifact or Node (all other concrete subclasses of Namespace have
restricted their owned elements to exclude Event).The question is: is this containment intended, or should an Event be
contained in e.g. the StateMachine in which it is used? If the currently
allowed containment IS intended, please explain the semantics of e.g. an
Event contained in an otherwise empty Package (or even Model). -
Reported: XMI 1.3 — Wed, 5 Dec 2001 05:00 GMT
-
Disposition: Resolved — UML 1.4.2
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT