Extracting Software Requirements from Unstructured Documents
Not on the map. Why?
Abstract (arXiv)
Requirements identification in textual documents or extraction is a tedious and error prone task that many researchers suggest automating. We manually annotated the PURE dataset and thus created a new one containing both requirements and non-requirements. Using this dataset, we fine-tuned the BERT model and compare the results with several baselines such as fastText and ELMo. In order to evaluate the model on semantically more complex documents we compare the PURE dataset results with experiments on Request For Information (RFI) documents. The RFIs often include software requirements, but in a less standardized way. The fine-tuned BERT showed promising results on PURE dataset on the binary sentence classification task. Comparing with previous and recent studies dealing with constrained inputs, our approach demonstrates high performance in terms of precision and recall metrics, while being agnostic to the unstructured textual input.
Key facts. Cited by 3 papers in the map (data through 14 Oct 2026). First posted on arXiv 4 Feb 2022.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2024: 1; 2025: 2.
3 papers.
- 2024Generative Language Models Potential for Requirement Engineering Applications: Insights into Current Strengths and Limitationscited by 0
- 2025ReqBrain: Task-Specific Instruction Tuning of LLMs for AI-Assisted Requirements Generationcited by 0
- 2025Generating Privacy Stories From Software Documentationcited by 0
- 2025Generating Privacy Stories From Software Documentation28 Jun 2025
- 2025ReqBrain: Task-Specific Instruction Tuning of LLMs for AI-Assisted Requirements Generation23 May 2025
- 2024Generative Language Models Potential for Requirement Engineering Applications: Insights into Current Strengths and Limitations1 Dec 2024