SQA Plan Template
TM-SQA-01 v2.0
12/16/03
SOFTWARE QUALITY ASSURANCE PLAN
TEMPLATE
TM-SQA-01 V2.0
DECEMBER 16, 2003
Systems Engineering Process Office, Code 212
Space and Naval Warfare Systems Center San Diego
53560 Hull Street
San Diego, CA 92152-5001
Approved for public release; distribution is unlimited
SQA Plan Template
TM-SQA-01 v2.0
12/16/03
ii
PREFACE
This document is a template of a Software Quality Assurance (SQA) Plan using the guidelines provided
in 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 Assurance
Planning. 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. The
planning 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
comply with 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 the products 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 Diego Systems 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 from users 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 using the 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 the SEPO Configuration
Management Procedure available on the SSC San Diego PAL.
SQA Plan Template
TM-SQA-01 v2.0
12/16/03
iii
DOCUMENT CHANGE REQUEST (DCR)
Document Title: Software Quality Assurance Plan Template
Tracking Number:
Name of Submitting Organization:
Organization Contact:
Phone:
Mailing Address:
Short Title:
Date:
Change Location:
(use section #, figure #, table #, etc.)
Proposed change:
Rational for Change:
Note: For the Systems Engineering Process Office (SEPO) to take appropriate action on a change request,
please provide a clear description of the recommended change along with supporting rationale.
Send to: Commanding Officer, Space and Naval Warfare Systems Center, Code 212, 53560 Hull Street,
San Diego, CA 92152-5001
Fax: (619) 553-6249
Email: sepo@spawar.navy.mil
Submit online: http://sepo.spawar.navy.mil/
DCR Form 9/2002
SQA Plan Template
TM-SQA-01 v2.0
12/16/03
iv
RECORD OF CHANGES
*A - ADDED M - MODIFIED D - DELETED
VERSION
NUMBER
DATE
NUMBER OF
FIGURE, TABLE OR
PARAGRAPH
A*
M
D
TITLE OR BRIEF DESCRIPTION
CHANGE
REQUEST
NUMBER
1.3
1/25/00
Entire Document
Updated Template to include checklists
for general Software Engineering Process
Verification (Appendix B) and focused
CMM Key Process Area Verification
(Appendix C)
2.0
12/16/03
Entire Document
Revised Task definitions and reorganized
them into a separate section; incorporated
changes from DCR #SQAPT-003;
removed SW-CMM Key Process Area
validation process and checklists (to be
documented as a separate document –
addressing CMMI verification); added an
“escalation procedure” to Section 7 for
resolution of non-concurrence of SQA
recommendations
SQAPT-
003
SQA-0001
SQA Plan Template
TM-SQA-01 v2.0
12/16/03
v
DOCUMENT CONVENTIONS
This document is a Software Quality Assurance (SQA) Plan template. As such, wording in this document
should be supplemented with project-specific information to produce an SQA Plan that accurately
describes the project SQA organization. Therefore, tailor (add, delete, change, or expand) the information
provided in this document
Standard conventions are used within this document to direct the reader to specific sections of the text.
These sections provide instructions and explanations and require users to substitute their own department-
specific information for the generic information provided or to "fill in a blank."
[[text]] Global changes. Items that appear in regular text and are surrounded by double brackets
represent changes that can be made globally throughout the document.
Italics Instructions and explanations. Items that appear in italics represent instructions to the user
and are not to appear in the completed version of the document.
In some cases where information may already be found in another project document, like the Software
Development Plan (SDP), refer to that document rather than duplicate the information in the project SQA
Plan.
The template begins with the Project SQA cover sheet on the page after the next. Delete all pages prior to
the Project SQA cover sheet in the final format of the project SQA Plan. Update the header page to
reflect the document configuration identifier for the project SQA Plan.
