State-of-art practices to detect inconsistencies and ambiguities from software requirements

An acceptable solution is built only if the problem space is correctly defined, which is the prime reason to perform a Requirement Engineering process before the development of the project. Requirement Engineering is the most important phase of a software development and holds the ability to affect the entire software development actions if improperly implemented. However, the requirement engineering process faces many problems. Two major problems are inconsistencies and ambiguities, since requirements are elicited from multiple stakeholders and are specified in natural language in SRS. Consequently, the problems should be resolved timely so that it does not move to the next phase of software development process. The purpose of the study is to review and discuss some of the existing techniques to detect inconsistencies and ambiguities in software requirements. Later observations on the existing work are also discussed and a framework for the same is also suggested.