Preserving aspects via automation: a maintainability study

Start Page
315
End Page
324
Article Number
6092580
Citation
International Symposium on Empirical Software Engineering and Measurement: 6092580. 315-324 (2011-12)
Contribution to Conference
5th International Symposium on Empirical Software Engineering and Measurement, ESEM 2011  
Publisher DOI
10.1109/esem.2011.40
Scopus ID
2-s2.0-84858716292
Publisher
IEEE
This paper presents an empirical study comparing two alternatives for generating code from aspect-oriented models. In an aspect "disrupting" process, an object oriented implementation in Java is automatically generated from domain specific models, comprising a mix of UML (for core functionality) and DSLs (for qualities like security and performance). In an aspect "preserving" process, an aspect oriented implementation in AspectJ is automatically generated from the same models. In both alternatives, a number of subjects are asked to perform several maintenance tasks requiring the addition and improvement of functionality. The results show that, in most of the cases, the AO alternative provides for shorter maintenance cycles.
Subjects
Domain specific modeling
Experimental study
Model driven engineering
DDC Class
004: Informatik