-
Key: UML14-36
-
Legacy Issue Number: 3127
-
Status: closed
-
Source: Google ( Don Baisley)
-
Summary:
All data types used in the UML metamodels are clumped together in a
Data_Types package in the Foundation metamodel. When a new type is needed
by some other metamodel, such as for Activity Graphs, the type is added into
Foundation. This breaks the whole concept of extensibility. Data types,
like other model elements, should be defined in the specific packages where
they are needed. A new package that requires new types should include those
types itself and not impose a change on UML Foundation.Recommendation: In the "physical" metamodel, put data types into the
packages where they are first used. For example, PseudostateKind should be
defined in Behavioral_Elements.State_Machines, not in Foundation.Data_Types. -
Reported: XMI 1.1 — Wed, 15 Dec 1999 05:00 GMT
-
Disposition: Resolved — UML 1.4.2
-
Disposition Summary:
No Data Available
-
Updated: Fri, 6 Mar 2015 20:58 GMT
UML14 — Data Types Misplaced in the "Physical" Metamodel (uml-rtf)
- Key: UML14-36
- OMG Task Force: UML 1.4 RTF