Participants in requirements validation sessions

Participants in requirements validation sessions

Who do I invite to the requirements validation sessions?

    Requires Free Membership to View

    Login

    When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

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.

This was first published in January 2008