Quality Assurance Plan Checklist

QUALITY ASSURANCE PLAN CHECKLIST
GUIDELINES FOR THE QUALITY ASSURANCE PLAN CHECKLIST:
This checklist is provided as part of the evaluation process for the Quality Assurance Plan. The checklist assists designated reviewers in determining
whether specifications meet criteria established in HUD’s System Development Methodology (SDM). The objective of the evaluation is to determine
whether the document complies with HUD development methodology requirements.
Attached to this document is the DOCUMENT REVIEW CHECKLIST. Its purpose is to assure that documents achieve the highest standards relative to
format, consistency, completeness, quality, and presentation.
Submissions must include the following three documents, and must be presented in the following order: (First) Document Review Checklist, (Second) the
Quality Assurance Plan Checklist, and (Third) the Quality Assurance Plan.
Document authors are required to complete the two columns indicated as “AUTHOR X-REFERENCE Page #/Section #” and “AUTHOR COMMENTS”
before the submission. Do NOT complete the last two columns marked as “COMPLY” and “REVIEWER COMMENTS” since these are for the designated
reviewers.
Document reviewers will consult the HUD SDM and SDM templates when reviewing the documents and completing the reviewer’s portions of this
checklist.
AUTHOR REFERENCE (Project Identifier):
Designated Reviewers: Start Date: Completed Date: Area Reviewed: Comments:

1:
2:
3:
4:
Summary Reviewer:
12 April 2002 Peer Review Page i

The Quality Assurance Plan (QAP) presents a framework for activities, which when followed, will ensure delivery of quality products and services. The SDM
provides the project standards and procedures to be used as the basis for the QA group’s reviews and audits.
TABLE OF CONTENTS
1.0 General Information 4.0 Reviews and Audits

1.1 Purpose 4.1 Review Process
1.2 Scope 4.2 Formal Reviews and Audits
1.3 System Overview 4.2.1 Lifecycle Reviews
1.4 Project References 4.2.2 Audits
1.5 Acronyms and Abbreviations 4.3 Informal Reviews
1.6 Points of Contact 4.4 Review Reports
1.6.1 Information 4.5 Review and Audit Metrics
1.6.2 Coordination 5.0 Testing
2.0 Schedule of Tasks and Responsibilities 6.0 Problem Reporting and Corrective Action
3.0 System Documentation 6.1 Problem/Issue Documentation
3.1 Documents by Phase 6.2 Report Metrics
3.1.1 Initiate Phase 7.0 Tools
3.1.2 Define Phase 8.0 Project Controls
3.1.3 Design Phase 8.1 Product Control
3.1.4 Build Phase 8.2 Supplier Control
3.1.5 Evaluate Phase 9.0 Training
3.1.6 Operate Phase
3.2 Discipline for Documentation Standard Practices
12 April 2002 Peer Review Page ii

To be completed by Author To be completed by Reviewer

AUTHOR
REQUIREMENT X-REFERENCE AUTHOR COMMENTS COMPLY REVIEWER
Page #/Section # COMMENTS
Y N
1.0 GENERAL INFORMATION
1.1 Purpose: Describe the purpose of the Quality
Assurance Plan.
1.2 Scope: Describe the scope of the Quality Assurance
Plan as it relates to the project.
1.3 System Overview: Provide a brief system overview
description as a point of reference for the remainder of
the document, including responsible organization,
system name or title, system code, system category,
operational status, and system environment and special
conditions.
1.4 Project References: Provide a list of the references
that were used in preparation of this document.
1.5 Acronyms and Abbreviations: Provide a list of the
acronyms and abbreviations used in this document and
the meaning of each.
1.6 Points of Contact:
1.6.1 Information: Provide a list of the points of
organizational contact (POCs) that may be
needed by the document user for
informational and troubleshooting purposes.
1.6.2 Coordination: Provide a list of
organizations that require coordination
between the project and its specific support
function (e.g., installation coordination,
security, etc.). Include a schedule for
coordination activities.
12 April 2002 Peer Review Page 1


AUTHOR
Y N
2.0 SCHEDULE OF TASKS AND RESPONSIBILITIES
Based on the tasks described in your Project Plan,
provide a schedule of the QA activities for the duration
of the project. Tasks may include, but are not limited
to, those listed below:
• Identify Standards and Guidelines

• Evaluate Software Tools
• Evaluate Facilities
• Evaluate Software Products Review Process
• Evaluate Project Planning, Tracking, and
Oversight Processes
• Evaluate Requirements Analysis Process
• Evaluate Design Process
• Evaluate Code and Unit Testing Process
• Evaluate Integration Testing Process
• Evaluate Acceptance Testing Process
• Evaluate Release Process
• Evaluate the Corrective Action Process
• Evaluate Media Certification Process
• Certify Non-deliverable Software
• Evaluate Storage and Handling Process
• Evaluate Deviations and Waivers Process
• Evaluate Configuration Management Process
• Evaluate Software Development Library
Control Process
• Evaluate Non-developmental Software
• Perform Configuration Audits
• Evaluate Risk Management Process


AUTHOR
Y N
3.0 SYSTEM DOCUMENTATION
3.1 Documents by Phase: List and briefly describe the
documentation expected to be produced during this
project. Depending on the size of your project, this
may include, but is not limited to, the documents in the
following subsections:
3.1.1 Initiate Phase:
• Needs Statement
• Project Plan (including WBS)
• Configuration Management Plan
• Quality Assurance Plan
• Feasibility Study
• Cost/Benefit Analysis
• Risk Analysis
3.1.2 Define Phase:
• System Support and Acquisition Plan
(initial)
• Functional Requirements Document
• Data Requirements Document
• System Security and Privacy Plan
• Internal Audit Plan
• Project Plan (updated)
3.1.3 Design Phase:
• System/Subsystem Specifications
• Database Specifications
• Program Specifications
• System Support and Acquisition Plan (final)
• Validation, Verification, and Testing Plan
(initial)
• Training Plan (initial)


AUTHOR
Y N
3.1.4 Build Phase:
• Installation and Conversion Plan (initial)
• Test Plan
• User’s Manual
• Operations Manual
• Maintenance Manual
• Validation, Verification, and Testing
Plan (final)
• Training Plan (final)
3.1.5 Evaluate Phase:
• Test Results and Evaluation Reports
• Installation and Conversion Plan (final)
3.1.6 Operate Phase:
• Pilot Test Results
• Training Material
3.2 Discipline for Documentation Standard Practices:
Describe the criteria that will be applied during review
and evaluation of all lifecycle documents.


AUTHOR
Y N
4.0 REVIEWS AND AUDITS
4.1 Review Process: Define the steps of the review
process and the procedures that will be used to conduct
reviews.
4.2 Formal Reviews and Audits:
4.2.1 Lifecycle Reviews: Identify the types of
SDM associated lifecycle or non-lifecycle
reviews that will be conducted within each
project lifecycle phase. Include a schedule
of reviews and include how the results of
each review will be used on the project.
Typically, the lifecycle reviews include:
• Requirements Review
• Design Review
• Specification Review
• Preliminary Design Review
• Critical Design Review
• Test Readiness Review
• Formal Qualification Review
• Production Readiness Review
• Acceptance Test Review
• Post-Implementation Review
4.2.2 Audits: Describe the audits that will be
conducted on the project and when they will
be scheduled.
4.3 Informal Reviews: Outline the types of informal
reviews that will be conducted.
4.4 Review Reports: Identify QA reports that will be
produced throughout the project lifecycle and their
uses.
4.5 Review and Audit Metrics: Describe the metrics that
will be used to capture management information, and
how they will be analyzed and reported.


AUTHOR
Y N
5.0 TESTING
Identify the roles and responsibilities of the QA
function in relation to testing throughout the various
stages of the project.
6.0 PROBLEM REPORTING AND CORRECTIVE ACTION
Discuss QA responsibilities and activities concerned
with the reporting and tracking of project-related
problems and resolutions.
6.1 Problem/Issue Documentation: Explain how
problems and issues will be documented.
6.2 Report Metrics: Describe how metrics from the
above reports will be collected and analyzed to
determine and coordinate corrective actions.
7.0 TOOLS
Describe the tools that will be used for QA and the
methodology employed to implement usage of the
mentioned tools.
8.0 PROJECT CONTROLS
8.1 Product Control: Identify how QA will monitor the
methods and tools used to maintain and store controlled
versions of system products.
8.2 Supplier Control: Describe the provisions for
assuring that products provided by suppliers meet
established requirements.
9.0 TRAINING
Identify the training activities that will be provided to
meet the needs of QA on this project.

Quality Assurance Plan Checklist

Uploaded by

Copyright:

Available Formats

Quality Assurance Plan Checklist

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Quality Assurance Plan Checklist

Uploaded by

Copyright:

Available Formats

QUALITY ASSURANCE PLAN CHECKLIST

GUIDELINES FOR THE QUALITY ASSURANCE PLAN CHECKLIST:

AUTHOR REFERENCE (Project Identifier):

Designated Reviewers: Start Date: Completed Date: Area Reviewed: Comments:

12 April 2002 Peer Review Page i

1.0 General Information 4.0 Reviews and Audits

12 April 2002 Peer Review Page ii

To be completed by Author To be completed by Reviewer

12 April 2002 Peer Review Page 1

To be completed by Author To be completed by Reviewer

• Identify Standards and Guidelines

12 April 2002 Peer Review Page 2

To be completed by Author To be completed by Reviewer

12 April 2002 Peer Review Page 3

To be completed by Author To be completed by Reviewer

12 April 2002 Peer Review Page 4

To be completed by Author To be completed by Reviewer

12 April 2002 Peer Review Page 5

To be completed by Author To be completed by Reviewer

12 April 2002 Peer Review Page 6

You might also like