RECOVER: Toward Requirements Generation From Stakeholders’ Conversations
- 21 May 2025
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 51 (6) , 1912-1933
Abstract
Stakeholders’ conversations in requirements elicitation meetings hold valuable insights into system and client needs. However, manually extracting requirements is time-consuming, labor-intensive, and prone to errors and biases. While current state-of-the-art methods assist in summarizing stakeholder conversations and classifying requirements based on their nature, there is a noticeable lack of approaches capable of both identifying requirements within these conversations and generating corresponding system requirements. These approaches would assist requirement identification, reducing engineers’ workload, time, and effort. They would also enhance accuracy and consistency in documentation, providing a reliable foundation for further analysis. To address this gap, this paper introduces RECOVER (Requirements EliCitation frOm conVERsations), a novel conversational requirements engineering approach that leverages natural language processing and large language models (LLMs) to support practitioners in automatically extracting system requirements from stakeholder interactions by analyzing individual conversation turns. The approach is evaluated using a mixed-method research design that combines statistical performance analysis with a user study involving requirements engineers, targeting two levels of granularity. First, at the conversation turn level, the evaluation measures RECOVER’s accuracy in identifying requirements-relevant dialogue and the quality of generated requirements in terms of correctness, completeness, and actionability. Second, at the entire conversation level, the evaluation assesses the overall usefulness and effectiveness of RECOVER in synthesizing comprehensive system requirements from full stakeholder discussions. Empirical evaluation of RECOVER shows promising performance, with generated requirements demonstrating satisfactory correctness, completeness, and actionability. The results also highlight the potential of automating requirements elicitation from conversations as an aid that enhances efficiency while maintaining human oversight.Keywords
All Related Versions
This publication has 36 references indexed in Scilit:
- Summarization of Elicitation Conversations to Locate Requirements-Relevant Information2023
- Extracting Software Requirements from Unstructured Documents2022
- Requirements Elicitation via Fit-Gap Analysis: A View Through the Grounded Theory Lens2021
- Alignment and granularity of requirements and architecture in agile development: A functional perspectiveInformation and Software Technology, 2021
- On deriving conceptual models from user requirements: An empirical studyInformation and Software Technology, 2021
- Extracting Declarative Process Models from Natural Language2019
- Interview Review: An Empirical Study on Detecting Ambiguities in Requirements Elicitation Interviews2018
- Ambiguity and tacit knowledge in requirements elicitation interviewsRequirements Engineering, 2016
- System requirements engineering in complex situationsRequirements Engineering, 2012
- Requirements Elicitation: A Survey of Techniques, Approaches, and Tools2006