Purpose:
<?>
Objective:
Validate requirements to ensure the resulting product will preform as intended in the end user’s environment.
Description:
Requirements validation is performed early in the development effort with end users to gain confidence that the requirements are capable of guiding a development that results in successful final validation. This activity should be integrated with risk management activities. Mature organizations will typically perform requirements validation in a more sophisticated way using multiple techniques and will broaden the basis of the validation to include other stakeholder needs and expectations.
Examples of techniques used for requirements validation include the following:
- Analysis
- Simulations
- Prototyping
- Demonstrations
Inputs:
<?>
Outputs:
<?>
Controls:
<?>
Task Instructions:
Ensure Review of Customer Requirements Document
- Using the Updated Customer Requirements Document, Draft Requirements Traceability Matrix and Formal Peer Review [the Business Analyst] is responsible for ensuring that the Customer Requirements Document is reviewed to verify if the Customer Requirements have been captured completely and accurately.
Obtain Approval and Baseline Customer Requirements Document
- Using the [?], [the Business Analyst] with support from the Project Manager is responsible for sending the Customer Requirements Document to the Product Owner, Business Project Champion, System Engineer to obtain their approval to baseline the Customer Requirements Document.
- Using the [?], [the Business Analyst] with support from the Project Manager is responsible for ensuring that all the action items are closed before formal baseline of the Customer Requirements Document.
- Using the [?], [the Business Analyst] is responsible for communicating the Customer Requirements document baseline to the Requirements Providers, Business Project Champion, Lead Architect, Senior Manager, System Deployment Manager, QA Analyst, and to the Project Team.
