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.
It can also be the most time consuming as it generally involves all the stakeholder representatives. This means that this process is iterative and may go through a few iterations before all the issues are resolved.
Prototyping – One of the most effective ways to ensure that the developers are on the same page as the users.
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.
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.These are just some of the practices that are important to employ in validating requirements.Using these will help any development methodology be more effective in practice.You would most likely use different techniques to validate rich text documents vs. The really good thing about Composer, though, is that with a central repository, a project dashboard, and collaborative platform, both general and very granular feedback can be provided by stakeholders – including external customers if they have been given access.6) Hold facilitated use case workshops – Use case workshops can be incredibly effective if you have the right participants and people are fully engaged.They will help capture those high quality requirements that ensure delivery of the right product to customers.