2009
DOI: 10.1007/978-3-642-02655-3_8
|View full text |Cite
|
Sign up to set email alerts
|

Round-Trip Support for Invasive Software Composition Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2010
2010
2019
2019

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(2 citation statements)
references
References 9 publications
0
2
0
Order By: Relevance
“…Note that we do not consider AOM approaches that support full code generation (e.g., [10,37]), as these are not considered to be representative for AOM [16]. We also do not take into account MDE approaches that allow immediate code modifications by automatically reflecting those changes at the model level (e.g., [26,41]), as the support for round trip engineering in AOM is currently very limited.…”
Section: Introductionmentioning
confidence: 99%
“…Note that we do not consider AOM approaches that support full code generation (e.g., [10,37]), as these are not considered to be representative for AOM [16]. We also do not take into account MDE approaches that allow immediate code modifications by automatically reflecting those changes at the model level (e.g., [26,41]), as the support for round trip engineering in AOM is currently very limited.…”
Section: Introductionmentioning
confidence: 99%
“…Finally, in [37] authors define composition interface for model fragments as a set of ports representing reference and variation points of a language. Reference points are root nodes for model fragments, where variation points are nodes that may be replaced during composition.…”
Section: Related Workmentioning
confidence: 99%