1. OMG Issue

UML14 — page 2-163, the statemachine semantics escription

  • Key: UML14-13
  • Legacy Issue Number: 4508
  • Status: closed  
  • Source: Anonymous
  • Summary:

    I am reading the UML 1.4 draft specification. On page 2-163, the statemachine semantics are described. There is the following semantic defined: [3] A top state cannot have any containing states>isEmpty

    I find the text description a little bit strange. The text wants to say that the top state cannot be contained in a container state. Maybe something to refrase in the next draft? At least it should a a containing state, because a state can only be contained into 1 composite state.

    On page 2-168 the behaviour when exiting a concurrent state is described. So far as I can see there is no guarantee about the order in which the exit actions of the regions are executed. So a design in which the exit actions are dependent on each other is a malformed design. Maybe something to add?

    On page 2-176, in the c++ example, there is a small error. After the code "balance = balance + amount" a ";" is missing.

  • Reported: UML 1.3 — Fri, 17 Aug 2001 04:00 GMT
  • Disposition: Resolved — UML 1.4
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 20:58 GMT