<Project Name>
Quality Assurance Plan
Responsible person: / name, surnameStatus: / Draft/Revised
Template ID: / tech.tmpl.020
Document Version: / 3.0.0
Last Revision Date: / November 25,2004
Quality Assurance Plan / <Project name>
Table of Contents
1. PREFACE
2. CONTACT PERSONS
3. RELATED DOCUMENTATION
4. CHANGE HISTORY
5. OPEN ISSUES
6. MANAGEMENT
6.1.Organization
6.2.Tasks and Responsibilities
7. DOCUMENTATION
8. STANDARDS, CONVENTIONS AND METRICS
8.1.Standards
8.2.Conventions
8.3.Metrics
9. REVIEWS AND AUDITS
10. TESTING
11. PROBLEM REPORTS AND CORRECTIVE ACTIONS
12. TOOLS, TECHNIQUES AND METHODOLOGIES
12.1.Tools
12.2.Methods
12.3.Methodologies
13. CONFIGURATION MANAGEMENT
14. MANAGEMENT OF ENVIRONMENT [Optional Section]
15. MANAGEMENT OF SUPPLIERS [Optional Section]
16. COLLECTION, SUPPORT AND STORAGE OF RECORDS
17. TRAINING
18. RISK MANAGEMENT
19. Signatures of Responsible Persons
Appendix A:List of tables [Optional]
Appendix B:List of Figures [Optional]
Appendix C:Glossary [Optional]
1.PREFACE
[The preface should provide an overall view of the document. State the name and the version of the described product in this section. Also, define the main document objectives.
Note: The preface should provide only information about the document, not the product.
Example:
“This Quality Assurance Plan for the <Project name. It describes planned QA activities, project strategy, schedule, responsibilities and management. The document also contains various resources required for the successful completion of this project.
The document itself is a part of <Company name> documentation and should be maintained according to the appropriate ISO procedure.”
2.CONTACT PERSONS
Name / Role / E–mail / PhonesOffice / Mobile
3.RELATED DOCUMENTATION
Document / Version / DescriptionNone.
4.CHANGE HISTORY
Date / Author / DescriptionCreated document. First draft.
5.OPEN ISSUES
ID / Author / Description / Opened6.MANAGEMENT
6.1.Organization
[Describe a structure of the organization responsible for Quality Assurance (projects, units, etc’).]
6.2.Tasks and Responsibilities
[Define Quality Assurance tasks for the project, identify project members responsible for each task execution and show, how these tasks are synchronized with the project’s milestones. The following table may be used:]
Table 1. Tasks and responsibilities
QA task / ResponsibleReviews / QA manager
Testing / QA manager
Timeframe control / Project manager
Budget control / Project manager
Management of Quality Records / Quality manager
Configuration management / Configuration manager
7.DOCUMENTATION
[Provide the overview on documentation, which should be produced for the project.]
8.STANDARDS, CONVENTIONS AND METRICS
[Provide the references to any standards, conventions, metrics, etc’ used within the project. The following subchapters may be included optionally:]
8.1.Standards
[Describe the used standards (documentation, coding, testing, etc’). The following table may be used:]
Table 2: Standards
Unit / Standard / ComplianceSpecification / <A, AD>*
Design
...
Code
* Absolute compliance (A), Adjusted compliance (AD).
8.2.Conventions
[Describe conventions for the source code, documentation, etc’.]
8.3.Metrics
[Describe product and process metrics used for to measure the project results.]
9.REVIEWS AND AUDITS
[This section specifies the schedule, resources, methods, and procedures to be used in project reviews and audits. It also defines, what reviews and audits should be carried out during the all project phases. The following can be described in this section:
1)Software requirement review;
2)Initial design review;
3)Detailed design review;
4)Review of Software verification and validation plan;
5)Review of Software configuration management plan;
6)Functional audit (test);
7)Physical audit;
8)Internal process audit (test);
9)Project management review;
10)Centralized audits of project;
11)After-project review;
12)etc’.]
10.TESTING
[Provide the references to any documents used in quality assurance testing. The following types of documentation may be required:
1)Test plan;’
2)Use case specification;
3)Check List;
4)Test journal;
5)Test problem report;
6)etc’. ]
11.PROBLEM REPORTS AND CORRECTIVE ACTIONS
[Define problem reports and corrective action procedures in this section. Any documents regarding these issues can be referenced.]
12.TOOLS, TECHNIQUES AND METHODOLOGIES
[List any tools, techniques or methodologies used in the project. The following subsections should be included:]
12.1.Tools
[The following table can be used to describe tools:]
Table 3: Project tools
Activity / Tool / NotesAnalysis
Design
Coding
Configuration management
Documentation
…
12.2.Methods
[The following table can be used to describe methods:]
Table 4: Methods
Activity / Method / NotesCoding / Defensive programming / -
...
12.3.Methodologies
[The following table may be used to describe methodologies:]
Table 5: Methodologies
Activity / Methodology / NotesAnalysis / Object Modelling Technique
13.CONFIGURATION MANAGEMENT
[Describe methods and means for supporting, storage, protection, and documentation of controlled software versions. The issues such as code management, document management and change management should be described.
Note: The reference to Configuration Management Plan can be provided instead.]
14.MANAGEMENT OF ENVIRONMENT [Optional Section]
[Describe procedures for environment management.]
15.MANAGEMENT OF SUPPLIERS [Optional Section]
[Describe procedures for supplier management.]
16.COLLECTION, SUPPORT AND STORAGE OF RECORDS
[Describe records maintained during the project. Include information on how and where each type of record is stored. Describe the following, if necessary:
1)Software QA plan;
2)Records of standard adjustments;
3)Records of reviews;
4)Overview of testing;
5)Problem reports;
6)Conclusions of internal audits;
7)Register of products supplied by customer;
8)Software product documentation;
9)Acceptance of delivery act;
10)Configuration management plan;
11)Configuration management documents and change requests;
12)Plan of verification and validation of software product;
13)Measurement and statistics data;
14)Software testing tool verification records;
15)Nonconformity and related corrective and preventive action records (nonconformity management plans, nonconformity acts, internal and centralised audit indicated nonconformity records, etc.);
16)Verification and validation records;
17)Project reviews.]
17.TRAINING
[List any training activities required for the project members to achieve the project needs.]
18.RISK MANAGEMENT
[Describe the risk management issues.]
19.Signatures of Responsible Persons
<Position of Team member> / <Name>Appendix A:
List of tables [Optional]
[The list of all document tables is advisable to insert, if there are numerous tables in the document.
To generate the List of tables execute Insert Index and Tables, select the tab Table of Figures, and then choose the caption label as “Table” and press the OK button.]
Appendix B:List of Figures [Optional]
[The list of all document figures is advisable to insert, if there are numerous figures in the document.
To generate the List of figures execute Insert Indexand Tables, select the tab Table of Figures, then choose the caption label as “Figures” and press the OK button.]
Appendix C:Glossary [Optional]
[The Glossary is advisable if there is a large amount of terms and abbreviations used in the document. The following table format may be used:]
Table 6: Terms and Abbreviations
TermsGlossary / The list of the project terms and abbreviations
Abbreviations
API / Application Programming Interface
Page 1/10