Bad-Smell Metrics for Aspect-Oriented Software

Abstract

Aspect-Oriented Programming (AOP) is a newprogramming paradigm that improves separation of concerns by decomposing the crosscutting concerns in aspect modules. Bad smells are metaphors to describe software patterns that are generally associated with bad design and bad programming of Object-Oriented Programming (OOP). New notions and different ways of thinking for developing Aspect-Oriented (AO) software inevitably introduce bad smells which are specific bad design and bad programming in AO software called AO bad smells. Software metrics have been used to measure software artifact for a better understanding of its attributes and to assess its quality. Bad-smell metrics should be used as indicators for determining whether a particular fraction of AO code contains bad smells or not. Therefore, this paper proposes definition of metrics corresponding to the characteristic of each AO bad smell as a means to detecting them. The proposed bad-smell metrics are validated and the results show that the proposed badsmell metrics can preliminarily indicate bad smells hidden in AO software.

An exploratory study of code smells in evolving aspect-oriented systems

“…This paper presents a first exploratory analysis of code smells in evolving aspect-oriented systems. Our analysis also revealed a new suite of six code smells (Section 3.2), which complement previously-documented ones [26] [32]. Our investigation focused on 18 releases of 3 heterogeneous applications (Section 2.2): a Web-based system, an open-source framework for data mapping, and a product line for mobile media management.…”

“…Our key findings suggest that smells previously identified in aspect-oriented code did not occur as often as claimed or expected [26] [32]. Our analysis also indicated that certain smells, which were not reported elsewhere, might occur more often than those well-known smells [26] [32].…”

“…Therefore, the documentation of what and how AOP smells occur are of paramount importance. Even though catalogs for AOP smells are beginning to appear [26] [32], there is no systematic investigation on whether and how often these anomalies can manifest in longliving software systems. There is also little knowledge about their harmful impact on software maintenance, such as the need for further refactorings or corrective changes.…”

“…In fact, the expressive power of AOP mechanisms might facilitate the introduction of certain code smells (or anomalies) [6][26] [32]. A code smell is any symptom in the source code that possibly indicates a deeper maintainability problem [6].…”

Pemetaan Secara Sistematis Pada Metrik Kualitas Perangkat Lunak

“…Validasi Makalah Internal Validity (Pai & Dugan, 2007) (Selvarani, dkk., 2009) (Yahaya, dkk., 2010) (Ma, dkk., 2009) (Nagappan & Ball, 2007) (Marcus & Poshyvanyk, 2005) (Steidl, dkk., 2013) (Costal & Franch, 2012) (Shim, dkk., 2008) (Oyetoyan, dkk., 2013) (Zhou & Liu, 2007) (Hansen, dkk., 2011) (Al Dallal & Briand, 2010 (Thwin & Quah, 2005) (Al Dallal, 2012) (Al Dallal, 2011) (Stefani & Xenos, 2009) (Ahn, dkk., 2013) (Hulse & Khoshgoftaar, 2008) Eksternal Validity (Kulkarni, dkk., 2010) (Srivisut & Muenchaisri, 2007) (Chaparro, dkk., 2014) (Khaer, dkk., 2008) (Chirila & Cret¸u, 2011) (Damm & Lundberg, 2007) (Pai & Dugan, 2007) …”