Search engine for discovering works of Art, research articles, and books related to Art and Culture
ShareThis
Javascript must be enabled to continue!

INVESTIGATION OF CODE SMELLS IN ECLIPSE FRAMEWORK USING SONARQUBE: AN EMPIRICAL ANALYSIS

View through CrossRef
The Eclipse Framework provides both public and internal Application Programming Interfaces (APIs). Public APIs are widely supported and encouraged for use, while internal APIs are considered immature and subject to frequent changes. However, the quality of these APIs is not guaranteed, with many users reporting code smells, which could lead to application failures if unresolved. While some studies indicate that not all code smells can be easily fixed, users often face the challenge of either addressing these issues themselves or abandoning problematic APIs. To address this, we conducted an empirical investigation using the SonarQube static code analysis tool on 28 major Eclipse releases, aiming to identify code-smell-free APIs. Our study provides a dataset of 218K code-smell-free public APIs and 321K internal APIs. We found that 87.3% of public APIs and 91.5% of internal APIs in the analyzed releases are free from code smells, highlighting the importance of using these cleaner alternatives for application stability and long-term usability. Furthermore, we have discovered that the number of code smells proportionately increases as the Eclipse framework evolves. The average number of code smells and technical debt is 147K and 2,744 days respectively in all the studied Eclipse releases.  Results from this study can be used by both interface providers and users as a starting point to recognize code smell-free interfaces and estimate efforts needed to fix code smells in each version of Eclipse.
Title: INVESTIGATION OF CODE SMELLS IN ECLIPSE FRAMEWORK USING SONARQUBE: AN EMPIRICAL ANALYSIS
Description:
The Eclipse Framework provides both public and internal Application Programming Interfaces (APIs).
Public APIs are widely supported and encouraged for use, while internal APIs are considered immature and subject to frequent changes.
However, the quality of these APIs is not guaranteed, with many users reporting code smells, which could lead to application failures if unresolved.
While some studies indicate that not all code smells can be easily fixed, users often face the challenge of either addressing these issues themselves or abandoning problematic APIs.
To address this, we conducted an empirical investigation using the SonarQube static code analysis tool on 28 major Eclipse releases, aiming to identify code-smell-free APIs.
Our study provides a dataset of 218K code-smell-free public APIs and 321K internal APIs.
We found that 87.
3% of public APIs and 91.
5% of internal APIs in the analyzed releases are free from code smells, highlighting the importance of using these cleaner alternatives for application stability and long-term usability.
Furthermore, we have discovered that the number of code smells proportionately increases as the Eclipse framework evolves.
The average number of code smells and technical debt is 147K and 2,744 days respectively in all the studied Eclipse releases.
  Results from this study can be used by both interface providers and users as a starting point to recognize code smell-free interfaces and estimate efforts needed to fix code smells in each version of Eclipse.

Related Results

Software Metric Based Impact Analysis of Code Smells ‐ A Large Scale Empirical Study
Software Metric Based Impact Analysis of Code Smells ‐ A Large Scale Empirical Study
ABSTRACTContextCode smells are indicators of poor design and implementation choices that negatively affect software quality and maintainability. Moreover, it is difficult and time‐...
Exploring Test Smells Across Programming Languages: A Systematic Mapping Study
Exploring Test Smells Across Programming Languages: A Systematic Mapping Study
Tests are essential for ensuring code quality in software development. However, poor implementation practices can compromise the maintainability and evolution of test code, leading...
Test smells 20 years later: detectability, validity, and reliability
Test smells 20 years later: detectability, validity, and reliability
AbstractTest smells aim to capture design issues in test code that reduces its maintainability. These have been extensively studied and generally found quite prevalent in both huma...
Discovering code smells in Javascript software using clustering techniques
Discovering code smells in Javascript software using clustering techniques
A presença de code smells em projetos de software têm consequências negativas no que diz respeito a coesão e manutenibilidade do código. Assim sendo, a análise de técnicas usadas p...
Overview of Bad Code Smells in Software Development and Researches
Overview of Bad Code Smells in Software Development and Researches
Abstract This study examines the occurrence, influence, and moderation of bad code smells in software development through a hybrid research methodology combining qualitativ...
An empirical study into the effects of transpilation on quantum circuit smells
An empirical study into the effects of transpilation on quantum circuit smells
AbstractQuantum computing is a promising field that can solve complex problems beyond traditional computers’ capabilities. Developing high-quality quantum software applications, ca...
Explaining the Imperfect: How do LLMs Respond to Smelly Code?
Explaining the Imperfect: How do LLMs Respond to Smelly Code?
Code smells are indicators of suboptimal design or implementation that contribute to technical debt, impairing software comprehensibility and maintainability. While Large Language ...
Dynamic stacking ensemble for cross-language code smell detection
Dynamic stacking ensemble for cross-language code smell detection
Code smells refer to poor design and implementation choices by software engineers that might affect the overall software quality. Code smells detection using machine learning model...

Back to Top