IBM Rational has incorporated some of the best practices above into Rational Requirements Composer: project transparency, various methods to capture requirements, web review and validation, linking requirements to work items and test cases.
For another perspective on this topic, read the white paper in the business analysis e-kit: Getting your requirements right: Collaborate with stakeholders to work smarter What else have you experienced that works (or doesn’t)?
Prototyping is generally used to test validity and completeness of the requirements.
Having your customers develop acceptance criteria is one of the most important methods of validating requirements.
If they are not happy with the product, your time and money is wasted.
Just watch a requirements validation meeting when customers are present. Often the organization doesn’t want to include customers for fear they will divulge confidential information. IBM Rational has both extensive beta programs and design partner programs.
The feedback we’ve gotten through these programs greatly enhances the solutions we produce.
I’ve listed below several different practices for validating requirements and some pros and cons of each.