| 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.
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?
- Essential
- GOAL 1
- GOAL 2
- Expected
- GOAL 3
- Desired
- GOAL N
| Activity | Coverage or Frequency | Description |
|---|---|---|
| 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 |
- 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.
- 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.