1. Software Quality Management Plan
By: Coredrees Lindsey

2. Quality Management Plan
Purpose:
The quality management plan shows guidance on how quality management will be ensured on the project.
It will be ensured through design reviews, documentation, and others protocols.
It gives management and the customer a clear understanding of how quality will be maintained and what documentation they can expect addressing quality during the life of the project.

3. Quality Policy
Normally defined in general terms or by referring to other documents, the quality policy expresses the project or the support organization's attitude toward quality and quality practices.

4. Quality Approach
The quality approach often includes extensive reference documentation that supports the quality plan. This includes the documents needed to validate deliverable performance. It will also outline how specific practices such as design reviews and records management will be carried out.

5. Supporting Documentation
For some information incorporated in the quality approach documentation, such as flow charts and external reference, copies (or direction to copies) may be embedded as appendices or in supplemental folders.

6. Key Approaches Quality Management Plan in a one or two-paged document.
Develop and maintain the project software quality assurance plan.
Identify lessons learned that could improve process for future products

7. Quality Control Plan
Example

8. Control Plan
A Control Plan is used to document and commutate the initial plan for process control.
Also, a Control Plan describes the actions required at each step in the process to assure that all process outputs will be in a state of control.

9. Safety Personnel
Provide system software safely expertise to the (SQ) Software safely to the SQ personnel and/or project personnel as required.
Assist in the resolution of any software safety related issues, concerns, and/ or risks identified throughout the project life cycle.

10. Test
The test management processes and products are begins implemented per software management plan and/or test plans. This includes all types of integration testing (verification) and acceptance testing (validation).

11. References
This PowerPoint contained of info from the following websites:
Google
Wikipedia
Yahoo

12. Questions
??????