Analyzing the Rework Time and Severity of Code Debt: A Case Study Using Technical Debt Catalogs
This provides insights for software developers and maintainers in the Hibernate ecosystem to prioritize debt management, though it is an incremental study focused on a specific domain.
The paper analyzed Hibernate ecosystem projects to study Code Debt behavior, finding that debt with high maintenance impact severity is most common and requires the largest rework times, with rework time distributions varying in early development versions.
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.