Identification and measurement of Requirements Technical Debt in software development: A systematic literature review

Melo, Ana Duarte; Fagundes, Roberta; Lenarduzzi, Valentina; Santos, Wylliams Barbosa

doi:10.1016/j.jss.2022.111483

Cited by 26 publications

(18 citation statements)

References 44 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Similar to previous studies related to TD in RE [12,10], we are interested in understanding the concepts of RED and how to manage it. In contrast to previous studies on RED [3,4,14], we focus on the view of practitioners.…”

Section: Methodsmentioning

confidence: 99%

“…More recently, a systematic literature review by Melo et al [14] covered the causes of RED as well as methods to identify and manage it. They identified 66 primary studies that, although not explicitly focusing on RED, contained instances of investigations addressing activities related to RE, for instance, in design and documentation.…”

Section: Conceptsmentioning

confidence: 99%

“…Through the application of the TD metaphor first to requirements documentation [12,10] and later to requirements engineering in general [3,4,14], the research community established a conceptual foundation of RED. However, an empirical perspective on RED in practice is still a gap that we address in this study.…”

Section: Conceptsmentioning

confidence: 99%

See 2 more Smart Citations

An Initial Theory to Understand and Manage Requirements Engineering Debt in Practice

Frattini¹,

Fucci²,

Méndez³

et al. 2022

SSRN Journal

View full text Add to dashboard Cite

Section: Methodsmentioning

confidence: 99%

Section: Conceptsmentioning

confidence: 99%

See 1 more Smart Citation

An Initial Theory to Understand and Manage Requirements Engineering Debt in Practice

Frattini¹,

Fucci²,

Méndez³

et al. 2022

SSRN Journal

View full text Add to dashboard Cite

“…O Gerenciamento de Dívida Técnicas (GDT) é uma maneira de minimizar o risco de danos que as DTs podem causar ao projeto. Existem diferentes abordagens para a execuc ¸ão do GDT, onde uma das etapas do processo é a priorizac ¸ão das dívidas técnicas encontradas, com o objetivo de identificar os itens mais urgentes a serem resolvidos às custas dos itens que podem esperar mais na fila para serem pagos [Melo et al 2022] [Melo et al 2021.…”

Section: Introduc ¸ãOunclassified

Priorização de Dívidas Técnicas Orientada a Negócios com Tracy-TD: Estudo de caso na empresa COMEIA

Silva¹,

Almeida

Santos³

2022

Anais Estendidos Do XIII Congresso Brasileiro De Software: Teoria E Prática (CBSoft Estendido 2022)

View full text Add to dashboard Cite

Contexto: Dívida Técnica (DT) refere-se às soluções de baixa qualidade para um benefício imediato que precisam ser resolvidas posteriormente. Problema: Um projeto pode ter um volume de DTs que inviabilize a sua total quitação. É necessário priorizá-las para focar nas DTs com maior risco ao negócio. Objetivo: Contribuir com a avaliação da abordagem de priorização de DT alinhada ao negócio. Método: Estudo de caso com profissionais da indústria. Resultados: Identificamos o nível de alinhamento entre as visões técnica e de negócio, regra de priorização, e fatores que impactam a priorização das DTs. Conclusão: A validade da abordagem Tracy foi conferida em novo ambiente, bem como uma oportunidade de desdobramento da pesquisa foi observado.

show abstract

“…Inicialmente, o foco da DT estava nas atividades de codificação, mas à medida que a pesquisa se desenvolveu, o conceito foi ampliado para as demais fases de software e desenvolvimento de software, por exemplo, na engenharia de requisitos (MELO et al, 2022). Segundo Ernst (2012) , uma elicitação ou análise inadequada de requisitos causa erros que aumentam a incidência de DT em projetos de software.…”

Section: Dívida Técnica De Requisitosunclassified

What Strategies Are Used for the Payment of Requirements Debt in Software Development?

Santos¹,

Galegale²

19th CONTECSI International Conference on Information Systems and Technology Management

View full text Add to dashboard Cite

The concept of technical debt in software development emerged by Cunningham (1992). Since then, this topic has been discussed and explored by several authors. There are types of technical debt corresponding to the phases of the software development cycle, such as requirements debt. This type of debt was initially mentioned by Ernst ( 2012), approximately 20 years after the introduction of the technical debt metaphor. This article aims to identify which are the strategies for payment requirements debt since the advent of the concept. The method used was literature review and content analysis with the application based on the PRISMA-P protocol, through descriptive research. The results, so far, reveal that there is still little discussion on the subject of technical debt of requirements. The main approach of the research refers to the types of technical debt of code and architecture.

show abstract

Identification and measurement of Requirements Technical Debt in software development: A systematic literature review

Cited by 26 publications

References 44 publications

An Initial Theory to Understand and Manage Requirements Engineering Debt in Practice

An Initial Theory to Understand and Manage Requirements Engineering Debt in Practice

Priorização de Dívidas Técnicas Orientada a Negócios com Tracy-TD: Estudo de caso na empresa COMEIA

What Strategies Are Used for the Payment of Requirements Debt in Software Development?

Contact Info

Product

Resources

About