Community
Participate
Working Groups
The property view for a FinalState (see clause 14.5.2 in [UML 2.5]) is not correct. Indeed, the "UML" tab enable the possibility to assign an entry, an exit or a doActivity behavior to a final state. This shall not be possible since clause 14.5.2.4 in [UML 2.5] specifies that: 1] inv: exit->isEmpty() 2] inv: entry->isEmpty() 3] inv: doActivity->isEmpty() In addition, the advanced tab provides the capability for a final state to have a sub-machine. This shall not be possible since inv: submachine->isEmpty()