Abstract Requirements Ambiguity Testing

Whitepaper – Requirements Ambiguity Testing ABSTRACT The Standish Group and other studies show that the top four reasons why software projects fail due to Incomplete Requirements and Specifications, Changing Requirements and Specifications, Unclear Project Objectives and Lack of user input to requirements. In most software projects, the importance of testing 'Requirement specifications' is often ignored. According to Standish group, the most common reason for failures in software projects is due to defects in the requirements phase. Failing to test requirements in the inception phase results in costly deviations in the final product and also has severe impact on the development life cycle. Project schedules are stretched, deliverables are delayed, costs are overrun and the customer takes the hit. Incorporating testing activities right from project inception minimizes the impact on the project and saves precious time and resources. Requirements must be clearly specified, completely described and unambiguously defined. Several techniques are available to test the requirements. One such technique is 'Ambiguity Testing' and is implemented at the inception phase of requirement gathering. Scope This white paper: • describes the critical need for testing requirements • explains the characteristics of poor and testable requirements • elaborates the process of Ambiguity testing to achieve testable requirements. Read the whitepaper at: http://www.allianceglobalservices.com/white‐paper/whitepaper‐requirements‐ambiguity‐testing ©Alliance Global Services 2009 Page 1

Abstract Requirements Ambiguity Testing

by Alliance Global Services on Dec 19, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

Abstract Requirements Ambiguity Testing — Document Transcript