The purpose of Requirements Management is to establish a common understanding between the customer and the software project of the customer's requirements that will be addressed by the software project.
Requirements Management involves establishing and maintaining an agreement with the customer on the requirements for the software project. This agreement is referred to as the "system requirements allocated to the software." The agreement covers both the technical and nontechnical (e.g., delivery dates) requirements.
SSC San Diego projects shall:
1. Control system requirements allocated to software to establish a baseline for software engineering and management use.
2. Keep software plans, products, and activities consistent with the system requirements allocated to software.
3. Establish responsibility for analyzing the system requirements and allocating them to hardware, software, and other system components.
4. Document the allocated requirements.
5. Provide adequate resources and funding for managing the allocated requirements.
6. Train members of the software engineering group and other software-related groups to perform their requirements management activities.
7. Conduct reviews by the software engineering group of the allocated requirements before they are incorporated into the software project.
8. Use the allocated requirements as the basis for software plans, work products, and activities.
9. Review changes to the allocated requirements and incorporate into the software project.
10. Make and use measurements to determine the status of the activities for managing the allocated requirements.
11. Review the activities for managing the allocated requirements with senior management on a periodic basis.
12. Review the activities for managing the allocated requirements with the project manager on both a periodic and event-driven basis.
13. Conduct reviews or audits by the software quality assurance group on the activities and work products for managing the allocated requirements and reports the results.
Software Project Managers are responsible for implementing this policy.
The Software Engineering Process Office (SEPO) is responsible for maintaining this policy.