2008
DOI: 10.1007/s00766-008-0063-7
|View full text |Cite
|
Sign up to set email alerts
|

Requirements for tools for ambiguity identification and measurement in natural language requirements specifications

Abstract: This paper proposes a two-step approach to identifying ambiguities in natural language (NL) requirements specifications (RSs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
59
1

Year Published

2015
2015
2019
2019

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 104 publications
(63 citation statements)
references
References 25 publications
0
59
1
Order By: Relevance
“…It depends both on the imprecision of words and grammatical constructions or context [55]. Moreover, lack of precision, as in the sentence "corrective action should be started as soon as possible", may even occur in not totally accurate quality documents.…”
Section: Quality and Informationmentioning
confidence: 99%
See 1 more Smart Citation
“…It depends both on the imprecision of words and grammatical constructions or context [55]. Moreover, lack of precision, as in the sentence "corrective action should be started as soon as possible", may even occur in not totally accurate quality documents.…”
Section: Quality and Informationmentioning
confidence: 99%
“…Moreover, lack of precision, as in the sentence "corrective action should be started as soon as possible", may even occur in not totally accurate quality documents. Therefore, in order to decrease the level of uncertainty, it is important firstly to scrutinise QMS documents for ambiguity, "manually" or, better, with the help of dedicated software, capable of identifying and indexing ambiguities [55,56].…”
Section: Quality and Informationmentioning
confidence: 99%
“…Additionally, some researchers have attempted to tackle implicit requirements by resolving ambiguity in requirements specifications. Instances of these include [19,20,21,22]. However, so far in the literature, there are not many empirical studies that focussed specifically on the issue of implicit requirements within software organisations.…”
Section: Related Workmentioning
confidence: 99%
“…These include [3,12,13,14], which considered how to identify and handle IMR. The works in [8,15,16,17,18] focussed on dealing with tacit/implicit knowledge in requirements; while [9,19,20,21,22] dealt with handling ambiguity in requirements.…”
Section: Introductionmentioning
confidence: 99%
“…Few articles broach the topic of contradictions in natural language [7,10]. However, much research attempts to diagnose quality defects by using NLP and text mining techniques [11][12][13][14][15][16][17]. Recent work has been done to classify requirements thanks to machine learning [18] or linguistics analysis [16].…”
Section: Related Workmentioning
confidence: 99%