A Case Study Implementing Features Using AspectJ
Christian Kästner, Sven Apel, Don S. Batory · International Software Product Line Conference (SPLC) · 2007
Software product lines aim to create highly configurable programs from a set of features. Common belief and recent studies suggest that aspects are well-suited for implementing features. We evaluate the suitability of AspectJ with respect to this task by a case study that refactors the embedded database system Berkeley DB into 38 features. Contrary to our initial expectations, the results were not encouraging. As the number of aspects in a feature grows, there is a noticeable decrease in code readability and maintainability. Most of the unique and powerful features of AspectJ were not needed. We document where AspectJ is unsuitable for implementing features of refactored legacy applications and explain why.
Cited by 168 works. doi:10.1109/spline.2007.12
Authors
References
- Refactoring: Improving the Design of Existing Code
- Aspect-oriented programming
- Feature Models, Grammars, and Propositional Formulas
- Scaling step-wise refinement
- Aspectj in Action: Practical Aspect-Oriented Programming
- Subject-oriented programming
- Feature-oriented programming: A fresh look at objects
- Virtual classes: a powerful mechanism in object-oriented programming
- Arranging language features for more robust pattern-based crosscuts
- Open Modules: Modular Reasoning About Advice