2018
DOI: 10.1109/ms.2018.3571242
|View full text |Cite
|
Sign up to set email alerts
|

Natural Language Processing for Requirements Engineering: The Best Is Yet to Come

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
51
0
2

Year Published

2018
2018
2021
2021

Publication Types

Select...
5
2
1

Relationship

5
3

Authors

Journals

citations
Cited by 94 publications
(63 citation statements)
references
References 2 publications
0
51
0
2
Order By: Relevance
“…The decision to express requirements in a programming language may bridge the gap. It may also be the only way to bring the developers closer to the requirements they implement: industry practitioners are generally not keen to switching their tools [16]. The advanced state of code reuse has all chances to skyrocket the state of requirements reuse if the requirements take the form of code.…”
Section: Supporting Workmentioning
confidence: 99%
See 1 more Smart Citation
“…The decision to express requirements in a programming language may bridge the gap. It may also be the only way to bring the developers closer to the requirements they implement: industry practitioners are generally not keen to switching their tools [16]. The advanced state of code reuse has all chances to skyrocket the state of requirements reuse if the requirements take the form of code.…”
Section: Supporting Workmentioning
confidence: 99%
“…Natural language processing (NLP) would be an appropriate instrument for implementing these tools [16].…”
Section: Future Workmentioning
confidence: 99%
“…Requirements tend to be redundant due to several concurrent projects and large number of requirements of those projects. Requirements written by several analysts of different projects or different departments of same project are in huge number [6].…”
Section: Nlp For Rementioning
confidence: 99%
“…Identifying method requirements is not an easy task, and the SME literature only provides very generic recommendations. For SUPERSEDE, we propose to use goal models (represented as i* models [20]) as well as the domain knowledge to extract method intentions and to assess context criteria. Indeed, a goal model interconnects the main actors via goal dependencies and allows to derive method intentions from these goals.…”
Section: Example: Requirements Prioritizationmentioning
confidence: 99%