Version 1.1 - 10/9/97

The purpose of Software Quality Management is to develop a quantitative understanding of the quality of each project's software products and achieve specific quality goals.

Software Quality Management involves defining quality goals for the software products, establishing plans to achieve these goals, and monitoring and adjusting the software plans, software work products, activities, and quality goals to satisfy the needs and desires of the customer and end user for high quality products.

The practices of Software Quality Management build on the practices of Integrated Software Management and Software Product Engineering, which establish and implement the project's defined software process, and Quantitative Process Management, which establishes a quantitative understanding of the ability of each project's defined software process to achieve the desired results.

SSC San Diego shall:

1. Plan each project's software quality management activities.
2. Define measurable goals for software product quality and their priorities.
3. Ensure actual progress toward achieving the quality goals for the software products is quantified and managed.
4. Provide adequate resources and funding for managing the quality of the software products.
5. Require training for the individuals implementing and supporting software quality management in the performance of their activities.
6. Require training for the members of the software engineering group and other software-related groups in software quality management.
7. Develop and maintain each project's software quality plan according to a documented procedure.
8. Ensure that each project's software quality plan is the basis for the project's activities for software quality management.
9. Ensure that each project's quantitative quality goals for the software products are defined, monitored, and revised throughout the software life cycle.
10. Ensure that the quality of each project's software products is measured, analyzed, and compared to the products' quantitative quality goals on an event-driven basis.
11. Allocate appropriately each software project's quantitative quality goals for the products to the subcontractors delivering software products to the project.
12. Make and use measurements to determine the status of the software quality management activities.
13. Review the activities for software quality management with senior management on a periodic basis.
14. Review the activities for software quality management with the project manager on both a periodic and event-driven basis.
15. Conduct reviews or audits by the software quality assurance group the activities and work products for software quality management and reports the results.