2013 20th Asia-Pacific Software Engineering Conference (APSEC) 2013
DOI: 10.1109/apsec.2013.41
|View full text |Cite
|
Sign up to set email alerts
|

Entity Disambiguation in Natural Language Text 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

2014
2014
2022
2022

Publication Types

Select...
4
3

Relationship

1
6

Authors

Journals

citations
Cited by 7 publications
(6 citation statements)
references
References 20 publications
0
6
0
Order By: Relevance
“…--Lexical Ambiguity: The main focus at this level is the ambiguity caused by words and terms. We recognized 6 papers related to this level [10], [93], [104]- [107]. --Syntactic Ambiguity: This level focuses on detecting sentences that have different possible grammatical structures.…”
Section: ) Requirements Extractionmentioning
confidence: 99%
“…--Lexical Ambiguity: The main focus at this level is the ambiguity caused by words and terms. We recognized 6 papers related to this level [10], [93], [104]- [107]. --Syntactic Ambiguity: This level focuses on detecting sentences that have different possible grammatical structures.…”
Section: ) Requirements Extractionmentioning
confidence: 99%
“…-Lexical Ambiguity: The main focus at this level is the ambiguity caused by words and terms. We recognized 6 papers related to this level [93,104,105,106,10,107].…”
Section: Quality Assessmentmentioning
confidence: 99%
“…Then, each requirement is represented as a vector representation in this k-dimensional space. In most related papers, this representation is employed to calculate the similarity between requirements as a part of similarity-based rules [70,107] or clustering machine learning techniques [135,99,78].…”
Section: Topic Modeling Based Representationsmentioning
confidence: 99%
“…Requirements are assumed to be free from linguistic errors as well as terminological ambiguities [25], else quality of the final outputs may be lower, which for example, depends upon the identification of entity and action terms. It is further assumed that requirements correctly express the intention of its writer else errors in the estimation of semantic associations among requirements might increase.…”
Section: Inputsmentioning
confidence: 99%