Issue 8458: UML 2 Super / General / missing merges (uml2-rtf) Source: International Business Machines (Mr. Jim Amsden, jamsden(at)us.ibm.com) Nature: Uncategorized Issue Severity: Summary: Compliance level L3 references, but does not merge: Superstructure::Logical View::UML::CommonBehaviors Superstructure::Logical View::UML::CompositeStructures There are a number of diagrams in the UML2 Rose model that contain unlabeled dependencies between packages. In particular, Activities, Interactions, StateMachines, and UseCases have dependencies to CommonBehaviors that are unlabeled. See diagram UML/Behavior Packages and UML/UML Top-Level Packages. Since CommonBehaviors does not contain any classes, it does not necessarily need to be merged into any compliance level. Instead, the packages it contains are merged as needed. Recommendation: Remove all unlabeled dependencies between packages, or mark them as either package imports or package merges as needed. Resolution: see above Revised Text: Mark all unlabeled dependencies between packages as package imports in the UML2 metamodel and in figures: Figure 7 Figure 123 Figure 140 Figure 353 Figure 411 Figure 445 Editor’s note: added figure 11.11 Actions taken: March 4, 2005: received issue August 23, 2006: closed issue Discussion: Since CommonBehaviors does not directly contain any classes, it does not necessarily need to be merged into any compliance level. Instead, the packages it contains are merged as needed. The package imports are ok because the are merged away in the compliance levels. UML2 models are CMOF models, and CMOF does not support dependencies. So all unlabeled dependencies in the UML2 metamodel should be either package imports or merges. End of Annotations:===== ssue X3: UML 2 Super / General / missing merges Source: Jim Amsden, IBM Software Summary: Compliance level L3 references, but does not merge: Superstructure::Logical View::UML::CommonBehaviors Superstructure::Logical View::UML::CompositeStructures There are a number of diagrams in the UML2 Rose model that contain unlabeled dependencies between packages. In particular, Activities, Interactions, StateMachines, and UseCases have dependencies to CommonBehaviors that are unlabeled. See diagram UML/Behavior Packages and UML/UML Top-Level Packages. Since CommonBehaviors does not contain any classes, it does not necessarily need to be merged into any compliance level. Instead, the packages it contains are merged as needed. Recommendation: Remove all unlabeled dependencies between packages, or mark them as either package imports or package merges as needed.