2014 IEEE 27th Canadian Conference on Electrical and Computer Engineering (CCECE) 2014
DOI: 10.1109/ccece.2014.6900955
|View full text |Cite
|
Sign up to set email alerts
|

Semi-automation for ambiguity resolution in Open Source Software requirements

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
4
3
1
1

Relationship

0
9

Authors

Journals

citations
Cited by 11 publications
(6 citation statements)
references
References 18 publications
0
6
0
Order By: Relevance
“…Thus, requirements engineers have to go through these reports, discriminate users' intents and decide on whether to accept or reject. However, such process of understanding, classifying and clarifying end users' enhancement reports becomes a tedious and labor-intensive task, even for experienced requirements engineers 27 .…”
Section: Overviewmentioning
confidence: 99%
“…Thus, requirements engineers have to go through these reports, discriminate users' intents and decide on whether to accept or reject. However, such process of understanding, classifying and clarifying end users' enhancement reports becomes a tedious and labor-intensive task, even for experienced requirements engineers 27 .…”
Section: Overviewmentioning
confidence: 99%
“…The authors propose the detection and resolution of ambiguity problems before documenting, through the adoption of natural language processing (NLP), the semantic web technique and the measurement of the similarity between requirements.  S14 - Gill et al (2014) Requirements": This research proposes the implementation of an ontologybased intelligent agent (OBIA) in order to determine metric information in software requirements. Some of the actions permitted by the intelligent agent are: Partially deleting the person from the information processing processes, avoiding the loss of information and enhancing the quantity of metric information in the requirements recompilation phase, or improving software quality.…”
Section: Extraction Of Informationmentioning
confidence: 99%
“…An example of ambiguity correction is the work of Gill et al [9], who proposed a framework to develop semi-automatic tools for ambiguity correction in open source software requirements. They discussed some challenges in open source requirements that make it a special case.…”
Section: Ambiguity Correctionmentioning
confidence: 99%
“… Ambiguity correction: refers to semi-automated tools that interact with the user to make the needed corrections such as the work of Gill et al [9].…”
Section: Introductionmentioning
confidence: 99%