Techniques for validating requirements
Investing in requirements quality always saves you more money than you spend.Test Thinking On many projects, testing is a late-stage activity.
Developers and testers can examine requirements to assess whether they understand each one well enough to do their part of the project work based on that requirement.
This prevents them from doing further damage and reduces your testing and maintenance costs.
Figure 1 illustrates the V model of software development, which shows test activities beginning in parallel with the corresponding development activities.
Intuitively, it seems that inserting time into the schedule to improve requirements quality would delay the planned ship date by that same duration.
However, this expectation assumes a zero return on your investment in requirements validation.