2006
DOI: 10.1109/mc.2006.45
|View full text |Cite
|
Sign up to set email alerts
|

Automating Change Evolution in Model-Driven Engineering

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
33
0

Year Published

2006
2006
2013
2013

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 49 publications
(33 citation statements)
references
References 8 publications
0
33
0
Order By: Relevance
“…To this end, in (Gray et al, 2006) the authors developed meta-transformations as transformations which produce transformations. However, unlike this proposal, in our approach the new transformations are created to get adaptability in the architectural models (horizontal transformations) rather than make the transformation from PIM to PSM models (vertical transformations).…”
Section: Related Workmentioning
confidence: 99%
“…To this end, in (Gray et al, 2006) the authors developed meta-transformations as transformations which produce transformations. However, unlike this proposal, in our approach the new transformations are created to get adaptability in the architectural models (horizontal transformations) rather than make the transformation from PIM to PSM models (vertical transformations).…”
Section: Related Workmentioning
confidence: 99%
“…Many researchers have proposed support environments to help explore the increasingly complex models that engineers are developing. Gray et al [26] have developed the Constraint-Specification Aspect Weaver (C-Saw), which uses aspect-oriented approaches [24] to help engineers in the process of model transformation. Cai and Sullivan [9] describe a formal method and tool called Simon that "supports interactive construction of formal models, derives and displays design structure matrices... and supports simple design impact analysis."…”
Section: Requirements Analysis Toolsmentioning
confidence: 99%
“…One of the challenges faced in MDE is the escalating complexity of software and system models [13]. For large-scale software development, the sheer size of models, the intertwining relationships between intra-and inter-model elements, and the concerns expressed across different models present a high adoption barrier to MDE practice.…”
Section: Introductionmentioning
confidence: 99%
“…Aspect-oriented software development (AOSD) provides explicit means to model concerns that crosscut multiple system components. It is argued that the synthesis of MDE and AOSD can not only provide effective support for managing software complexity, but also improve model quality and productivity [13].…”
Section: Introductionmentioning
confidence: 99%