QA Plan
| Release Information |
|
| Project |
|
| Release Number |
|
| Release Audience |
|
| Attached Worksheets |
Review Meeting Notes |
| |
System Test Case Suite |
| |
System Test Runs |
| Related Documents |
Software Requirements Specification |
| |
Design |
| |
Project Plan |
Process Impact : This document specifies quality goals, selects strategies for assuring that those goals have been met, and details a plan of action to carry out those strategies.
Introduction
Why is this QA plan needed?
What QA lessons were learned in previous releases?
What is the scope of this QA plan?
What is the summary of this plan?
Quality Goals for this Release
- Essential
- Expected
- Desired
QA Strategy
TODO: # (For each activity, specify the coverage or frequency that you plan to achieve. If you do not plan to perform an activity, write “N/A”.)
| Activity |
Coverage or Frequency |
Description |
| |
|
|
| |
|
|
| |
|
|
QA Strategy Evaluation
| Goal |
Activity 1 |
Activity 2 |
Activity N |
Overal Assrance |
| Goal 1 |
Medium |
Medium |
High |
Strong |
| Goal 2 |
Medium |
Medium |
High |
Strong |
| Goal 3 |
Medium |
Low |
Low |
Weak |
| Goal N |
Medium |
None |
None |
At-Risk |
Evaluation Cell Values
- High: This activity gives a strong assurance that the goal has been met in development.
- Medium: This activity gives a medium assurance that the goal has been met in development.
- Low: This activity gives only a little assurance that the goal has been met in development.
- None: This activity does not address the goal.
Overall Assurance Values
- Strong: The set of activities together provide strong assurance that the goal has been met in development.
- Weak: The activities together provide limited assurance that the goal has been met in development.
- At-Risk: There is little or no assurance that this goal has been met.
Plan of Action
QA Plan Checklist
Do the selected activities in the QA Strategy provide enough assurance that the project will meet it’s quality goals
Have human resources been allocated to carry out the QA activities
Have machine and software resources been allocated as needed for the QA activities
Has this QA Plan been communicated to the development team and other stakeholders