Package Merge in UML 2: Practice vs. Theory?

  • Alanna Zito
  • Zinovy Diskin
  • Juergen Dingel
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4199)

Abstract

The notion of compliance is meant to facilitate tool interoperability. UML 2 offers 4 compliance levels. Level Li + 1 is obtained from Level Li through an operation called package merge. Package merge is intended to allow modeling concepts defined at one level to be extended with new features. To ensure interoperability, package merge has to ensure compatibility: the XMI representation of the result of the merge has to be compatible with that of the original package. UML 2 lacks a precise and comprehensive definition of package merge. This paper reports on our work to understand and formalize package merge. Its main result is that package merge as defined in UML 2.1 does not ensure compatibility. To expose the problem and possible remedies more clearly, we present this result in terms of a very general classification of model extension mechanisms.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Alanna Zito
    • 1
  • Zinovy Diskin
    • 1
  • Juergen Dingel
    • 1
  1. 1.School of ComputingQueen’s UniversityKingstonCanada

Personalised recommendations