Product Type: Market Research Report
Published by: Ovum Plc
Published: September 2007
Product Code: R464-627Description Errors in requirements are a major source of waste in IT. There have been attempts to reduce the problem, but until recently they have suffered from being dispersed and unco-ordinated across the lifecycle. As enterprises become increasingly interested in cross-discipline application lifecycle management (ALM) solutions, requirements-based testing re-emerges to address the problem in an integrated way. It combines methods from requirements engineering and software testing into an orchestrated set of quality assurance activities and management tools that focus on getting the requirements right from the outset, managing inevitable change and discovering requirements errors before they become extremely costly to fix.
Table of Contents - Key messages
- Requirements back in the spotlight
- The most numerous and costly errors to fix
- A resurgence of interest
- Not all testing is requirements based
- Higher consciousness of requirements
- The trouble with requirements
- Where and how do we go wrong with requirements?
- The innate problem of defining complete requirements
- A clash of two disparate perspectives
- How to do requirements-based testing
- Activities
- Practices
- Objectives
- Quality assuring the requirements
- Establish testability, test requirements and derive test cases
- Measure requirements coverage
- Automation
- Pitfalls
|
|
