THE SOFTWARE QUALITY ASSURANCE PLAN (SQAP)

Title Page

1.1.

Project Title

1.2.
Abstract
(1-2 sentences describing the project)
Table of Contents
TITLE PAGE.............................................................................................................................................................................1
1.1. PROJECT TITLE .............................................................................................................................................................1
1.2. ABSTRACT....................................................................................................................................................................1
TABLE OF CONTENTS.........................................................................................................................................................1
2. PURPOSE..............................................................................................................................................................................1
3. MANAGEMENT...................................................................................................................................................................2
3.1. ORGANISATION.............................................................................................................................................................2
3.2. PROJECT PLAN..............................................................................................................................................................2
4.DOCUMENTATION.............................................................................................................................................................2
5.STANDARDS, PRACTICES, & CONVENTIONS...........................................................................................................2
6.REVIEWS...............................................................................................................................................................................3
6.1. SOFTWARE QUALITY ASSURANCE PLAN REVIEW (SQAPR)...............................................................................................3
6.2. SOFTWARE REQUIREMENTS REVIEW (SRR)......................................................................................................................3
6.3. CRITICAL DESIGN REVIEW (CDR)..................................................................................................................................3
6.4. TEST PLAN REVIEW (TPR)...........................................................................................................................................3
6.5. USER DOCUMENTATION REVIEW (UDR).........................................................................................................................3
7.VERIFICATION, VALIDATION & TESTING................................................................................................................3
8. PROBLEM REPORTING & CORRECTIVE ACTION.................................................................................................3
9. TOOLS, TECHNIQUES & METHODOLOGIES...........................................................................................................3
9.1. DESIGN METHODOLOGY.................................................................................................................................................3
9.2. CHOICE OF LANGUAGE....................................................................................................................................................4
9.3. TOOLS FOR CODING........................................................................................................................................................4
9.4. VERSION CONTROL........................................................................................................................................................4
9.5. RECORDS COLLECTION, MAINTENANCE & RETENTION.......................................................................................................4
9.6. MEDIA CONTROL..........................................................................................................................................................4
9.7. OTHER TOOLS..............................................................................................................................................................4
10.RISK MANAGEMENT.......................................................................................................................................................4
10.1. SCHEDULE CONTROL...................................................................................................................................................4
10.2. CHANGE CONTROL......................................................................................................................................................4
10.3. CONFLICT RESOLUTION................................................................................................................................................4

2. Purpose
/* This section should describe the intended result of the project. /*

The client requires this product because ....

3. Management
3.1.
Organisation
The team for this project is:
QATutorial.com
QATutorial.com
email: QATutorial@ QATutorial.com
3.2.
Project Plan
/* This section is essentially a summary of the major milestones from the Project Plan. */
Completion of Software Quality Assurance Plan

Date: dd/mmm/yyyy

Completion of Software Requirements Specification

Date: dd/mmm/yyyy

Completion of Design Documentation

Date: dd/mmm/yyyy

Completion of Software Test Plan

Date: dd/mmm/yyyy

Completion of Media Production

Date: dd/mmm/yyyy

Completion of Coding

Date: dd/mmm/yyyy

Conclusion of Debugging/Maintenance

Date: dd/mmm/yyyy

Delivery

Date: dd/mmm/yyyy

4.Documentation
The following Documents will be produced during the course of the project, according to the
templates described in Section 3 of the MEU Quality Manual.
(i)
(ii)
(iii)
(iv)
(v)
(vi)
(vii)

Project Plan
Location of Document: //server/test1
Software Quality Assurance Plan
Location of Document: //server/test1
Software Requirements Specification (SRS)
Location of Document: //server/test1
Software Design Description (SDD)
Location of Document: //server/test1
Software Test Plan (TP)
Location of Document: //server/test1
User Documentation
Location of Document: //server/test1
Design Notebook
Location of Document: //server/test1

5.Standards, Practices, & Conventions

The Standards, Practices & Conventions to be used in this project are mentioned below,

6.Reviews
6.1.
Date:

Software Quality Assurance Plan Review (SQAPR)

Personnel needed:
Review Criteria: Section x.1 Quality Manual.
6.2.
Date:

Software Requirements Review (SRR)

Personnel needed:
Review Criteria: Section x.2 of the Quality Manual.
6.3.
Date:

Critical Design Review (CDR)

Personnel needed:
Review Criteria: Section x.3 of the Quality Manual.
6.4.
Date:

Test Plan Review (TPR)

Personnel needed:
Review Criteria: Section x.4 of the Quality Manual.
6.5.
Date:

User Documentation Review (UDR)

Personnel needed:
Review Criteria: Section x.5 of the Quality Manual.
7.Verification, Validation & Testing
The criteria that will be used to verify and validate the products of this project are defined in Section
x of the Quality Manual.
8. Problem Reporting & Corrective Action
/* This section should describe how software errors are reported, and how team members are
allocated to the task of fixing them. */
9. Tools, Techniques & Methodologies
/* This section should list the special software tools, techniques, and methodologies used in the
project and state their purposes, and describe their use. */
9.1.
Design Methodology
/* fill this in */

9.2.
Choice of language
/* fill this in with justification */
9.3.
Tools for coding
Compiler(s)
/* fill this in */
Programming environment
/* fill this in */
9.4.
Version Control
/* Fill this in. Projects should try to make use of a version control system such as Microsoft Visual
Source Safe. Until this is possible, some form of manual version control should be used */
9.5.
Records Collection, Maintenance & Retention
/* fill this in, probably Records but how will you use it, changes to SQAP and NB, who is
responsible, when, what is recorded and where */
9.6.
Media Control
/* fill this in, including directory organisation and backup and labelling of floppy disks if needed
by PC and Mac projects */
9.7.
Other Tools
/* fill this in */
10.Risk Management
10.1. Schedule Control
/* Projects can fall behind schedule for a vast number of reasons. This Section aims to get the
Project Manager to anticipate potential problems and create mitigation strategies for them in
advance. */
10.2. Change Control
/* managing changes to the system, whether initiated by client or team member */
/* fill this in */
10.3. Conflict Resolution
/* resolving team conflicts */
/* fill this in */
11.Reference Documents
Reference documents used for this project include:
-