UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — UML SuperStructure - Inconsistency re State Machine terms

  • Key: UML22-146
  • Legacy Issue Number: 8967
  • Status: closed  
  • Source: Anonymous
  • Summary:

    think there is some inconsistency in your usage of terms
    in chapter 15 State Machines.

    It isn't really clear (I think) what you mean sometimes when
    you use the terms "state machine" "behavioral state machines"
    and "protocol state machines".

    In my (humble) opinion you should never use only the term
    "state machine" when you do not mean both "behavioral state
    machine" and "protocol state machine".

    15.3.12 is a perfect example where I think there is confusion,
    or at least lack of clarity, since you talk about "state machines" executing "activities". Clearly, not all state machines do--
    more precisely--protocol state machines don't.

  • Reported: UML 2.0 — Tue, 16 Aug 2005 04:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    Discussion
    This issue was resolved by the UML 2.5 convention of using explicit meta-class names (e.g., StateMachine and ProtocolStateMachine)
    and by isloating the two types of state machines into distinct sections of the spec.
    Disposition: Closed - No Change

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