 |
Activity:
Validate Requirements (CMMI Level 3 : RD 3.5 )
 |
|
Participating Roles
Accountable:
Subject Matter Expert |
Validate that the product requirements, as written, are the proper requirements to produce the intended functionality. This validation is done from the customer's point of view. Validating the product requirements prior to development is intended to reduce the amount of wasted effort and limit the amount of functionality change requests during the project.
Entry Criteria
When:
- After product requirements are baselined.
Dependencies:
- Functional Requirements Baselined: The functional requirements are reviewed, approved, and baselined.
- Interface Requirements Baselined: The interface requirements are reviewed, approved, and baselined.
- Security Requirements Baselined: The security requirements are reviewed, approved, and baselined.
- Safety Requirements Baselined: The safety requirements are reviewed, approved, and baselined.
- Operational Requirements Baselined: The operational requirements are reviewed, approved, and baselined.
Sub-Activities
|
|
1 |
Review Product Requirements |
- Hold a validation review meeting to discuss the product requirements with pertinent stakeholders. Determine if the product requirements are the proper ones to produce the intended functionality. If not, determine what needs to be modified, added, or removed.
|
|
2 |
Revise Product Requirements |
- Revise the product requirements based on feedback from the review meeting.
|
|
3 |
Approve Product Requirements |
- Once all issues have been addressed and verified, approve the product requirements.
|
Exit Criteria
 |
The product requirements, as specified, are validated. | |
 |
Program Management
