Advertisement

Using a Model Merging Language for Reconciling Model Versions

  • Klaus-D. Engel
  • Richard F. Paige
  • Dimitrios S. Kolovos
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4066)

Abstract

A difficult challenge in the industrialisation of Model-Driven Development is managing different versions of models. Different versions may arise at any time during the development process, due to different individuals or teams working on different parts of the overall model. To manage these versions it is necessary to be able to identify differences and reconcile these differences in a single, integrated model. We describe the use of model merging technology for managing different versions of a model in an industrial software development process. The use of automated model merging technology is contrasted with an alternative, semi-automated approach. The contributions of model merging to helping to solve this problem are outlined.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Object Management Group. Meta Object Facility official web-site. Internet resource, http://www.omg.org/mof/
  2. 2.
    Object Management Group. Model Driven Architecture official web-site. Internet resource, http://www.omg.org/mda/
  3. 3.
    Object Management Group. XMI specification. Internet resource, http://www.omg.org/technology/documents/formal/xmi.htm
  4. 4.
    Modelware IST Project. Internet resource, http://www.modelware-ist.org
  5. 5.
    Kolovos, D., Paige, R.F., Polack, F.A.C.: The Epsilon Object Language (EOL). In: Proc. EC-MDA 2006. LNCS. Springer, Heidelberg (2006)Google Scholar
  6. 6.
    Atlas Model Management Architecture (last accessed, February 2006), Available at: http://www.sciences.univ-nantes.fr/lina/atl/AMMAROOT/
  7. 7.
    Epsilon Model Management Platform (last accessed, February 2006), Available at: http://www.cs.york.ac.uk/~dkolovos/epsilon
  8. 8.
    Enterprise Architect (last accessed, January 2006), http://www.sparksystems.com.au
  9. 9.
    Ohst, D., Welle, M., Kelter, U.: Differences between Versions of UML Diagrams. In: 9th European Software Engineering Conference, pp. 227–236. ACM Press, New York (2003)Google Scholar
  10. 10.
    Lin, Y., Zhang, J., Gray, J.: Model Comparison: A Key Challenge for Transformation Testing and Version Control in Model Driven Software Development. In: OOPSLA Workshop on Best Practices for Model-Driven Software Development (2004)Google Scholar
  11. 11.
    Alanen, M., Porres, I.: Version Control of Software Models. In: Advances in UML and XML-Based Software Evolution. Idea Group Publishing (2005)Google Scholar
  12. 12.
    Alanen, M., Porres, I.: Difference and Union of Models. In: Stevens, P., Whittle, J., Booch, G. (eds.) UML 2003. LNCS, vol. 2863, pp. 2–17. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  13. 13.
    Kath, O.: The AMEDATO Solution - A Success Story For Model Driven Technologies. Burlingame, CA, U.S.A., December 5-9, 2005 (2005) (AMEDATO Presentation: mda-user/05-12-01) Google Scholar
  14. 14.
    Revision Control Wikipedia Entry (last accessed, February 2006), http://en.wikipedia.org/wiki/Revision_control
  15. 15.
    Kolovos, D.S., Paige, R.F., Polack, F.A.C.: On-Demand Merging of Traceability Links with Models (submitted, April 2006), http://www.cs.york.ac.uk/~dkolovos

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Klaus-D. Engel
    • 1
  • Richard F. Paige
    • 2
  • Dimitrios S. Kolovos
    • 2
  1. 1.Fraunhofer FOKUS 
  2. 2.Department of Computer ScienceUniversity of YorkUK

Personalised recommendations