Evolution control in MDE projects: Controlling model and code co-evolution

3Citations
Citations of this article
11Readers
Mendeley users who have this article in their library.
Get full text

Abstract

The dream of Model Driven Engineering (MDE) is that Software Engineering activities should be performed only on models, but in practice a significant amount of programming is still being performed. There is a clear need to keep code and models strongly synchronized when they represent the same entities at different levels of abstraction. We observe that versioning is ill supported by MDE tools, and that no strong synchronization is ensured between code and model versions. This, among other things, explains why MDE is not widely adopted in industry. This paper presents the solution developed in the CADSE project for providing consistent support for model and code co-evolution. It is shown that it requires to (1) define, what evolution policy is to be applied, (2) closely synchronize both ways, the model entities and the computer artifacts, and (3) enforce consistency constraints and evolution policies during the commit and check-out of both model elements and their corresponding artifacts. © 2010 Springer.

Cite

CITATION STYLE

APA

Estublier, J., Leveque, T., & Vega, G. (2010). Evolution control in MDE projects: Controlling model and code co-evolution. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 5961 LNCS, pp. 431–438). https://doi.org/10.1007/978-3-642-11623-0_26

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free