Further investigation of the survivability of code technical debt items

  title={Further investigation of the survivability of code technical debt items},
  author={Ehsan Zabardast and Kwabena Ebo Bennin and Javier Gonzalez-Huerta},
  journal={Journal of Software: Evolution and Process},
Context: Technical debt (TD) discusses the negative impact of sub‐optimal decisions to cope with the need‐for‐speed in software development. Code technical debt items (TDI) are atomic elements of TD that can be observed in code artifacts. Empirical results on open‐source systems demonstrated how code‐smells, which are just one type of TDIs, are introduced and “survive” during release cycles. However, little is known about whether the results on the survivability of code‐smells hold for other… 



How do developers fix issues and pay back technical debt in the Apache ecosystem?

A case study is presented, in which the evolution of fifty-seven Java open-source software projects by the Apache Software Foundation is analyzed at the temporal granularity level of weekly snapshots and it is revealed that a small subset of all issue types is responsible for the largest percentage of TD repayment.

The Evolution of Technical Debt in the Apache Ecosystem

This paper studies sixty-six Java open-source software projects from the Apache ecosystem focusing on the evolution of technical debt and calculates the trends of the technical debt time series but also investigates the lower-level constituent components of this technical debt.

A systematic mapping study on technical debt and its management

Investigating the Evolution of Bad Smells in Object-Oriented Code

This paper explores the presence and evolution of non-trivial bad smells by analyzing past versions of code and attempts to study the subject from the point of view of the problems themselves distinguishing deliberate maintenance activities from the removal of design problems as a side effect of software evolution.

Refactoring, Bug Fixing, and New Development Effect on Technical Debt: An Industrial Case Study

An empirical study on an industrial project and investigated how Refactoring, Bug Fixing, and New Development affect the Technical Debt, suggesting that TD in the studied project is mainly introduced in the development of new features.

Quantifying the Effect of Code Smells on Maintenance Effort

To reduce maintenance effort, a focus on reducing code size and the work practices that limit the number of changes may be more beneficial than refactoring code smells.

On the Accuracy of SonarQube Technical Debt Remediation Time

SonarQube remediation time, compared to the actual time for reducing technical debt, is generally overestimated, and that the most accurate estimation relates to code smells, while the least accurate concerns bugs.

On the diffuseness of code technical debt in Java projects of the apache ecosystem

The goal is to understand which type of TD is more diffused and how much attention is paid by the developers, as well as to investigate whether TD issues with a higherlevel of severity are resolved faster than those with a lower level of severity.

Are Static Analysis Violations Really Fixed? A Closer Look at Realistic Usage of SonarQube

A comprehensive, multi-method study about the usage of SonarQube, finding a low resolution rate per project in all organizations and conjecture that just a subset of the checkers reveal real design and coding flaws, and this might artificially increase the technical debt of the systems.

Monitoring Technical Debt in an Industrial Setting

The outcomes of this study can be useful to both researchers and practitioners, in the sense that the former can focus their efforts on aspects that are meaningful to industry, whereas the latter to develop meaningful dashboards, with multiple views.