-
Key: UML22-181
-
Legacy Issue Number: 9245
-
Status: closed
-
Source: Capgemini ( Anneke Kleppe)
-
Summary:
The infrastructure specification [1] described the metaclass Element as followes:
“Element is an abstract metaclass with no superclass. It is used as the common superclass for all
metaclasses in the infrastructure library.” [1, page 45 and page 93]
Both packages, Abstraction and Basic, are using the same definition for Element. Therefore, it is logical to
assume that both packages will contain their own class Element, as shown in Figure 2.
InfrastructureLibrary
Abstractions Basic
Element Element
Figure 2
The Rose Model [2] specifies one single class Element, a metaclass that is part of Abstractions. The exact
name is Abstractions::Elements::Element. The Basic package imports this metaclass. (see Figure 3). We
assume this is the correct interpretation, therefore the text on page 93 should be changed accordingly.
InfrastructureLibrary
Basic
Abstractions
Element
(from Elements)
<<import>>
Figure 3 -
Reported: UML 2.0 — Wed, 18 Jan 2006 05:00 GMT
-
Disposition: Resolved — UML 2.2
-
Disposition Summary:
Discussion
This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
Disposition: Closed - No Change -
Updated: Fri, 6 Mar 2015 20:58 GMT