2018
DOI: 10.1002/sys.21461
|View full text |Cite
|
Sign up to set email alerts
|

Automatic requirements extraction, analysis, and graph representation using an approach derived from computational linguistics

Abstract: The quality of requirements is fundamental in engineering projects. Requirements are usually expressed partly or totally in a natural language (NL) format and come from different documents.Their qualities are difficult to analyze manually, especially when hundreds of thousands of them have to be considered. The assistance of software tools is becoming a necessity. In this article, the goal was to develop a set of metrics supported by NL processing (NLP) methods supporting different types of analysis of require… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
7
0
1

Year Published

2019
2019
2024
2024

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 19 publications
(8 citation statements)
references
References 25 publications
0
7
0
1
Order By: Relevance
“…It also classifies requirements for specific purposes that may be useful during software development. Work associated with the classified requirements may be split between different software development teams, with each team assigned a different class of requirements [33].…”
Section: Natural Language Processingmentioning
confidence: 99%
“…It also classifies requirements for specific purposes that may be useful during software development. Work associated with the classified requirements may be split between different software development teams, with each team assigned a different class of requirements [33].…”
Section: Natural Language Processingmentioning
confidence: 99%
“…The use of NLP for requirements engineering has been around for some time. Reference [3] provides a good overview of the state of the art for natural language requirements engineering in 2001, and a more up-to-date (2018) overview can be found in [4].…”
Section: A Previous Contributionsmentioning
confidence: 99%
“…Besides, the two selected papers use different AI techniques and aim to automate two different activities of the design process. In particular, the first paper, presented by Mokammel et al (2018), seeks to automate the generation of a Requirement list. The second paper, presented in Karan and Asadi (2019), has a broader design outcome (i.e.…”
Section: Examples Of Tools Characterize In the Analysismentioning
confidence: 99%
“…To this purpose, the first paper, presented in Mokammel et al (2018), aims to requirement elicitation and treatment thanks to Natural Language processing and to propose a graph representation and clustering of requirements to offer representation allowing to evaluate, to select or to modify the Requirement list As can be seen from Table 3, in general, the level of automation of the Designer-AI Tool interaction presented by the authors is low, except for the "generation" function. In fact, Level 3 is here reached [Designer (Direction) / Computer (Execution)] since the designer has to define the lists of documents to be treated in the analysis.…”
Section: Examples Of Tools Characterize In the Analysismentioning
confidence: 99%