Proceedings of the 2014 IEEE 15th International Conference on Information Reuse and Integration (IEEE IRI 2014) 2014
DOI: 10.1109/iri.2014.7051941
|View full text |Cite
|
Sign up to set email alerts
|

A mapping study on architecture-driven modernization

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2014
2014
2020
2020

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 6 publications
(3 citation statements)
references
References 27 publications
0
3
0
Order By: Relevance
“…Several approaches relying on this technique have been published recently, e.g. [17][18][19]. All of the mentioned approaches differ from the approach presented in this paper inasmuch as they do not support incremental round-trip engineering between models and code.…”
Section: Related Workmentioning
confidence: 99%
“…Several approaches relying on this technique have been published recently, e.g. [17][18][19]. All of the mentioned approaches differ from the approach presented in this paper inasmuch as they do not support incremental round-trip engineering between models and code.…”
Section: Related Workmentioning
confidence: 99%
“…The idea behind KDM is to motivate the community to start creating parsers and tools that work over KDM instances; thus, every tool that takes KDM as input can be considered platform and languageindependent. For instance, a refactoring catalogue for KDM can be used for refactoring systems implemented in different languages [32]. One of the primary uses of KDM is during reverse engineering processes, in that a parser reads sourcecode of a system and generates a KDM instance representing it.…”
Section: Introductionmentioning
confidence: 99%
“…Whenever one decides to modernize legacy systems aiming to remodularize concerns, a candidate paradigm is Aspect-Orientation (AO), which provides abstractions to improve the modularization of crosscutting concerns [29]. Although ADM/KDM had been created to support modernization of legacy systems, the original version of the KDM does not contains metaclasses suitable for representing AOP concepts [32]; hampering modernization processes whose goal is to remodularize crosscutting concerns [3].…”
Section: Introductionmentioning
confidence: 99%