-
Key: UML25-379
-
Legacy Issue Number: 17993
-
Status: closed
-
Source: University of Texas ( Omar Badreddin)
-
Summary:
I think this is also new specification in UML 2.5. If so, it should be added to the summary of new specifications at the beginning of the document.
This is a feature with some value. The question is the following. Does this feature brings more value than the complexity it adds to the specification and the tools that supports UML? My view is that such a feature adds more avoidable complexity to the tools. At the same time, the same behavior can be achieved using the already existing UML features. I would vote against this feature in favor of keeping the specifications less complex
-
Reported: UML 2.4.1 — Thu, 27 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
The submitter is mistaken. Deferred events have always been a part of UML state machines.
Disposition: Closed - No Change -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Location: p. 330 Deferred Events - Value of Deferred Events
- Key: UML25-379
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF