Methods for validating requirements
By watching users, a process flow, pain points, awkward steps and opportunities can be determined by an analyst for improvement. Passive observation is provides better feedback to refine requirements on the same hand active observation works best for obtaining an understanding over an existing business process.
You can use any of these approaches to uncover the implicit requirements that are often overlooked.
Popularly known as JAD or joint application design, these workshops can be efficient for gathering requirements.
The requirements workshops are more organized and structured than a brainstorming session where the involved parties get together to document requirements.
Prototyping can be very helpful at gathering feedback.
Low fidelity prototypes make a good listening tool.
Chunks of information are mostly buried in present documents that assist you in putting questions as a part of validating the requirement completeness.Techniques involving visualization of the requirements like storyboards, prototypes, scenarios are helpful when you have a business user who may not be worried about the ins and outs of technical solution or have long attention duration for legalizing the requirements with users to let the analyst drive his discovery efficiently than just reading a document with a prospective user.