UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — Section: Common Behavior (02)

Open Closed All
  • Key: UML22-153
  • Legacy Issue Number: 9002
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    The semantics of TimeEvent uses undefined term "active". State machines uses the term for states, not triggers. Need definition independent of state machines in any case.
  • Reported: UML 2.0 — Sun, 25 Sep 2005 04:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    The UML 2.5 beta specification still uses the phrase “time at which the Trigger becomes active” in 13.3.3
    under “Time Events”. The intended idea seems to be what is now discussed earlier in 13.3.3 under “Even
    Dispatching”: a Behavior may come to a “wait point” at which it has a number of “outstanding Triggers”.
    For any such Triggers with a relative TimeEvent, the starting point should be the time at which the Behavior
    comes to the wait point.
  • Updated: Fri, 6 Mar 2015 20:58 GMT