Differences between versions of UML diagrams
Proceedings of the 9th European software engineering conference held jointly with 11th ACM SIGSOFT international symposium on Foundations of software engineering
The epsilon object language (EOL)
ECMDA-FA'06 Proceedings of the Second European conference on Model Driven Architecture: foundations and Applications
Managing Model Conflicts in Distributed Development
MoDELS '08 Proceedings of the 11th international conference on Model Driven Engineering Languages and Systems
Think global, act local: implementing model management with domain-specific integration languages
MoDELS'06 Proceedings of the 2006 international conference on Models in software engineering
An algebraic view on the semantics of model composition
ECMDA-FA'07 Proceedings of the 3rd European conference on Model driven architecture-foundations and applications
A formal approach to three-way merging of EMF models
Proceedings of the 1st International Workshop on Model Comparison in Practice
Issues in model-driven behavioural product derivation
Proceedings of the 5th Workshop on Variability Modeling of Software-Intensive Systems
A manifesto for semantic model differencing
MODELS'10 Proceedings of the 2010 international conference on Models in software engineering
ADDiff: semantic differencing for activity diagrams
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
CDDiff: semantic differencing for class diagrams
Proceedings of the 25th European conference on Object-oriented programming
Journal of Systems and Software
Hi-index | 0.00 |
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.