-
Key: UML22-70
-
Legacy Issue Number: 8274
-
Status: closed
-
Source: Adaptive ( Mr. Pete Rivett)
-
Summary:
11.6.2 of Infra and 7.3.16 of Super refer to the possibility of Enumerations having attributes: "A compartment listing the attributes for the enumeration is placed
below the name compartment." This concept does not make sense to me: an enumeration inherently represents a single value-set modeled through owned EnumerationLiterals.
The only type of attribute that might ever make sense is a derived attribute (e.g. Color.isPrimary).Proposed resolution:
Add constraint to above sections on Enumeration to state that only attributes permitted are derived ones. Also that any Operation must have isQuery=true. -
Reported: UML 1.4.2 — Mon, 14 Feb 2005 05:00 GMT
-
Disposition: Resolved — UML 2.2
-
Disposition Summary:
Enumeration literals are immutable, so writeable attributes do not make sense. But read-only attributes do
make sense: they don’t need to be derived. The current description of equality of EnumerationLiterals needs
improvement. Operations on enumerations are allowed.
This also resolves 17933 -
Updated: Fri, 6 Mar 2015 20:58 GMT
UML22 — UML2/Infra section 11.6.2/ Enumerations should not have attributes
- Key: UML22-70
- OMG Task Force: UML 2.2 RTF