The browser you are using is not supported by this website. All versions of Internet Explorer are no longer supported, either by us or Microsoft (read more here: https://www.microsoft.com/en-us/microsoft-365/windows/end-of-ie-support).

Please use a modern browser to fully experience our website, such as the newest versions of Edge, Chrome, Firefox or Safari etc.

Requirements for Practical Model Merge - An Industrial Perspective

Author

Summary, in English

All the support tools that developers are used to must be in place, if the use of model-centric development in companies hits to take off. Industry deals with big models and many people working on the same model. Collaboration in a team inevitably leads to parallel work creating different versions that eventually will have to be merged together. However, our experience is that at present the support for model merge is far from optimal. In this paper, we put forward a number of requirements for practical merge tools, based on our analysis of literature, merge tool evaluations, interviews with developers, and a number of use cases for concurrent development of models. We found future work to do for both tool vendors and academic research. Fortunately we also uncovered a few tips and tricks that companies using model-centric development can implement on the short term while waiting for better times.

Publishing year

2009

Language

English

Pages

167-180

Publication/Series

Model Driven Engineering Languages And Systems, Proceedings

Volume

5795

Document type

Conference paper

Publisher

Springer

Topic

  • Computer Science

Keywords

  • team coordination
  • parallel work
  • version control
  • Model merge
  • diff
  • industrial experience

Conference name

12th International Conference on Model Driven Engineering Languages and Systems

Conference date

2009-10-04 - 2009-10-09

Conference place

Denver, CO, United States

Status

Published

ISBN/ISSN/Other

  • ISSN: 1611-3349
  • ISSN: 0302-9743