10.29327/1407529.27-33
Technical Debt (TD) in software engineering refers to the additional cost generated by inadequate decisions or implementations in software projects. Requirements TD emerges when specific requirements are overlooked, poorly understood, or implemented inadequately, leading to disparities between the developed product and the original specifications. In this context, requirements engineering should worry about how to prevent requirements TD from occurring and how to deal with requirements TD. This paper presents a qualitative study investigating the causes of requirements TD and identifying actions that can mitigate or resolve them. This qualitative study occurs in a software project of a partnership between an IT company and the Computer Networks, Software Engineering, and Systems Group (GREat) of the Federal University of Ceará. The literature review helped identify types and causes of RTD, later correlated with responses from exploratory questions in project retrospective sessions. With the qualitative analysis conducted, significant challenges were detected, especially in the requirements elicitation phase, highlighting the need for more effective approaches. To deal with these issues, actions aimed at mitigating and resolving existing Requirements Technical Debts were identified and implemented.
Requirements Engineering; Requirements Technical Debt; Qualitative Study
@inproceedings{wer202428,
author = {Oliveira, R. and Marques, A. B. and Santos, I. and Andrade, R.},
title = {Understanding Technical Debts of Requirements in an Industry Project: A Qualitative Study},
booktitle = {Proceedings of the WER2024-27th Workshop on Requirements Engineering, Buenos Aires, Argentina},
year = {2024},
issn = {2675-0066},
isbn = {978-65-01-06131-3},
doi = {10.29327/1407529.27-33}
}