A Method to Deal with the Type of Lexical Ambiguity in a Software Requirement Specification Document

SRS is the agreement between the client and the developer, it is a document which specifies the clientpsilas requirement and also validates the final product. In various surveys it was found that approximately 20-25% of the project time is allocated for the requirements definition and major part of...

Full description

Saved in:
Bibliographic Details
Published in2008 First International Conference on Emerging Trends in Engineering and Technology pp. 1212 - 1215
Main Authors Beg, R., Abbas, Q., Joshi, A.
Format Conference Proceeding
LanguageEnglish
Published IEEE 01.07.2008
Subjects
Ambiguity
Data mining
Data structures
Dictionaries
Formal Languages
Heteronyms and Homographs
Homonyms
Lexical Ambiguity
Natural languages
Requirement Engineering
Software
Software engineering
Software Requirement Specification
Speech
Online AccessGet full text

Cover

More Information
Summary:SRS is the agreement between the client and the developer, it is a document which specifies the clientpsilas requirement and also validates the final product. In various surveys it was found that approximately 20-25% of the project time is allocated for the requirements definition and major part of its time is wasted in making the requirement specification unambiguous, to avoid the conflict in future. Conflict arises because of more than one interpretation of a requirement, this lead to misinterpretation of design constraints, functionality, and external interfaces or in any further enhancements. In our proposed system requirements are documented in natural language. The system checks whether the written requirements are valid requirements or not and also checks for the lexical type of ambiguities, especially the ambiguity related to homonyms, heteronyms and homographs.
ISSN:2157-0477
2157-0485
DOI:10.1109/ICETET.2008.160