Fabio Palomba
Auto-generated profile, based on publicly available information

Fabio Palomba

University of Salerno

Research Focus & Metrics

Academic Career Length

15Years (2012-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
1 April 2019 in Information and Software Technology
Verified
Journal Article
Closed access
MAMuhammad Ilyas Azeem
Muhammad Ilyas Azeem
FPFabio Palomba
Fabio Palomba
LSLin Shi
Lin Shi
QWQing Wang
Qing Wang

7 August 2017 in Empirical Software Engineering
Verified
Journal Article
Open access
PDF file
FPFabio Palomba
Fabio Palomba
GBGabriele Bavota
Gabriele Bavota
MPMassimiliano Di Penta
Massimiliano Di Penta
FFFausto Fasano
Fausto Fasano
RORocco Oliveto
Rocco Oliveto
ALAndrea De Lucia
Andrea De Lucia
Code smells are symptoms of poor design and implementation choices that may hinder code comprehensibility and maintainability. Despite the effort devoted by the research community in studying code smells, the extent to which code smells in software systems affect software maintainability remains still unclear. In this paper we present a large scale empirical investigation on the diffuseness of code smells and their impact on code change- and fault-proneness. The study was conducted across a total of 395 releases of 30 open source projects and considering 17,350 manually validated instances of 13 different code smell kinds. The results show that smells characterized by long and/or complex code (e.g., Complex Class) are highly diffused, and that smelly classes have a higher change- and fault-proneness than smell-free classes.

20 November 2014 in IEEE Transactions on Software Engineering
Verified
Journal Article
Open access
FPFabio Palomba
Fabio Palomba
GBGabriele Bavota
Gabriele Bavota
MPMassimiliano Di Penta
Massimiliano Di Penta
RORocco Oliveto
Rocco Oliveto
DPDenys Poshyvanyk
Denys Poshyvanyk
ALAndrea De Lucia
Andrea De Lucia
Code smells are symptoms of poor design and implementation choices that may hinder code comprehension, and possibly increase changeand fault-proneness. While most of the detection techniques just rely on structural information, many code smells are intrinsically characterized by how code elements change overtime. In this paper, we propose Historical Information for Smell deTection (HIST), an approach exploiting change history information to detect instances of five different code smells, namely Divergent Change, Shotgun Surgery, Parallel Inheritance, Blob, and Feature Envy. We evaluate HIST in two empirical studies. The first, conducted on 20 open source projects, aimed at assessing the accuracy of HIST in detecting instances of the code smells mentioned above. The results indicate that the precision of HIST ranges between 72 and 86 percent, and its recall ranges between 58 and 100 percent. Also, results of the first study indicate that HIST is able to identify code smells that cannot be identified by competitive approaches solely based on code analysis of a single system's snapshot. Then, we conducted a second study aimed at investigating to what extent the code smells detected by HIST (and by competitive code analysis techniques) reflect developers' perception of poor design and implementation choices. We involved 12 developers of four open source projects that recognized more than 75 percent of the code smell instances identified by HIST as actual design/implementation problems.

16 January 2017 in IEEE Transactions on Software Engineering
Verified
Journal Article
Open access
MTMichele Tufano
Michele Tufano
FPFabio Palomba
Fabio Palomba
GBGabriele Bavota
Gabriele Bavota
RORocco Oliveto
Rocco Oliveto
MPMassimiliano Di Penta
Massimiliano Di Penta
DPDenys Poshyvanyk
Denys Poshyvanyk
Technical debt is a metaphor introduced by Cunningham to indicate “not quite right code which we postpone making it right”. One noticeable symptom of technical debt is represented by code smells, defined as symptoms of poor design and implementation choices. Previous studies showed the negative impact of code smells on the comprehensibility and maintainability of code. While the repercussions of smells on code quality have been empirically assessed, there is still only anecdotal evidence on when and why bad smells are introduced, what is their survivability, and how they are removed by developers. To empirically corroborate such anecdotal evidence, we conducted a large empirical study over the change history of 200 open source projects. This study required the development of a strategy to identify smell-introducing commits, the mining of over half a million of commits, and the manual analysis and classification of over 10K of them. Our findings mostly contradict common wisdom, showing that most of the smell instances are introduced when an artifact is created and not as a result of its evolution. At the same time, 80 percent of smells survive in the system. Also, among the 20 percent of removed instances, only 9 percent are removed as a direct consequence of refactoring operations.

1 March 2018
Verified
Conference Paper
Closed access
DNDario Di Nucci
Dario Di Nucci
FPFabio Palomba
Fabio Palomba
DTDamian A. Tamburri
Damian A. Tamburri
ASAlexander Serebrenik
Alexander Serebrenik
ALAndrea De Lucia
Andrea De Lucia
Code smells are symptoms of poor design and implementation choices weighing heavily on the quality of produced source code. During the last decades several code smell detection tools have been proposed. However, the literature shows that the results of these tools can be subjective and are intrinsically tied to the nature and approach of the detection. In a recent work the use of Machine-Learning (ML) techniques for code smell detection has been proposed, possibly solving the issue of tool subjectivity giving to a learner the ability to discern between smelly and non-smelly source code elements. While this work opened a new perspective for code smell detection, it only considered the case where instances affected by a single type smell are contained in each dataset used to train and test the machine learners. In this work we replicate the study with a different dataset configuration containing instances of more than one type of smell. The results reveal that with this configuration the machine learning techniques reveal critical limitations in the state of the art which deserve further research.

1 September 2015 in Journal of Systems and Software
Verified
Journal Article
Closed access
GBGabriele Bavota
Gabriele Bavota
ALAndrea De Lucia
Andrea De Lucia
MPMassimiliano Di Penta
Massimiliano Di Penta
RORocco Oliveto
Rocco Oliveto
FPFabio Palomba
Fabio Palomba