Towards Quantifying Requirements Technical Debt for Software Requirements concerning Veracity: A Perspective and Research Roadmap

Fuente: arXiv
Enregistré dans:
Détails bibliographiques
Auteurs principaux: Perera, Judith, Tempero, Ewan, Tu, Yu-Cheng, Blincoe, Kelly, Galster, Matthias
Format: Preprint
Publié: 2024
Sujets:
Accès en ligne:
Tags: Ajouter un tag
Pas de tags, Soyez le premier à ajouter un tag!
_version_ 1866911938226683904
author Perera, Judith
Tempero, Ewan
Tu, Yu-Cheng
Blincoe, Kelly
Galster, Matthias
author_facet Perera, Judith
Tempero, Ewan
Tu, Yu-Cheng
Blincoe, Kelly
Galster, Matthias
contents Software practitioners can make sub-optimal decisions concerning requirements during gathering, documenting, prioritizing, and implementing requirements as software features or architectural design decisions -- this is captured by the metaphor `Requirements Technical Debt (RTD).' In our prior work, we developed a conceptual model to understand the quantification of RTD and support its management. In this paper, we present our perspective and the vision to apply the lens of RTD to software requirements concerning veracity, i.e., requirements related to truth, trust, authenticity, and demonstrability in software-intensive systems. Our goal is to cultivate awareness of veracity as an important concern and eventually support the management of RTD for software requirements concerning veracity, what we term as `Veracity Debt,' through its quantification.
format Preprint
id arxiv_https___arxiv_org_abs_2407_00391
institution arXiv
publishDate 2024
record_format arxiv
spellingShingle Towards Quantifying Requirements Technical Debt for Software Requirements concerning Veracity: A Perspective and Research Roadmap
Perera, Judith
Tempero, Ewan
Tu, Yu-Cheng
Blincoe, Kelly
Galster, Matthias
Software Engineering
Software practitioners can make sub-optimal decisions concerning requirements during gathering, documenting, prioritizing, and implementing requirements as software features or architectural design decisions -- this is captured by the metaphor `Requirements Technical Debt (RTD).' In our prior work, we developed a conceptual model to understand the quantification of RTD and support its management. In this paper, we present our perspective and the vision to apply the lens of RTD to software requirements concerning veracity, i.e., requirements related to truth, trust, authenticity, and demonstrability in software-intensive systems. Our goal is to cultivate awareness of veracity as an important concern and eventually support the management of RTD for software requirements concerning veracity, what we term as `Veracity Debt,' through its quantification.
title Towards Quantifying Requirements Technical Debt for Software Requirements concerning Veracity: A Perspective and Research Roadmap
topic Software Engineering
url https://arxiv.org/abs/2407.00391