Model-Driven Software Development: Technology, Engineering, Management
Model-Driven Software Development: Technology, Engineering, Management
The Objects and Arrows of Computational Design
MoDELS '08 Proceedings of the 11th international conference on Model Driven Engineering Languages and Systems
Services to the Field: An Approach for Resource Constrained Sensor/Actor Networks
WAINA '09 Proceedings of the 2009 International Conference on Advanced Information Networking and Applications Workshops
COPE - Automating Coupled Evolution of Metamodels and Models
Genoa Proceedings of the 23rd European Conference on ECOOP 2009 --- Object-Oriented Programming
A Taxonomy of Model Transformation
Electronic Notes in Theoretical Computer Science (ENTCS)
GPCE '10 Proceedings of the ninth international conference on Generative programming and component engineering
Model migration with epsilon flock
ICMT'10 Proceedings of the Third international conference on Theory and practice of model transformations
Delta-oriented programming of software product lines
SPLC'10 Proceedings of the 14th international conference on Software product lines: going beyond
MoDELS'05 Proceedings of the 2005 international conference on Satellite Events at the MoDELS
Metamodel adaptation and model co-adaptation
ECOOP'07 Proceedings of the 21st European conference on Object-Oriented Programming
| Hi-index | 0.00 |
The model-driven architecture proposes stepwise model refinement. The resulting model-to-model (M2M) transformation chains can consist of many steps. For realizing the transformations two approaches exist: Exogenous transformations, where input and output use different metamodels, and endogenous transformations, that use the same metamodel for input and output. Due to the particularities of embedded systems, using only endogenous transformations is not appropriate. For exogenous transformations, problems arise with respect to creation and maintenance of the subsequent metamodels. Another problem of these M2M transformation chains is that for one transformation step typically large parts of the model data remain unchanged. The resulting M2M transformation does often include many copy operations that distract the developers from the "real" transformations and increase implementation overhead. This paper introduces a generic approach that solves these issues by a (semi-) automatic metamodel construction and copy operation of unchanged model data between subsequent steps.