Measurable and Testable Requirements

A stitch in time saves nine says a proverb. It explains a lot about the cost of fixing the bugs in software development. The cost of fixing an error is lowest in the first phase of software development i.e., requirements. This is because there are very few deliverables at the beginning of a project to correct if an error is found. As the project moves into subsequent phases of software development, the cost of fixing an error rises dramatically since there are more deliverables affected by the correction of each error. Of the bugs rooted in requirements, many are due to poorly written, ambiguous, unclear, and incorrect requirements.