-
Key: UML25-342
-
Legacy Issue Number: 17924
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
Even though an operation it has the same # of parameters and the type is the same, does not really make the types match.
For example, changing effect or unique--> nonUnique would change the “effective” type though not in a way that UML recognizes -
Reported: UML 2.4.1 — Wed, 26 Sep 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
Merged with 15499
-
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Location p 157 isConsistentWith: missing rules
- Key: UML25-342
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF