-
Key: UML25-377
-
Legacy Issue Number: 17991
-
Status: closed
-
Source: University of Texas ( Omar Badreddin)
-
Summary:
This is an area of intentional ambiguity. Why not just make a choice regarding a region with no start state? I would suggest that UML should allow a region without a start state and go with the second choice "the region remains inactive while the containing state is active."
-
Reported: UML 2.4.1 — Thu, 27 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
The reason this was defined as a variation point is to support the different semantics that were realized in various
existing state machine realizations (at least those that were of concern when UML 2.0 was being defined). Selecting
only one variant as the only valid one would be, in effect, a change in the semantics of UML, which would have an
impact on existing models.
Disposition: Closed - No Change -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Location: p. 328 Regions - Resolve intentional ambiguity
- Key: UML25-377
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF