A Method to Deal with the Type of Lexical Ambiguity in a Software Requirement Specification Document
Rizwan Beg, Qamar Abbas, Alok Joshi · 2008
SRS is the agreement between the client and the developer, it is a document which specifies the client’s 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.