Removal of Design Problems through Refactorings: Are We Looking at the Right Symptoms?

Eposhi, Andre; Oizumi, Willian; Garcia, Alessandro; Sousa, Leonardo; Oliveira, Roberto; Oliveira, Anderson

doi:10.1109/icpc.2019.00032

Cited by 16 publications

(13 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Eposhi et al [23] studied, among other things, the relationship between refactoring and code quality issues. Their findings show that (i) the density of code smells is more than 8 times higher in refactored classes and (ii) refactoring actions usually do not reduce the density of quality issues.…”

Section: Related Workmentioning

confidence: 99%

On the relationship between refactoring actions and bugs: a differentiated replication

Penta

Bavota

Zampetti

2020

Proceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Softw

View full text Add to dashboard Cite

Software refactoring aims at improving code quality while preserving the system's external behavior. Although in principle refactoring is a behavior-preserving activity, a study presented by Bavota et al. in 2012 reported the proneness of some refactoring actions (e.g., pull up method) to induce faults. The study was performed by mining refactoring activities and bugs from three systems. Taking profit of the advances made in the mining software repositories field (e.g., better tools to detect refactoring actions at commit-level granularity), we present a differentiated replication of the work by Bavota et al. in which we (i) overcome some of the weaknesses that affect their experimental design, (ii) answer the same research questions of the original study on a much larger dataset (3 vs 103 systems), and (iii) complement the quantitative analysis of the relationship between refactoring and bugs with a qualitative, manual inspection of commits aimed at verifying the extent to which refactoring actions trigger bug-fixing activities. The results of our quantitative analysis confirm the findings of the replicated study, while the qualitative analysis partially demystifies the role played by refactoring actions in the bug introduction. CCS CONCEPTS • Software and its engineering → Software reliability; Designing software.

show abstract

Section: Related Workmentioning

confidence: 99%

On the relationship between refactoring actions and bugs: a differentiated replication

Penta

Bavota

Zampetti

2020

Proceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Softw

View full text Add to dashboard Cite

show abstract

“…Different ways of measuring design quality have been investigated. Many researchers [12,13,24,25,44,46,47,52,56,69,70] have used code smells [32] to quantify design quality. Code smells are symptoms of poor design and implementation choices [32].…”

Section: Related Workmentioning

confidence: 99%

“…While trying to identify a suitable metric for measuring design quality, researchers have investigated different metrics such as Coupling Between Object (CBO), COupling Factor (COF), Weighted Method per Class (WMC), and code smells [13,20,24,44,47,56]. We opted to use the occurrence of code smell as a proxy for (poor) software design quality since a large number of studies have used and validated code smells for the aforementioned purpose [12,13,24,25,44,46,47,52,52,56,69,70].…”

Section: Introductionmentioning

confidence: 99%

On the relationship between design discussions and design quality: a case study of Apache projects

Mannan

Ahmed

Jensen

et al. 2020

Proceedings of the 28th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Softw

View full text Add to dashboard Cite

“…There are multiple studies about the perspective of developers about design degradation [28,34,37,69,91]. Other studies focus on the use of diversity and density of symptoms (i.e., code smells) as characteristics of design degradation [29,67,68].…”

Section: On the Impact Of Modern Code Review And Their Practices On Design Degradationmentioning

confidence: 99%

“…More specifically, even though studies have been investigating the impact of modern code review on design quality [11,15,21,24,40], most of them only address the relation between modern code review -and their practices -and design degradation in a constrained manner. Such studies tend to analyze design degradation considering only single events (related to design degradation), such as the introduction of a single design problem [34,37], or simply analyzing the degradation frequency [28,29,41,40].…”

Section: On the Impact Of Modern Code Review And Their Practices On Design Degradationmentioning

confidence: 99%

Unveiling Social and Technical Facets of Design Degradation in Modern Code Review

UCHOA¹

View full text Add to dashboard Cite

in 2016. Anderson has worked for Research & Development (R&D) projects in software engineering and information systems for healthcare, in collaboration with institutions from Brazil and the United Kingdom (UK). His collaborative work resulted in more than 25 peer-reviewed papers. Anderson collaborates with various researchers in Brazil (more recently, UFPR, UFPE, and UFC) and UK (Newcastle University). His main research interests are software gamification, code review, software reuse, software evolution, software maintenance, and human aspects.

show abstract

Removal of Design Problems through Refactorings: Are We Looking at the Right Symptoms?

Cited by 16 publications

References 31 publications

On the relationship between refactoring actions and bugs: a differentiated replication

On the relationship between refactoring actions and bugs: a differentiated replication

On the relationship between design discussions and design quality: a case study of Apache projects

Unveiling Social and Technical Facets of Design Degradation in Modern Code Review

Contact Info

Product

Resources

About