Analyzing the Rework Time and Severity of Code Debt: A Case Study Using Technical Debt Catalogs

by   Bruno Santos de Lima, et al.

This paper presents a case study analyzing Hibernate ecosystem software projects to investigate and demonstrate Code Debt behavior in relation to severity and rework time. The case study carried out revealed that the Code Debt with severity related to impact on software maintenance is the most representative and has the largest rework times to be paid in the Hibernate ecosystem. Besides, it was found that the distributions of rework times of Code Debt for all severities undergo variations in the initial versions of the development.


page 1

page 2

page 3

page 4


Can Clean New Code reduce Technical Debt Density?

While technical debt grows in absolute numbers as software systems evolv...

Release as a Contract: A Concept of Meta-Maintenance for the Entire FLOSS Ecosystem

We advocate for a paradigm shift in supporting free/libre and open sourc...

On The Effect Of Code Review On Code Smells

Code smells are symptoms of poor design quality. Since code review is a ...

The Evolving Ecosystem of Predatory Journals: A Case Study in Indian Perspective

Digital advancement in scholarly repositories has led to the emergence o...

Does Migrate a Monolithic System to Microservices Decreases the Technical Debt?

Background. The migration from monolithic systems to microservices invol...

Some SonarQube Issues have a Significant but SmallEffect on Faults and Changes. A large-scale empirical study

Context. Companies commonly invest effort to remove technical issues bel...