Last updated on Monday, October 06, 2025
@inproceedings{Hovsepyan2011ESEM,
author = {Hovsepyan, Aram and Scandariato, Riccardo and
Van Baelen, Stefan and Joosen, Wouter and
Demeyer, S.},
booktitle = {Proceedings {ESEM}'2011 (International Symposium on
Empirical Software Engineering)},
month = sep,
note = {Acceptance ratio: 33/103 = 32\%},
pages = {315 -324},
title = {Preserving aspects via automation: a maintainability
study},
year = {2011},
abstract = {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 perfor mance). 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.},
annote = {internationalconference},
top = {A in CORE2013},
doi = {10.1109/ESEM.2011.40},
issn = {1938-6451},
url = {https://lirias.kuleuven.be/handle/123456789/311545},
}