Software Quality Assurance Plan
(SQAP)
Document Number: [nn]
Date: Day, Month Day, Year
[Project Name]
[Author 1]
[Author 2 - if none, leave blank line]
[Author 3 - if none, leave blank line]
[Author 4 - if none, leave blank line]
Professor [Name]
Software Engineering Department
Monmouth University
West Long Branch, NJ 07764-1898
Software Quality Assurance Plan (SQAP)
[Project Name]
Table of Contents
3
1 SCOPE 4
1.1 IDENTIFICATION 4
1.2 SYSTEM OVERVIEW 5
1.3 DOCUMENT OVERVIEW 7
2 REFERENCED DOCUMENTS 8
3 CURRENT SYSTEM OR SITUATION 9
3.1 BACKGROUND, OBJECTIVES, AND SCOPE 9
3.2 OPERATIONAL POLICIES AND CONSTRAINTS 9
3.3 FUNCTIONAL RESPONSIBILITIES 9
3.4 USERS OR INVOLVED PERSONNEL 10
3.4.1 PROGRAM MANAGEMENT (SPONSOR) IS RESPONSIBLE FOR: 10
3.4.2 PROJECT MANAGEMENT IS RESPONSIBLE FOR: 10
3.4.3 SYSTEM ENGINEERING IS RESPONSIBLE FOR: 11
3.4.4 SOFTWARE DESIGN/DEVELOPMENT IS RESPONSIBLE FOR: 11
3.4.5 SOFTWARE TEST IS RESPONSIBLE FOR: 12
3.4.6 SYSTEM TEST IS RESPONSIBLE FOR: 12
3.4.7 LOGISTICS IS RESPONSIBLE FOR: 12
3.4.8 SOFTWARE CONFIGURATION MANAGEMENT (SCM) IS RESPONSIBLE FOR: 12
3.4.9 INDEPENDENT VERIFICATION AND VALIDATION (IV&V) IS RESPONSIBLE FOR: 13
3.4.10 SOFTWARE ENGINEERING PROCESS OFFICE IS RESPONSIBLE FOR: 13
3.5 SUPPORT CONCEPT 13
4 SQA TASKS 14
4.1 REVIEW SOFTWARE PRODUCTS 14
4.2 EVALUATE SOFTWARE TOOLS 14
4.3 EVALUATE FACILITIES 15
4.4 EVALUATE SOFTWARE PRODUCTS REVIEW PROCESS 15
Page 2 of 33 Pages
Software Quality Assurance Plan (SQAP)
[Project Name]
4.5 EVALUATE PROJECT PLANNING AND OVERSIGHT PROCESS 16
4.6 EVALUATE SYSTEM REQUIREMENTS ANALYSIS PROCESS 16
4.7 EVALUATE SYSTEM DESIGN PROCESS 18
4.8 EVALUATE SOFTWARE DESIGN PROCESS 19
4.9 EVALUATE CODING AND UNIT TESTING PROCESS 20
4.10 EVALUATE UNIT INTEGRATION AND TESTING AND SYSTEM QUALIFICATION TESTING
21
4.11 EVALUATE END-ITEM DELIVERY 23
4.12 EVALUATE THE CORRECTIVE ACTION PROCESS 24
4.13 NON-DELIVERABLE SOFTWARE CERTIFICATION 25
4.14 EVALUATE STORAGE AND HANDLING PROCESS 25
4.15 EVALUATE SUBCONTRACTOR CONTROL 26
4.16 EVALUATE CONFIGURATION MANAGEMENT PROCESS 26
4.17 EVALUATE SOFTWARE DEVELOPMENT LIBRARY CONTROL PROCESS 27
4.18 PERFORM CONFIGURATION AUDITS 28
4.19 VERIFYING IMPLEMENTATION OF REQUIREMENTS MANAGEMENT KPA 29
4.20 VERIFYING IMPLEMENTATION OF SOFTWARE PROJECT PLANNING KPA 29
4.21 VERIFYING IMPLEMENTATION OF SOFTWARE PROJECT TRACKING AND OVERSIGHT
KPA 29
4.22 VERIFYING IMPLEMENTATION OF SOFTWARE SUBCONTRACT MANAGEMENT KPA 30
4.23 VERIFYING IMPLEMENTATION OF SOFTWARE CONFIGURATION MANAGEMENT KPA
30
4.24 VERIFYING IMPLEMENTATION OF ORGANIZATION PROCESS DEFINITION 30
4.25 VERIFYING IMPLEMENTATION OF INTEGRATED SOFTWARE MANAGEMENT 31
4.26 VERIFYING IMPLEMENTATION OF SOFTWARE PRODUCT ENGINEERING 31
4.27 VERIFYING IMPLEMENTATION OF INTER-GROUP COORDINATION 32
4.28 VERIFYING IMPLEMENTATION OF PEER REVIEWS 32
5 NOTES 32
Page 3 of 33 Pages
Software Quality Assurance Plan (SQAP)
[Project Name]
1 Scope
[This section shall be divided into the following paragraphs.]
[Example: This plan establishes the SQA activities performed during development and
maintenance of the [project name].
The goal of the SQA program is to ensure that all software and documentation to be
delivered meet all technical requirements. The SQA procedures defined herein shall be
used to examine all deliverable software and documentation to determine compliance
with technical and performance requirements.]
1.1 Identification
[This paragraph shall contain a full identification of the system and the software to which
this document applies, including, as applicable, identification number(s), title(s),
abbreviation(s), version number(s), and release number(s).]
[Example: This document is a template of a Software Quality Assurance (SQA) Plan
using the guidelines provided in IEEE 730-1989, 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 an SQA Plan (SQAP) 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 documents.
Table 10-1. Software Lifecycle Activities
Page 4 of 33 Pages
Software Quality Assurance Plan (SQAP)
[Project Name]
SOFTWARE LIFECYCLE
ACTIVITY
Project Planning & Oversight
Software Development Environment
System Requirements Analysis
System Design
Software Requirements Analysis
Software Design
Software Implementation & Unit Testing
Unit Integration & Testing
Software Item Qualification Testing
Software/Hardware Item Integration & Testing
System Qualification Testing
Software Use Preparation
Software Transition Preparation
[Table 1-1 shows the software life cycle activities of the Software Items to which this
SQAP applies.
[In Table 1-1, add or delete activities that do or do not apply to the project’s software
lifecycle, and as specified in the project’s SDP.]]
1.2 System Overview
[This paragraph shall briefly state the purpose of the system and the software to which
this document applies. It shall describe the general nature of the system and software;
summarize the history of system development, operation, and maintenance; identify the
project sponsor, acquirer, user, developer, and support agencies; identify current and
planned operating sites; and list other relevant documents.]
[Example: Table 1-2 shows the software items that this plan applies to.
Page 5 of 33 Pages
- 1
- 2
- 3
- 4
- 5
- 6
前往页