On the Impact of Aspect-Oriented Code Smells on Architecture Modularity: An Exploratory Study

Aspect-oriented programming (AOP) aims to improve software modularity, although developers can unwittingly introduce code smells in their programs. A code smell is any symptom in the source code that possibly indicates a deeper modularity problem. Several works have been concerned about code smell o...

Full description

Saved in:
Bibliographic Details
Main Authors: Macia, I., Garcia, A., von Staa, A., Garcia, J., Medvidovic, N.
Format: Conference Proceeding
Language:English
Subjects:
architectural smells
aspect-oriented programming
code smells
Computer architecture
Concurrent computing
Connectors
Correlation
Programming
Reliability
Software
Online Access:Request full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Aspect-oriented programming (AOP) aims to improve software modularity, although developers can unwittingly introduce code smells in their programs. A code smell is any symptom in the source code that possibly indicates a deeper modularity problem. Several works have been concerned about code smell occurrences in aspect-oriented systems. However, there is little knowledge about their actual damage to the modularity of architectural designs. This gap makes it difficult for developers understand and manage the harmful architecture-level impact of recurring code smells. This paper presents an exploratory analysis that investigates the influence of aspect-oriented code smells on evolving architectural designs. We analyzed code smell occurrences in 14 versions of 2 applications designed using different architectural styles. The outcome of our evaluation suggests that code smell occurrences often entail architecture modularity problems in these systems. Even worse, our analysis revealed that certain architecturally-relevant code smells were not targeted by the refactoring strategies in place.
DOI:10.1109/SBCARS.2011.18