2020 IEEE International Conference on Software Maintenance and Evolution (ICSME) 2020
DOI: 10.1109/icsme46990.2020.00067
|View full text |Cite
|
Sign up to set email alerts
|

Score-Based Automatic Detection and Resolution of Syntactic Ambiguity in Natural Language Requirements

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
13
0
1

Year Published

2021
2021
2023
2023

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 18 publications
(14 citation statements)
references
References 20 publications
0
13
0
1
Order By: Relevance
“…--Syntactic Ambiguity: This level focuses on detecting sentences that have different possible grammatical structures. We recognized one paper handling this level of ambiguity (Osama et al [108]). --Semantic Ambiguity: This level focuses on detecting confusing contexts in sentences such as anaphoric ambiguity and coordination ambiguity.…”
Section: ) Requirements Extractionmentioning
confidence: 99%
“…--Syntactic Ambiguity: This level focuses on detecting sentences that have different possible grammatical structures. We recognized one paper handling this level of ambiguity (Osama et al [108]). --Semantic Ambiguity: This level focuses on detecting confusing contexts in sentences such as anaphoric ambiguity and coordination ambiguity.…”
Section: ) Requirements Extractionmentioning
confidence: 99%
“…-Syntactic Ambiguity: This level focuses on detecting sentences that have different possible grammatical structures. We recognized one paper handling this level of ambiguity (Osama et al [108]).…”
Section: Quality Assessmentmentioning
confidence: 99%
“…Ambiguity is a persistent issue in NL requirements. Hence, such ambiguity has been extensively studied in the literature [17,18,19,11,20]. For example, recently, Ezzini et al [20] proposed six alternative solutions for automating the handling of anaphoric ambiguity in requirements.…”
Section: Related Workmentioning
confidence: 99%
“…For example, analysts sometimes describe multiple functions in a single requirement (i.e., non-atomic requirement), miss essential words (e.g., actors and verbs) or even phrases (e.g., system responses), or write a requirement following an ambiguous structure (e.g., a system response between conditions). We note that some of these quality problems have been studied individually in many prior works, such as checking the completeness [12,13,14,15,16] or ambiguity [17,18,19,11,20] of requirements. However, compared to these research strands, there has been relatively less focus on developing an automated solution that can both detect and resolve multiple quality problems in a requirement.…”
Section: Introductionmentioning
confidence: 99%