UML 2.5 FTF Avatar
  1. OMG Issue

UML25 — Notation for state machine specializations

Open Closed All
  • Key: UML25-478
  • Legacy Issue Number: 18248
  • Status: closed  
  • Source: NASA ( Dr. Nicolas F. Rouquette)
  • Summary:

    In chapter 14, the notation for state machine specializations uses <<extended>> and

    {final}.


    <<extended>> is defined as a constraint-based keyword for a Region or a StateMachine.
    However, the notation in 14.3.4 clearly indicates that a state can be extended.
    There should be a new entry in the keyword table specifying the constraint-based application
    of the extended keyword to a State that has a non-empty redefinedState.


    The notation only covers the possibility of a modeler declaring states and transitions as {final}

    .
    Conceptually, a modeler should also be able to declare a region as

    {final}.
    There is no definition for what {final}

    is. Since it requires explicit declaration from the modeler,
    it should be defined as a stereotype-based keyword notation with a new stereotype <<final>> defined in the UML standard profile.

    <<extended>> and

    {final}

    should be explicitly defined in the semantics section in 14.3.3.
  • Reported: UML 2.5b1 — Mon, 5 Nov 2012 05:00 GMT
  • Disposition: Resolved — UML 2.5
  • Disposition Summary:

    Merged with 12380
  • Updated: Fri, 6 Mar 2015 20:59 GMT