2008 12th International IEEE Enterprise Distributed Object Computing Conference 2008
DOI: 10.1109/edoc.2008.44
|View full text |Cite
|
Sign up to set email alerts
|

Automating Co-evolution in Model-Driven Engineering

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
156
0
1

Year Published

2009
2009
2022
2022

Publication Types

Select...
7
1

Relationship

0
8

Authors

Journals

citations
Cited by 193 publications
(162 citation statements)
references
References 5 publications
0
156
0
1
Order By: Relevance
“…Our work differentiates from these in being the only one to investigate the automatic synchronization between refinement transformations of application and test cases. Similar problems to our framework are addressed in the field of model and transformation co-evolution, for instance in [18], [26] and [11]. While some of the design issues are shared with these works, our proposal addresses the peculiar relationship between the model of an artifact and the model of a test case.…”
Section: Related Workmentioning
confidence: 98%
“…Our work differentiates from these in being the only one to investigate the automatic synchronization between refinement transformations of application and test cases. Similar problems to our framework are addressed in the field of model and transformation co-evolution, for instance in [18], [26] and [11]. While some of the design issues are shared with these works, our proposal addresses the peculiar relationship between the model of an artifact and the model of a test case.…”
Section: Related Workmentioning
confidence: 98%
“…Finally, our meta-model refactorings and subsequent propagation to the model fragments can be seen as a simplified scenario of meta-model/model evolution [5].…”
Section: Related Workmentioning
confidence: 99%
“…However, the resolution of an open issue by means of a refactoring may break the conformance. According to [5], changes in meta-models can be classified into non-breaking, breaking and resolvable, and breaking and unresolvable. Our refactorings automatically update the fragments if a change is non-breaking or resolvable.…”
Section: Interactivity and Exploration By Supervising Decisionsmentioning
confidence: 99%
“…These approaches then reuse the logs of applied transactions to derive adaptation transformations. Cicchetti et al [16] use difference models provided by external tools.…”
Section: Related Workmentioning
confidence: 99%
“…The works described in [14][15] [16][17] [18] assume traces of changes are available, and derive adaptation transformations from them. In particular, [14], [18], and [17] apply stepwise automatic transactions on MM1 to obtain MM2.…”
Section: Related Workmentioning
confidence: 99%