-
Key: UMLR-196
-
Legacy Issue Number: 14936
-
Status: open
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
Current timing model does not enable useful capture/mapping of values vs time. UML does support initial values and current values, but not evolving values. This is necessary for proper description of the behavior, capture of simulations, requirements development
-
Reported: UML 2.5 — Mon, 11 Jan 2010 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
UMLR — UML: Need more robust value model that would enable capture of values vs time
- Key: UMLR-196
- OMG Task Force: UML 2.6 RTF