Requirements must be validated from two perspectives: 1) Requirements Suppliers; those concerned with requirement...
characteristics such as complete, correct, necessary, and prioritized, and 2) Requirements Receivers; those concerned with requirement characteristics such as modifiable, feasible, traceable, testable and unambiguous.
Generally speaking, separate validation sessions are conducted to satisfy each perspective, and prevent participants from "resolving" identified issues during the review session. Rather, resolution of issues is an elicitation activity, and the necessary participants must be reconsidered. Finally, when in doubt, it is never "too early" to get stakeholders involved.
Dig Deeper on Software Requirements Gathering Techniques
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.