Investigating the Relationship between Technical Debt Management and Software Development Issues
artículo original
Fecha
2023-02-03Autor
Berenguer, Clara
Borges, Adriano
Freire, Sávio
Rios, Nicolli
Ramač, Robert
Taušan, Nebojša
Pérez, Boris
Castellanos, Camilo
Correal, Darío
Pacheco Hernández, Alexia
López Herrera, Gustavo
Mendonça, Manoel
Falessi, Davide
Seaman, Carolyn
Mandić, Vladimir
Izurieta, Clemente
Spínola, Rodrigo
Metadatos
Mostrar el registro completo del ítemResumen
Context: The presence of technical debt (TD) brings risks to software projects. Managers must continuously find a cost-benefit balance between the benefits of incurring in TD and the costs of its presence in a software project. Much attention has been given to TD related to coding issues, but other types of debt can also have impactful consequences on projects. Aims: This paper seeks to elaborate on the growing need to expand TD research to other areas of software development, by analyzing six elements related to TD management, namely: causes, effects, preventive practices, reasons for non-prevention, repayment practices, and reasons for non-repayment of TD. Method: We survey and analyze, quantitatively and qualitatively, the answers of 653 software industry practitioners on TD to investigate how the previously mentioned elements are related to coding and non-coding issues of the software development process. Results: Coding issues are commonly related to the investigated elements but, indeed, they are only part of the TD Management stage. Issues related to the project planning and management, human factors, knowledge, quality, process, requirements, verification, validation, and test, design, architecture, and the organization are also common sources of TD. We organize the results in a hump diagram and specialize it considering the point of view of practitioners that have used agile, hybrid, and traditional process models in their projects. Conclusion: The hump diagram, in combination with the detailed results, provides guidance on what to expect from the presence of TD and how to react to it considering several issues of software development. The results shed light on TD management of software elements, beyond source code related artifacts.
External link to the item
10.5753/jserd.2023.2581Colecciones
Ítems relacionados
Mostrando ítems relacionados por Título, autor o materia.
-
Execution of the “competency assessment” program implemented by the Ministry of Public Education in the Technical Education: the case of Professional Technical School in San Sebastian
Retana Morales, Jorge (2013-12-19)This article refers the results of the research about the program assessment by competences, implemented by the Ministry of public education in the technical education in the Professional Technical School in San Sebastian, ... -
Technical and Nontechnical Prioritization Schema for Technical Debt: Voice of TD-Experienced Practitioners
Mandić, Vladimir; Taušan, Nebojša; Ramač, Robert; Freire, Sávio; Rios, Nicolli; Pérez, Boris; Castellanos, Camilo; Correal, Darío; Pacheco Hernández, Alexia; López Herrera, Gustavo; Izurieta, Clemente; Falessi, Davide; Seaman, Carolyn; Spínola, Rodrigo (2021-08-09)Technical debt (TD) can be injected at any stage of software development, spreading across other phases and causing various problems. This article presents a model for conceptualizing TD causes, effects, payment practices, ... -
Análisis de la Calidad Técnica: Pruebas de Bachillerato Fórmula 11 Estudios Sociales.
Delgado Rojas, Marta E.; Quesada Selva, Katherine (IIMEC, 1998)Este informe es presentado por el IIMEC al Ministerio de Educación como parte de un estudio de calidad técnica de las pruebas de Bachillerato de Estudios Sociales aplicada en 1997 por el Ministerio de Educación Pública, a ...