{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,4,9]],"date-time":"2026-04-09T02:46:51Z","timestamp":1775702811542,"version":"3.50.1"},"reference-count":43,"publisher":"Springer Science and Business Media LLC","issue":"4","license":[{"start":{"date-parts":[[2024,7,6]],"date-time":"2024-07-06T00:00:00Z","timestamp":1720224000000},"content-version":"tdm","delay-in-days":0,"URL":"https:\/\/creativecommons.org\/licenses\/by\/4.0"},{"start":{"date-parts":[[2024,7,6]],"date-time":"2024-07-06T00:00:00Z","timestamp":1720224000000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/creativecommons.org\/licenses\/by\/4.0"}],"funder":[{"DOI":"10.13039\/501100003524","name":"Ministry of Business, Innovation and Employment","doi-asserted-by":"publisher","award":["The Science for Technological Innovation (SfTI) National Science Challenge Veracity Technology Spearhead"],"award-info":[{"award-number":["The Science for Technological Innovation (SfTI) National Science Challenge Veracity Technology Spearhead"]}],"id":[{"id":"10.13039\/501100003524","id-type":"DOI","asserted-by":"publisher"}]},{"DOI":"10.13039\/501100001537","name":"University of Auckland","doi-asserted-by":"crossref","id":[{"id":"10.13039\/501100001537","id-type":"DOI","asserted-by":"crossref"}]}],"content-domain":{"domain":["link.springer.com"],"crossmark-restriction":false},"short-container-title":["Requirements Eng"],"published-print":{"date-parts":[[2024,12]]},"abstract":"<jats:title>Abstract<\/jats:title><jats:p>Requirements Technical Debt (RTD) applies the Technical Debt (TD) metaphor to capture the consequences of sub-optimal decisions made concerning Requirements. Understanding the quantification of RTD is key to its management. To facilitate this understanding, we developed a conceptual model, the <jats:italic>Requirements\u00a0Technical\u00a0Debt\u00a0Quantification Model (RTDQM)<\/jats:italic>. Our work is grounded in the literature found via a systematic mapping study and informed by prior work modeling the quantification of software code-related TD types. The key finding is that although RTD is similar to code-related TD in many aspects, it also has its own components. RTD can be incurred regardless of the presence of code-related TD. Unlike code-related TD, RTD has a feedback loop involving the user. RTD can have a cascading impact on other development activities, such as design and implementation, apart from the extra costs and efforts incurred during requirements engineering activities; this is modeled by the RTD Interest constituents in our model. The model was used to compare and analyze existing quantification approaches. It helped identify what RTD quantification concepts are discussed in the existing approaches and what concepts are supported by metrics for their quantification. The model serves as a reference for practitioners to select existing or to develop new quantification approaches to support informed decision-making for RTD management.<\/jats:p>","DOI":"10.1007\/s00766-024-00424-3","type":"journal-article","created":{"date-parts":[[2024,7,6]],"date-time":"2024-07-06T07:01:47Z","timestamp":1720249307000},"page":"421-458","update-policy":"https:\/\/doi.org\/10.1007\/springer_crossmark_policy","source":"Crossref","is-referenced-by-count":7,"title":["Modelling the quantification of requirements technical debt"],"prefix":"10.1007","volume":"29","author":[{"ORCID":"https:\/\/orcid.org\/0000-0002-1092-4229","authenticated-orcid":false,"given":"Judith","family":"Perera","sequence":"first","affiliation":[]},{"ORCID":"https:\/\/orcid.org\/0000-0002-3786-1707","authenticated-orcid":false,"given":"Ewan","family":"Tempero","sequence":"additional","affiliation":[]},{"ORCID":"https:\/\/orcid.org\/0000-0001-7284-7081","authenticated-orcid":false,"given":"Yu-Cheng","family":"Tu","sequence":"additional","affiliation":[]},{"ORCID":"https:\/\/orcid.org\/0000-0003-4092-9706","authenticated-orcid":false,"given":"Kelly","family":"Blincoe","sequence":"additional","affiliation":[]}],"member":"297","published-online":{"date-parts":[[2024,7,6]]},"reference":[{"key":"424_CR1","doi-asserted-by":"crossref","unstructured":"Bonfim VD, Benitti FBV (2022) Requirements debt: causes, consequences, and mitigating practices. In: SEKE, pp 13\u201318","DOI":"10.18293\/SEKE2022-114"},{"key":"424_CR2","doi-asserted-by":"crossref","unstructured":"Ernst NA (2012) On the role of requirements in understanding and managing technical debt. In: 2012 third international workshop on managing technical debt, pp 61\u201364. IEEE","DOI":"10.1109\/MTD.2012.6226002"},{"key":"424_CR3","doi-asserted-by":"publisher","unstructured":"Perera J, Tempero E, Tu Y-C, Blincoe K (2023) Quantifying requirements technical debt: a systematic mapping study and a conceptual model. In: 2023 IEEE 31st international requirements engineering conference (RE), pp 123\u2013133. https:\/\/doi.org\/10.1109\/RE57278.2023.00021","DOI":"10.1109\/RE57278.2023.00021"},{"key":"424_CR4","doi-asserted-by":"crossref","unstructured":"Abad ZSH, Ruhe G (2015) Using real options to manage technical debt in requirements engineering. In: 2015 IEEE 23rd international requirements engineering conference, pp 230\u2013235. IEEE","DOI":"10.1109\/RE.2015.7320428"},{"key":"424_CR5","doi-asserted-by":"publisher","unstructured":"Perera J, Tempero E, Tu Y-C, Blincoe K (2023) Quantifying technical debt: a systematic mapping study and a conceptual model. arXiv preprint arXiv:2303.06535https:\/\/doi.org\/10.48550\/arXiv.2303.06535","DOI":"10.48550\/arXiv.2303.06535"},{"issue":"321","key":"424_CR6","first-page":"1","volume":"31","author":"N Guarino","year":"2020","unstructured":"Guarino N, Guizzardi G, Mylopoulos J (2020) On the philosophical foundations of conceptual models. Inf Modell Knowl Bases 31(321):1","journal-title":"Inf Modell Knowl Bases"},{"key":"424_CR7","doi-asserted-by":"crossref","unstructured":"Delcambre LM, Liddle SW, Pastor O, Storey VC (2018) A reference framework for conceptual modeling. In: Conceptual modeling: 37th international conference, ER 2018, Xi\u2019an, China, October 22\u201325, 2018, Proceedings 37, pp 27\u201342. Springer","DOI":"10.1007\/978-3-030-00847-5_4"},{"key":"424_CR8","doi-asserted-by":"publisher","first-page":"193","DOI":"10.1016\/j.jss.2014.12.027","volume":"101","author":"Z Li","year":"2015","unstructured":"Li Z, Avgeriou P, Liang P (2015) A systematic mapping study on technical debt and its management. J Syst Softw 101:193\u2013220","journal-title":"J Syst Softw"},{"issue":"October","key":"424_CR9","doi-asserted-by":"publisher","first-page":"29","DOI":"10.1145\/157709.157715","volume":"F1296","author":"W Cunningham","year":"1992","unstructured":"Cunningham W (1992) The WyCash portfolio management system. Proc Conf Object-Oriented Program Syst Lang Appl OOPSLA Part F1296(October):29\u201330. https:\/\/doi.org\/10.1145\/157709.157715","journal-title":"Proc Conf Object-Oriented Program Syst Lang Appl OOPSLA Part"},{"key":"424_CR10","doi-asserted-by":"publisher","first-page":"117","DOI":"10.1016\/j.infsof.2018.05.010","volume":"102","author":"N Rios","year":"2018","unstructured":"Rios N, Mendon\u00e7a Neto MG, Sp\u00ednola RO (2018) A tertiary study on technical debt: types, management strategies, research trends, and base information for practitioners. Inf Softw Technol 102:117\u2013145","journal-title":"Inf Softw Technol"},{"key":"424_CR11","unstructured":"Avgeriou P, Kruchten P, Ozkaya I, Seaman C (2016) Managing technical debt in software engineering (dagstuhl seminar 16162). In: Dagstuhl reports, vol. 6"},{"key":"424_CR12","doi-asserted-by":"publisher","DOI":"10.1016\/j.jss.2022.111483","volume":"194","author":"A Melo","year":"2022","unstructured":"Melo A, Fagundes R, Lenarduzzi V, Santos WB (2022) Identification and measurement of requirements technical debt in software development: a systematic literature review. J Syst Softw 194:111483","journal-title":"J Syst Softw"},{"key":"424_CR13","doi-asserted-by":"crossref","unstructured":"Lenarduzzi V, Fucci D (2019) Towards a holistic definition of requirements debt. In: 2019 ACM\/IEEE international symposium on empirical software engineering and measurement, pp 1\u20135. IEEE","DOI":"10.1109\/ESEM.2019.8870159"},{"key":"424_CR14","doi-asserted-by":"publisher","DOI":"10.1016\/j.infsof.2023.107201","volume":"159","author":"J Frattini","year":"2023","unstructured":"Frattini J, Fucci D, Mendez D, Sp\u00ednola R, Mandi\u0107 V, Tau\u0161an N, Ahmad MO, Gonzalez-Huerta J (2023) An initial theory to understand and manage requirements engineering debt in practice. Inf Softw Technol 159:107201. https:\/\/doi.org\/10.1016\/j.infsof.2023.107201","journal-title":"Inf Softw Technol"},{"key":"424_CR15","doi-asserted-by":"crossref","unstructured":"Nugroho A, Visser J, Kuipers T (2011) An empirical model of technical debt and interest. In: Proceedings of the 2nd workshop on managing technical debt, pp 1\u20138","DOI":"10.1145\/1985362.1985364"},{"key":"424_CR16","doi-asserted-by":"publisher","first-page":"100","DOI":"10.1016\/j.infsof.2015.10.008","volume":"70","author":"NS Alves","year":"2016","unstructured":"Alves NS, Mendes TS, Mendon\u00e7a MG, Sp\u00ednola RO, Shull F, Seaman C (2016) Identification and management of technical debt: a systematic mapping study. Inf Softw Technol 70:100\u2013121","journal-title":"Inf Softw Technol"},{"key":"424_CR17","doi-asserted-by":"publisher","first-page":"139","DOI":"10.1016\/j.infsof.2016.10.004","volume":"82","author":"WN Behutiye","year":"2017","unstructured":"Behutiye WN, Rodr\u00edguez P, Oivo M, Tosun A (2017) Analyzing the concept of technical debt in the context of agile software development: a systematic literature review. Inf Softw Technol 82:139\u2013158","journal-title":"Inf Softw Technol"},{"issue":"8","key":"424_CR18","doi-asserted-by":"publisher","first-page":"792","DOI":"10.1016\/j.infsof.2010.03.006","volume":"52","author":"B Kitchenham","year":"2010","unstructured":"Kitchenham B, Pretorius R, Budgen D, Brereton OP, Turner M, Niazi M, Linkman S (2010) Systematic literature reviews in software engineering-a tertiary study. Inf Softw Technol 52(8):792\u2013805","journal-title":"Inf Softw Technol"},{"key":"424_CR19","doi-asserted-by":"crossref","unstructured":"Petersen K, Feldt R, Mujtaba S, Mattsson M (2008) Systematic mapping studies in software engineering. In: 12th international conference on evaluation and assessment in software engineering, pp 1\u201310","DOI":"10.14236\/ewic\/EASE2008.8"},{"issue":"4","key":"424_CR20","doi-asserted-by":"publisher","first-page":"571","DOI":"10.1016\/j.jss.2006.07.009","volume":"80","author":"P Brereton","year":"2007","unstructured":"Brereton P, Kitchenham BA, Budgen D, Turner M, Khalil M (2007) Lessons from applying the systematic literature review process within the software engineering domain. J Syst Softw 80(4):571\u2013583","journal-title":"J Syst Softw"},{"issue":"3","key":"424_CR21","doi-asserted-by":"publisher","first-page":"2059","DOI":"10.1007\/s11192-014-1506-1","volume":"102","author":"A Cavacini","year":"2015","unstructured":"Cavacini A (2015) What is the best database for computer science journal articles? Scientometrics 102(3):2059\u20132071","journal-title":"Scientometrics"},{"key":"424_CR22","doi-asserted-by":"crossref","unstructured":"Wohlin C (2014) Guidelines for snowballing in systematic literature studies and a replication in software engineering. In: Proceedings of the 18th international conference on evaluation and assessment in software engineering, pp 1\u201310","DOI":"10.1145\/2601248.2601268"},{"issue":"2","key":"424_CR23","doi-asserted-by":"publisher","first-page":"77","DOI":"10.1191\/1478088706qp063oa","volume":"3","author":"V Braun","year":"2006","unstructured":"Braun V, Clarke V (2006) Using thematic analysis in psychology. Qual Res Psychol 3(2):77\u2013101","journal-title":"Qual Res Psychol"},{"key":"424_CR24","doi-asserted-by":"crossref","unstructured":"Charalampidou S, Ampatzoglou A, Chatzigeorgiou A, Tsiridis N (2018) Integrating traceability within the ide to prevent requirements documentation debt. In: 2018 44th euromicro conference on software engineering and advanced applications, pp 421\u2013428. IEEE","DOI":"10.1109\/SEAA.2018.00075"},{"key":"424_CR25","doi-asserted-by":"crossref","unstructured":"Belle AB, Lethbridge TC, Kpodjedo S, Adesina OO, Garz\u00f3n MA (2019) A novel approach to measure confidence and uncertainty in assurance cases. In: 2019 IEEE 27th international requirements engineering conference workshops, pp 24\u201333. IEEE","DOI":"10.1109\/REW.2019.00011"},{"key":"424_CR26","unstructured":"Lenarduzzi V, Fucci D, Mend\u00e9z D (2020) On the perceived harmfulness of requirement smells: An empirical study. In: Joint 26th international conference on requirements engineering: foundation for software quality workshops, doctoral symposium, live studies track, and poster track, Pisa; Italy, vol. 2584. CEUR-WS"},{"key":"424_CR27","doi-asserted-by":"crossref","unstructured":"Ojameruaye B, Bahsoon R (2014) Systematic elaboration of compliance requirements using compliance debt and portfolio theory. In: Requirements engineering: foundation for software quality: 20th international working conference, REFSQ 2014, Essen, Germany, April 7\u201310, 2014. Proceedings 20, pp 152\u2013167. Springer","DOI":"10.1007\/978-3-319-05843-6_12"},{"key":"424_CR28","doi-asserted-by":"publisher","DOI":"10.1016\/j.jss.2021.111112","volume":"183","author":"W Behutiye","year":"2022","unstructured":"Behutiye W, Rodr\u00edguez P, Oivo M, Aaramaa S, Partanen J, Abherv\u00e9 A (2022) Towards optimal quality requirement documentation in agile software development: a multiple case study. J Syst Softw 183:111112","journal-title":"J Syst Softw"},{"key":"424_CR29","doi-asserted-by":"publisher","DOI":"10.1016\/j.infsof.2023.107201","volume":"159","author":"J Frattini","year":"2023","unstructured":"Frattini J, Fucci D, Mendez D, Spinola R, Mandi\u0107 V, Tau\u0161an N, Ahmad MO, Gonzalez-Huerta J (2023) An initial theory to understand and manage requirements engineering debt in practice. Inf Softw Technol 159:107201","journal-title":"Inf Softw Technol"},{"key":"424_CR30","doi-asserted-by":"publisher","first-page":"96","DOI":"10.1016\/j.infsof.2017.04.002","volume":"88","author":"P Mohagheghi","year":"2017","unstructured":"Mohagheghi P, Aparicio ME (2017) An industry experience report on managing product quality requirements in a large organization. Inf Softw Technol 88:96\u2013109","journal-title":"Inf Softw Technol"},{"key":"424_CR31","doi-asserted-by":"crossref","unstructured":"Ojameruaye B, Bahsoon R, Duboc L (2016) Sustainability debt: a portfolio-based approach for evaluating sustainability requirements in architectures. In: Proceedings of the 38th International Conference on Software Engineering Companion, pp 543\u2013552","DOI":"10.1145\/2889160.2889218"},{"key":"424_CR32","doi-asserted-by":"crossref","unstructured":"Costa AFF, Marques ABDS, Santos IS, Andrade RMDC (2022) Towards a process to manage usability technical debts. In: Proceedings of the XXXVI Brazilian Symposium on Software Engineering, pp 241\u2013246","DOI":"10.1145\/3555228.3555266"},{"key":"424_CR33","doi-asserted-by":"crossref","unstructured":"Mendes TS, F Farias MA, Mendon\u00e7a M, Soares HF, Kalinowski M, Sp\u00ednola RO (2016) Impacts of agile requirements documentation debt on software projects: a retrospective study. In: Proceedings of the 31st annual ACM symposium on applied computing, pp 1290\u20131295","DOI":"10.1145\/2851613.2851761"},{"key":"424_CR34","unstructured":"Sivzattian S, Nuseibeh B (2001) Linking the selection of requirements to market value: A portfolio-based approach. In: Proceedings of 7th international workshop on requirements engineering: foundation for software quality (REFSQ 2001)"},{"key":"424_CR35","doi-asserted-by":"crossref","unstructured":"Barbosa L, Freire S, Rios N, Rama\u010d R, Tau\u0161an N, P\u00e9rez B, Castellanos C, Correal D, Pacheco A, L\u00f3pez G, et al (2022) Organizing the td management landscape for requirements and requirements documentation debt. UMBC Faculty Collection","DOI":"10.29327\/1298262.25-7"},{"key":"424_CR36","doi-asserted-by":"crossref","unstructured":"Kazman R, Asundi J, Klein M (2001) Quantifying the costs and benefits of architectural decisions. In: Proceedings of the 23rd international conference on software engineering. ICSE 2001, pp 297\u2013306. IEEE","DOI":"10.1109\/ICSE.2001.919103"},{"issue":"5","key":"424_CR37","doi-asserted-by":"publisher","first-page":"67","DOI":"10.1109\/52.605933","volume":"14","author":"J Karlsson","year":"1997","unstructured":"Karlsson J, Ryan K (1997) A cost-value approach for prioritizing requirements. IEEE Softw 14(5):67\u201374","journal-title":"IEEE Softw"},{"key":"424_CR38","doi-asserted-by":"crossref","unstructured":"Charalampidou S, Ampatzoglou A, Chatzigeorgiou A, Avgeriou P (2017) Assessing code smell interest probability: a case study. In: Proceedings of the XP2017 scientific workshops, pp 1\u20138","DOI":"10.1145\/3120459.3120465"},{"key":"424_CR39","doi-asserted-by":"publisher","DOI":"10.1016\/j.infsof.2022.106964","volume":"149","author":"HJ Junior","year":"2022","unstructured":"Junior HJ, Travassos GH (2022) Consolidating a common perspective on technical debt and its management through a tertiary study. Inf Softw Technol 149:106964","journal-title":"Inf Softw Technol"},{"key":"424_CR40","volume-title":"Sommerville: software engineering","author":"I Sommerville","year":"2011","unstructured":"Sommerville I (2011) Sommerville: software engineering. Pearson, London"},{"key":"424_CR41","doi-asserted-by":"crossref","unstructured":"Ojameruaye B, Bahsoon R (2021) Sustainability archdebts: an economics-driven approach for evaluating sustainable requirements. Softw Sustain, 369\u2013398","DOI":"10.1007\/978-3-030-69970-3_16"},{"key":"424_CR42","volume-title":"Software architecture in practice","author":"L Bass","year":"2007","unstructured":"Bass L, Clements P, Kazman R (2007) Software architecture in practice. Addison-Wesley Professional, Boston"},{"key":"424_CR43","doi-asserted-by":"publisher","first-page":"1","DOI":"10.1016\/j.infsof.2015.03.007","volume":"64","author":"K Petersen","year":"2015","unstructured":"Petersen K, Vakkalanka S, Kuzniarz L (2015) Guidelines for conducting systematic mapping studies in software engineering: An update. Inf Softw Technol 64:1\u201318","journal-title":"Inf Softw Technol"}],"container-title":["Requirements Engineering"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/link.springer.com\/content\/pdf\/10.1007\/s00766-024-00424-3.pdf","content-type":"application\/pdf","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/link.springer.com\/article\/10.1007\/s00766-024-00424-3\/fulltext.html","content-type":"text\/html","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/link.springer.com\/content\/pdf\/10.1007\/s00766-024-00424-3.pdf","content-type":"application\/pdf","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2024,11,15]],"date-time":"2024-11-15T09:06:25Z","timestamp":1731661585000},"score":1,"resource":{"primary":{"URL":"https:\/\/link.springer.com\/10.1007\/s00766-024-00424-3"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2024,7,6]]},"references-count":43,"journal-issue":{"issue":"4","published-print":{"date-parts":[[2024,12]]}},"alternative-id":["424"],"URL":"https:\/\/doi.org\/10.1007\/s00766-024-00424-3","relation":{},"ISSN":["0947-3602","1432-010X"],"issn-type":[{"value":"0947-3602","type":"print"},{"value":"1432-010X","type":"electronic"}],"subject":[],"published":{"date-parts":[[2024,7,6]]},"assertion":[{"value":"8 December 2023","order":1,"name":"received","label":"Received","group":{"name":"ArticleHistory","label":"Article History"}},{"value":"4 June 2024","order":2,"name":"accepted","label":"Accepted","group":{"name":"ArticleHistory","label":"Article History"}},{"value":"6 July 2024","order":3,"name":"first_online","label":"First Online","group":{"name":"ArticleHistory","label":"Article History"}}]}}