From aspect-oriented models to aspect-oriented code? The maintenance perspective

Start Page
85
End Page
96
Citation
Proceedings of the 9th International Conference on Aspect-Oriented Software Development: 85-96 (2010-05-19)
Contribution to Conference
9th International Conference on Aspect-Oriented Software Development, AOSD 2010  
Publisher DOI
10.1145/1739230.1739241
Scopus ID
2-s2.0-77952258102
Publisher
ACM
Aspect-Oriented Modeling (AOM) provides support for separating concerns at the design level. Even though most AOM approaches provide means to execute the composition of the modularized concerns to obtain a composed model, it is also possible to keep the concerns modularized at the implementation level by targeting an aspect-oriented platform. Model-driven approaches have emerged to support both alternatives via tools. Clearly, these choices are not equivalent. Rather, they have a direct impact on several dimensions, including maintainability. Hence, the main research problem addressed by this work is to figure out which alternative provides for shorter maintenance time. To answer this question, we have conducted a series of quantitative studies and experiments.
Subjects
Aspect-oriented modeling
Aspect-oriented programming
Empirical study
Model composition
Model-driven engineering
DDC Class
004: Informatik