UML 1.4 NO IDEA Avatar
  1. OMG Issue

UML14 — Why is a StateMachine's top a State instead of a CompositeState?

Open Closed All
  • Key: UML14-46
  • Legacy Issue Number: 3569
  • Status: closed  
  • Source: MotionPoint ( Eugenio Alvarez)
  • Summary:

    Every StateMachine must have one top State. However, there is an
    OCL constraint that says that the top State must be a CompositeState
    (Semantics 2.12.3 Well-FormednessRules, StateMachine Section, rule [2], p
    2-141). So, why not make the top relationship from StateMachine to
    CompositeState instead of from StateMachine to State. The constraint can
    then be eliminated.
  • Reported: UML 1.3 — Tue, 18 Apr 2000 04:00 GMT
  • Disposition: Resolved — UML 1.4.2
  • Disposition Summary:

    No Data Available
  • Updated: Fri, 6 Mar 2015 20:58 GMT