A Comprehensive View on TD Prevention Practices and Reasons for not Preventing It-Reference-Cited by-同舟云学术

A Comprehensive View on TD Prevention Practices and Reasons for not Preventing It

Published:2024-06-28 Issue: Volume: Page:
ISSN:1049-331X
Container-title:ACM Transactions on Software Engineering and Methodology
language:en
Short-container-title:ACM Trans. Softw. Eng. Methodol.

Author:

Freire Sávio¹^ORCID,Pacheco Alexia²,Rios Nicolli³^ORCID,Pérez Boris⁴^ORCID,Castellanos Camilo⁵,Correal Darío⁵^ORCID,Ramač Robert⁶^ORCID,Mandić Vladimir⁶^ORCID,Taušan Nebojša⁶^ORCID,López Gustavo²^ORCID,Mendonça Manoel⁷^ORCID,Falessi Davide⁸,Izurieta Clemente⁹^ORCID,Seaman Carolyn¹⁰^ORCID,Spínola Rodrigo¹¹^ORCID

Affiliation:

1. Federal Institute of Ceará, Morada Nova and Federal University of Bahia, Salvador, Brazil

2. University of Costa Rica, San José, Costa Rica

3. Federal University of Rio de Janeiro, Rio de Janeiro, Brazil

4. Francisco de Paula Santander University, Cúcuta, Colombia

5. University of Los Andes, Bogotá, Colombia

6. University of Novi Sad, Novi Sad, Serbia

7. Federal University of Bahia, Salvador, Brazil

8. University of Rome Tor Vergata, Rome, Italy

9. Montana State University, Bozeman, MT, United States

10. University of Maryland Baltimore County, Baltimore, MD, United States

11. Virginia Commonwealth University, Richmond, VA, United States

Abstract

Context . Technical debt (TD) prevention allows software practitioners to apply practices to avoid potential TD items in their projects. Aims. To uncover and prioritize, from the point of view of software practitioners, the practices that could be used to avoid TD items, the relations between these practices and the causes of TD, and the practice avoidance reasons (PARs) that could explain the failure to prevent TD. Method . We analyze data collected from six replications of a global industrial family of surveys on TD, totaling 653 answers. We also conducted a follow up survey to understand the importance level of analyzed data. Results . Most practitioners indicated that TD could be prevented, revealing 89 prevention practices and 23 PARs for explaining the failure to prevent TD. The paper identifies statistically significant relationships between preventive practices and certain causes of TD. Further, it prioritizes the list of practices, PARs, and relationships regarding their level of importance for TD prevention based on the opinion of software practitioners. Conclusion . This work organizes TD prevention practices and PARs in a conceptual map and the relationships between practices and causes of TD in a Sankey diagram to help the visualization of the body of knowledge reported in this study.

Publisher

Association for Computing Machinery (ACM)

Link

https://dl.acm.org/doi/pdf/10.1145/3674727

Reference68 articles.

1. ACM Special Interest Group on Software Engineering. ACM SIGSOFT Empirical Standards for Software Engineering. Available at: https://github.com/acmsigsoft/EmpiricalStandards. Access on Jan 25, 2024.

2. Anselm Strauss and Juliet Corbin. 1998. Basics of qualitative research: techniques and procedures for developing grounded theory. Sage Publications, Thousand Oaks, Calif. XIII.

3. Architecture Technical Debt: Understanding Causes and a Qualitative Model

4. Technical Debt in Costa Rica: An InsighTD Survey Replication

5. Familiarity, Causes and Reactions of Software Practitioners to the Presence of Technical Debt: A Replicated Study in the Chilean Software Industry

Cited by 1 articles. 订阅此论文施引文献订阅此论文施引文献，注册后可以免费订阅5篇论文的施引文献，订阅后可以查看论文全部施引文献

1. Hearing the Voice of Software Practitioners on Technical Debt Monitoring: Understanding Monitoring Practices and the Practices' Avoidance Reasons;Journal of Software Engineering Research and Development;2024-08-30