-
Key: UML25-361
-
Legacy Issue Number: 17969
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
Title: Relative to what?
The concept of relative TimeEvent does not make sense unless a base Event is identified. This should be reflected in the metamodel diagrams and definitions. This is often a problem with timers in activity diagrams. -
Reported: UML 2.4.1 — Thu, 27 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
Note: The correct Notation subclause reference is 13.3.4, not 13.2.4.
In Subclause 13.3.3, under Time Events, it states “Relative TimeEvents shall always be used in the context of a Trigger,
and the starting point is the time at which the Trigger becomes active.”
Disposition: Closed - No Change -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Location: Page 313, 13.2.4 Notation relative
- Key: UML25-361
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF