Authors:
Josh G. M. Mengerink
1
;
Bram van der Sanden
1
;
Bram C. M. Cappers
1
;
Alexander Serebrenik
1
;
Ramon R. H. Schiffelers
2
and
Mark G. J. van den Brand
1
Affiliations:
1
Eindhoven University of Technology, Netherlands
;
2
Eindhoven University of Technology and ASML, Netherlands
Keyword(s):
Model Driven Engineering, Evolution, Maintenance.
Related
Ontology
Subjects/Areas/Topics:
Domain-Specific Modeling and Domain-Specific Languages
;
Languages, Tools and Architectures
;
Model Transformation
;
Model-Driven Software Development
;
Models
;
Paradigm Trends
;
Software Engineering
;
Syntax and Semantics of Modeling Languages
Abstract:
Model-driven engineering is used in the design of systems to (a.o.) enable analysis early in the design process.
For instance, by using domain-specific languages, enabling engineers to model systems in terms of their
domain, rather then encoding them into general purpose modeling languages. Domain-specific languages,
like classical software, evolve over time. When domain languages evolve, they may trigger co-evolution of
models, model-to-model transformations, editors (both graphical and textual), and other artifacts that depend
on the domain-specific language. This co-evolution can be tedious and very costly.
In literature, various approaches are proposed towards automated co-evolution. However, these approaches do
not reach full automation. Several other studies have shown that there are theoretical limitations to the level
of automation that can be achieved in certain scenarios. For several scenarios full automation can never be
achieved. We wish to gain insight to which
extent practically occurring scenarios can be automated.
To gain this insight, in this paper, we investigate on a large-scale industrial repository, which (co-)evolutionary
scenarios occur in practice, and compare them with the various scenarios and their theoretical automatability.
We then assess whether practically occurring scenarios can be fully automated.
(More)