The scent of a smell: an extensive comparison between textual and structural smells
Abstract
Code smells, i.e., symptoms of poor design and implementation choices applied by programmers during the development of a software project [2], represent an important factor contributing to technical debt [3]. The research community spent a lot of effort studying the extent to which code smells tend to remain in a software project for long periods of time [9], as well as their negative impact on non-functional properties of source code [4, 7]. As a consequence, several tools and techniques have been proposed to help developers in detecting code smells and to suggest refactoring opportunities (e.g., [5, 6, 8]).
BibTeX
@inproceedings{Palomba-al:ICSE18,
author = {Fabio Palomba and
Annibale Panichella and
Andy Zaidman and
Rocco Oliveto and
Andrea De Lucia},
title = {The scent of a smell: an extensive comparison between textual and structural smells},
booktitle = {ICSE},
pages = {740},
publisher = {{ACM}},
year = {2018},
}