DECEMBER 16, 2003
Systems Engineering Process Office, Code 212
Space and Naval Warfare Systems Center San Diego
53560 Hull StreetSan Diego, CA 92152-5001
Approved for public release; distribution is unlimited
THIS DOCUMENT IS A TEMPLATE OF A SOFTWARE QUALITY ASSURANCE (SQA) PLAN USING THE GUIDELINES PROVIDEDIN THE INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE) 730-1998, IEEE STANDARD FOR SOFTWARE QUALITY ASSURANCE PLANS, AND IEEE STD 730.1-1995, IEEE GUIDE FOR SOFTWARE QUALITY ASSURANCEPLANNING. THIS TEMPLATE SHOULD BE SUPPLEMENTED WITH PROJECT-SPECIFIC INFORMATION TO PRODUCE A SQA PLAN THAT ACCURATELY DESCRIBES THE PROJECT’S SQA ORGANIZATION, TASKS, ROLE, AND RESPONSIBILITIES. THEPLANNING AND DOCUMENTING OF SQA ACTIVITIES MUST AGREE AND BE CONSISTENT WITH THE PROJECT’S SOFTWARE DEVELOPMENT PLAN (SDP) AND ANY OTHER PROJECT-PLANNING DOCUMENT. ADDITIONALLY, THE SQA PLAN MUST COMPLYWITH SPACE AND NAVAL WARFARE (SPAWAR) SYSTEMS CENTER (SSC) SAN DIEGO SQA POLICY, WHICH PROVIDES MANAGEMENT WITH APPROPRIATE VISIBILITY INTO THE PROCESS BEING USED BY THE SOFTWARE PROJECT AND OF THEPRODUCTS BEING BUILT.
This document supplements the SQA Process. Refer to Section 4, Create/Maintain SQA Plan, of the SQA Process for a description on the use of this template.
The SSC San DiegoSystems Engineering Process Office (SEPO) assumes responsibility for this document and updates it as required to meet the needs of users within SSC San Diego CA. SEPO welcomes and solicits feedback fromusers of this document so that future revisions will reflect improvements, based on organizational experience and lessons learned.
Users of this document may report deficiencies or corrections usingthe Document Change Request (DCR) found on the next page or online through the SSC San Diego Process Asset Library (PAL) at http://sepo.spawar.navy.mil/. Updates are performed in accordance with...