Quality Assurance Plan - HUD
[pic]
QUALITY
ASSURANCE
PLAN
Project or System Name
U.S. Department of Housing and Urban Development
Month, Year
Revision Sheet
|Release No. |Date |Revision Description |
|Rev. 0 |5/30/00 |Quality Assurance Plan Template and Checklist |
|Rev. 1 |6/13/00 |New section 2.0 (Task and Responsibilities) and additional text in section 3.1 |
|Rev. 2 |4/12/02 |Conversion to WORD 2000 format |
| | | |
| | | |
| | | |
| | | |
| |Quality Assurance Plan Authorization |
| |Memorandum |
I have carefully assessed the Quality Assurance Plan for the (System Name). This document has been completed in accordance with the requirements of the HUD System Development Methodology.
MANAGEMENT CERTIFICATION - Please check the appropriate statement.
______ The document is accepted.
______ The document is accepted pending the changes noted.
______ The document is not accepted.
We fully accept the changes as needed improvements and authorize initiation of work to proceed. Based on our authority and judgment, the continued operation of this system is authorized.
_______________________________ _____________________
NAME DATE
Project Leader
_______________________________ _____________________
NAME DATE
Operations Division Director
_______________________________ _____________________
NAME DATE
Program Area/Sponsor Representative
_______________________________ _____________________
NAME DATE
Program Area/Sponsor Director
QUALITY ASSURANCE PLAN
TABLE OF CONTENTS
Page #
1.0 GENERAL INFORMATION 1-1
1.1 Purpose 1-1
1.2 Scope 1-1
1.3 System Overview 1-1
1.4 Project References 1-2
1.5 Acronyms and Abbreviations 1-2
1.6 Points of Contact 1-2
1.6.1 Information 1-2
1.6.2 Coordination 1-2
2.0 SCHEDULE OF TASKS AND RESPONSIBILITIES 2-1
3.0 SYSTEM DOCUMENTATION 3-1
3.1 Documents by Phase 3-1
3.1.1 Initiate Phase 3-1
3.1.2 Define Phase 3-1
3.1.3 Design Phase 3-2
3.1.4 Build Phase 3-2
3.1.5 Evaluate Phase 3-2
3.1.6 Operate Phase 3-2
3.2 Discipline for Documentation Standard Practices 3-3
4.0 REVIEWS AND AUDITS 4-1
4.1 Review Process 4-1
4.2 Formal Reviews and Audits 4-1
4.2.1 Lifecycle Reviews 4-1
4.2.2 Audits 4-1
4.3 Informal Reviews 4-2
4.4 Review Reports 4-2
4.5 Review and Audit Metrics 4-2
5.0 TESTING 5-1
6.0 PROBLEM REPORTING AND CORRECTIVE ACTION 6-1
6.1 Problem/Issue Documentation 6-1
6.2 Report Metrics 6-1
7.0 TOOLS 7-1
8.0 PROJECT CONTROLS 8-1
8.1 Product Control 8-1
8.2 Supplier Control 8-1
9.0 TRAINING 9-1
1.0 GENERAL INFORMATION
NOTE TO AUTHOR: Highlighted, italicized text throughout this template is provided solely as background information to assist you in creating this document. Please delete all such text, as well as the instructions in each section, prior to submitting this document. ONLY YOUR PROJECT-SPECIFIC INFORMATION SHOULD APPEAR IN THE FINAL VERSION OF THIS DOCUMENT.
This 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.
GENERAL INFORMATION
1 1.1 Purpose
Describe the purpose of the Quality Assurance Plan.
2 1.2 Scope
Describe the scope of the Quality Assurance Plan as it relates to the project.
3 1.3 System Overview
Provide a brief system overview description as a point of reference for the remainder of the document. In addition, include the following:
1. Responsible organization
2. System name or title
3. System code
4. System category
1. Major application: performs clearly defined functions for which there is a readily identifiable security consideration and need
2. General support system: provides general ADP or network support for a variety of users and applications
5. Operational status
3. Operational
4. Under development
6. System environment and special conditions
4 1.4 Project References
Provide a list of the references that were used in preparation of this document. Examples of references are:
7. Previously developed documents relating to the project
8. Documentation concerning related projects
9. HUD standard procedures documents
10. Quality Assurance Guidelines
5 1.5 Acronyms and Abbreviations
Provide a list of the acronyms and abbreviations used in this document and the meaning of each.
6 1.6 Points of Contact
1 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. Include type of contact, contact name, department, telephone number, and e-mail address (if applicable). Points of contact may include, but are not limited to, helpdesk POC, development/maintenance POC, and operations POC.
2 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.
2.0 SCHEDULE OF TASKS AND RESPONSIBILITIES
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. (Refer to the Quality Assurance Guidelines in the SDM for a complete description of these tasks.) A waiver exempting the project from any of these tasks is required.
11. Identify Standards and Guidelines
12. Evaluate Software Tools
13. Evaluate Facilities
14. Evaluate Software Products Review Process
15. Evaluate Project Planning, Tracking, and Oversight Processes
16. Evaluate Requirements Analysis Process
17. Evaluate Design Process
18. Evaluate Code and Unit Testing Process
19. Evaluate Integration Testing Process
20. Evaluate Acceptance Testing Process
21. Evaluate Release Process
22. Evaluate the Corrective Action Process
23. Evaluate Media Certification Process
24. Certify Non-deliverable Software
25. Evaluate Storage and Handling Process
26. Evaluate Deviations and Waivers Process
27. Evaluate Configuration Management Process
28. Evaluate Software Development Library Control Process
29. Evaluate Non-developmental Software
30. Perform Configuration Audits
31. Evaluate Risk Management Process
3.0 SYSTEM DOCUMENTATION
SYSTEM DOCUMENTATION
This section describes all documentation that will be generated, by lifecycle phase, for the project. The identified documentation listed will be that which control the development, verification and validation, use and maintenance of the software.
1 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. (Note that some of the documents listed below are updated in subsequent phases.) The HUD SDM Documentation Standards lists the objectives for producing standardized system documentation. The QAP may include any other deliverables cited in the project Work Breakdown Structure (WBS).
1 3.1.1 Initiate Phase
32. Needs Statement
33. Project Plan (including WBS)
34. Configuration Management Plan
35. Quality Assurance Plan
36. Feasibility Study
37. Cost/Benefit Analysis
38. Risk Analysis
2 3.1.2 Define Phase
39. System Support and Acquisition Plan (initial)
40. Functional Requirements Document
41. Data Requirements Document
42. System Security and Privacy Plan
43. Internal Audit Plan
44. Project Plan (updated)
3 3.1.3 Design Phase
45. System/Subsystem Specifications
46. Database Specifications
47. Program Specifications
48. System Support and Acquisition Plan (final)
49. Validation, Verification, and Testing Plan (initial)
50. Training Plan (initial)
51. Project Plan (updated)
4 3.1.4 Build Phase
52. Installation and Conversion Plan (initial)
53. Test Plan
54. User’s Manual
55. Operations Manual
56. Maintenance Manual
57. Validation, Verification, and Testing Plan (final)
58. Training Plan (final)
59. Project Plan (updated)
5 3.1.5 Evaluate Phase
60. Test Results and Evaluation Reports
61. Installation and Conversion Plan (final)
62. Project Plan (updated)
6 3.1.6 Operate Phase
63. Pilot Test Results
64. Training Material
65. Project Plan (updated)
2 3.2 Discipline for Documentation Standard Practices
Describe the criteria that will be applied during review and evaluation of all lifecycle documents. If HUD documentation standard templates are not used in the creation of project documents, describe the alternative. A waiver exempting the project from standard template usage is required.
4.0 REVIEWS AND AUDITS
REVIEWS AND AUDITS
This section discusses quality assurance’s role in the reviews and audits that will be conducted during the lifecycle of the project to ensure the quality, consistency, comprehension, and completeness of the project documentation and activities.
1 4.1 Review Process
Define the steps of the review process and the procedures that will be used to conduct reviews. Address management and attendee responsibilities with respect to the review process.
2 4.2 Formal Reviews and Audits
This subsection addresses the formal, scheduled reviews and audits that will be conducted on the project. Reviews are a monitoring mechanism to assess the progress and well being of the project.
1 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:
66. Requirements Review
67. Preliminary Design Review
68. Specification Review
69. Design Review
70. Critical Design Review
71. Test Readiness Review
72. Formal Qualification Review
73. Production Readiness Review
74. Acceptance Test Review
75. Post-Implementation Review
2 4.2.2 Audits
Describe the audits that will be conducted on the project and when they will be scheduled. Audits are independent examinations of a deliverable or a set of deliverables. Audits are accomplished by comparing the actual characteristics of a deliverable with those required or specified.
3 4.3 Informal Reviews
Outline the types of informal reviews that will be conducted. Types of reviews may include walkthroughs, desk check codes, peer reviews, and quality control reviews.
4 4.4 Review Reports
Identify QA reports that will be produced throughout the project lifecycle and their uses. These reports may include:
76. Review issues list
77. Review summary report
78. Action tracking report
5 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.
5.0 TESTING
TESTING
Identify the roles and responsibilities of the QA function in relation to testing throughout the various stages of the project. These include but are not limited to:
79. Unit testing
80. System testing
81. Integration testing
82. Regression testing
83. Acceptance testing
6.0 PROBLEM REPORTING AND CORRECTIVE ACTION
PROBLEM REPORTING AND CORRECTIVE ACTION
Discuss QA responsibilities and activities concerned with the reporting and tracking of project-related problems and resolutions.
1 6.1 Problem/Issue Documentation
Explain how problems and issues will be documented.
2 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
TOOLS
This section discusses QA responsibilities and activities concerned with the reporting and tracking of project related problems and resolutions.
Describe the tools that will be used for QA and the methodology employed to implement usage of the mentioned tools. The tools may include, but are not limited to:
84. Operating system utilities
85. Debugging aids
86. Documentation tools
87. Code and structure analyzers
88. Monitors
89. Statistical analysis packages
90. Static or dynamic test tools
8.0 PROJECT CONTROLS
PROJECT CONTROLS
1 8.1 Product Control
Identify how QA will monitor the methods and tools used to maintain and store controlled versions of system products.
2 8.2 Supplier Control
Describe the provisions for assuring that products provided by suppliers meets established requirements. In some cases, projects do not foresee purchasing certain products. If that is the case, the following paragraph may be used:
All supplier products have been operationally tested in the target system. No future product acquisition is planned.
9.0 TRAINING
TRAINING
Identify the training activities that will be provided to meet the needs of QA on this project. Suggested training may include:
91. Project orientation on roles, responsibilities, and quality assurance staff authority
92. Software engineering skills and practices
93. Project standards, procedures, and methods
94. Understanding and using automated tools
95. Interpersonal communications
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- dod guide to iuid quality assurance
- project quality management plan template
- risk analysis quality assurance iso 9001 and business
- quality assurance plan hud
- skills matrix quality assurance
- how era develops software
- quality assurance policy
- implementation plan template
- sample quality assurance surveillance plan
- example of a qa project plan review checklist
Related searches
- quality assurance vs quality control
- construction quality assurance plan template
- simple quality assurance plan template
- quality assurance quality control pdf
- quality assurance and quality improvement
- quality assurance improvement plan template
- quality assurance plan template free
- quality assurance plan examples
- basic quality assurance plan template
- quality assurance program plan template
- quality assurance plan example
- laboratory quality assurance plan template