Issue 18248: Notation for state machine specializations (uml25-ftf) Source: NASA (Dr. Nicolas F. Rouquette, nicolas.f.rouquette(at)jpl.nasa.gov) Nature: Uncategorized Issue Severity: 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. Resolution: Revised Text: Actions taken: November 5, 2012: received issue Discussion: End of Annotations:===== m: "Rouquette, Nicolas F (313K)" To: "issues@omg.org" CC: "uml25-ftf@omg.org" Subject: Notation for state machine specializations Thread-Topic: Notation for state machine specializations Thread-Index: AQHNu5iUaQ8CYNEwSkKc4W90NZv/QQ== Date: Mon, 5 Nov 2012 21:00:25 +0000 Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 x-originating-ip: [128.149.137.113] X-Source-Sender: nicolas.f.rouquette@jpl.nasa.gov X-AUTH: Authorized In chapter 14, the notation for state machine specializations uses <> and {final}. <> 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 <> defined in the UML standard profile. <> and {final} should be explicitly defined in the semantics section in 14.3.3. - Nicolas.