-
Key: UML25-497
-
Legacy Issue Number: 18455
-
Status: closed
-
Source: Dassault Systemes ( Mr. Nerijus Jankevicius)
-
Summary:
UML spec, Figure 15.3 shows that multiplicity of redefining state is 0..1 which automatically means that it is impossible to have two or more subclasses which redefine the same state in their statemachines.
It should be fixed to state [0..*] I believe
-
Reported: UML 2.5b1 — Thu, 14 Feb 2013 05:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
Change the appropriate association end multiplicities from [0..1] to [0..*].
-
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — wrong multiplicity of redefining states
- Key: UML25-497
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF