RECOVER: Toward Requirements Generation from Stakeholders' Conversations
Not on the map. Why?
Abstract (arXiv)
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. 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. The approach is evaluated using a mixed-method study that combines 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
Key facts. Cited by 6 papers in the map (data through 13 Oct 2026). First posted on arXiv 29 Nov 2024.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2025: 4; 2026: 2.
6 papers.
- 2025Automated Non-Functional Requirements Generation in Software Engineering with Large Language Models: A Comparative Studycited by 3
- 2025A Blueprint for AI-Driven Software Quality: Integrating LLMs with Established Standardscited by 1
- 2026Tracing Stereotypes in Pre-trained Transformers: From Biased Neurons to Fairer Modelscited by 1
- 2025SEER: Sustainability Enhanced Engineering of Software Requirementscited by 0
- 2025An Empirical Study of Sample Selection Strategies for Large Language Model Repaircited by 0
- 2026From Chat to Interview: Agentic Requirements Elicitation with an Experience Ontologycited by 0
- 2026From Chat to Interview: Agentic Requirements Elicitation with an Experience Ontology7 May 2026
- 2026Tracing Stereotypes in Pre-trained Transformers: From Biased Neurons to Fairer Models9 Jan 2026
- 2025An Empirical Study of Sample Selection Strategies for Large Language Model Repair23 Oct 2025
- 2025SEER: Sustainability Enhanced Engineering of Software Requirements10 Oct 2025
- 2025A Blueprint for AI-Driven Software Quality: Integrating LLMs with Established Standards19 May 2025
- 2025Automated Non-Functional Requirements Generation in Software Engineering with Large Language Models: A Comparative Study19 Mar 2025