Correlation Between Code Smells for Open Source Java Projects

2021 ◽  
pp. 7-15
Author(s):  
Inderpreet Kaur ◽  
Arvinder Kaur
Keyword(s):  
2018 ◽  
Vol 144 ◽  
pp. 1-21 ◽  
Author(s):  
Bartosz Walter ◽  
Francesca Arcelli Fontana ◽  
Vincenzo Ferme

2021 ◽  
Vol ahead-of-print (ahead-of-print) ◽  
Author(s):  
Stuti Tandon ◽  
Vijay Kumar ◽  
V.B. Singh

PurposeCode smells indicate deep software issues. They have been studied by researchers with different perspectives. The need to study code smells was felt from the perspective of software industry. The authors aim to evaluate the code smells on the basis of their scope of impact on widely used open-source software (OSS) projects.Design/methodology/approachThe authors have proposed a methodology to identify and rank the smells in the source code of 16 versions of Apache Tomcat Software. Further, the authors have analyzed the categorized smells by calculating the weight of the smells using constant weights as well as Best Worst Method (BWM). Consequently, the authors have used Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS) to determine the rank of versions using constant weights as well as BWM.FindingsVersion 1 of Apache Tomcat has least smell, and version 8 is reported to contain the maximum code smells. Notable differences in both the cases during the trend analysis are reported by the study. The findings also show that increase is observed in the number of code smells with the release of newer versions. This increment is observed till version 8, followed by a subtle marked depreciation in the number of code smells in further releases.Originality/valueThe focus is to analyze smells and rank several versions of Apache Tomcat, one of the most widely used software for code smell study. This study will act as a significant one for the researchers as it prioritizes the versions and will help in narrowing down the options of the software used to study code smell.


2019 ◽  
Author(s):  
Felipe Gustavo De S. Gomes ◽  
Thiago Souto Mendes ◽  
Rodrigo O. Spínola ◽  
Manoel Mendonça ◽  
Mário Farias
Keyword(s):  

Code smells indicam possíveis problemas na implementação de um sistema que podem levar a` necessidade de refatoração do seu código. Eles podem ser detectados automaticamente e são considerados indicadores de presença de Dívida Técnica (DT). Contudo, estudos indicam que considerar apenas code smells na tarefa de detecção da presença de itens de dívida é insuficiente. E ́ necessário utilizar estratégias de detecção complementares, como a utilização de informações extráıdas a partir de comentários de código. Porém, ainda são poucos os estudos sobre a relação entre code smells e DT autoadmitida. Este trabalho analisa três projetos open source para investigar a relação existente, em termos de sobreposição e complementariedade de itens de DT identificados, utilizando detecção via code smells e DT auto-admitida. Os resultados indicam que as informações de comentários podem complementar as informações de code smells e apoiar os desenvolvedores a identificar DT.


Author(s):  
Bernardo Oliveira Rosa

Este trabalho visa contribuir com evidências experimentais para a discussão sobre CodeSmell (FOWLER, 1999) e a utilidade real de sua identificação e estudo para a indústriade software. Code smells, ou, numa tradução literal, “mal cheiros de código”, é umconceito utilizado na Programação Orientada a Objetos para determinar se um projetopode vir a ter problemas no sua evolução.


Information ◽  
2018 ◽  
Vol 9 (11) ◽  
pp. 273 ◽  
Author(s):  
Aloisio Cairo ◽  
Glauco Carneiro ◽  
Miguel Monteiro

Context: Code smells are associated to poor design and programming style, which often degrades code quality and hampers code comprehensibility and maintainability. Goal: identify published studies that provide evidence of the influence of code smells on the occurrence of software bugs. Method: We conducted a Systematic Literature Review (SLR) to reach the stated goal. Results: The SLR selected studies from July 2007 to September 2017, which analyzed the source code of open source software projects and several code smells. Based on evidence of 16 studies covered in this SLR, we conclude that 24 code smells are more influential in the occurrence of bugs relative to the remaining smells analyzed. In contrast, three studies reported that at least 6 code smells are less influential in such occurrences. Evidence from the selected studies also point out tools, techniques, and procedures that should be applied to analyze the influence of the smells. Conclusions: To the best of our knowledge, this is the first SLR to target this goal. This study provides an up-to-date and structured understanding of the influence of code smells on the occurrence of software bugs based on findings systematically collected from a list of relevant references in the latest decade.


Author(s):  
Aloisio Cairo ◽  
Glauco Carneiro ◽  
Miguel Monteiro

Context: Code smells are associated with poor design and programming style that often degrades code quality and hampers code comprehensibility and maintainability. Goal: Identify reports from the literature that provide evidence of the influence of code smells on the occurrence of software bugs. Method: We conducted a Systematic Literature Review (SLR) to reach the~stated goal. Results: The SLR includes selected studies from July 2007 to September 2017 which analyzed the source code for open source and proprietary projects, as well, as several code smells and anti-patterns. The results of this SLR show that 24 code smells are more influential in the occurrence of bugs according to 16 studies. In contrast, three studies reported that at least 6 code smells are less influential in such occurrences. Evidence from the selected studies also point out tools, techniques and procedures applied to analyze the influence. Conclusion: To the best of our knowledge, this is the first SLR to target this goal. This study provides an up-to-date and structured understanding of the influence of code smells on the occurrence of software bugs based on findings systematically collected from a list of relevant references in the latest decade.


Sign in / Sign up

Export Citation Format

Share Document