Quality Plan
Project name:
Example
Owner:
Sum Body Else
Modification date: yyyy/mm/dd
   
Checkpoint documents: Other documents:
 
 

 

Description:

This Quality Plan sets the project plans and expectations for overall project quality, tools, processes and plans.  This includes early release programs (like alpha- and beta-sites). 
 
Quality Objectives:

 
Must
  • Maintain code at its current quality level 
  • Meet division blah's functionality needs
Want
  • Improve code quality in the blah  module
  • Add additional test coverage 
Not
  • Get to 100% branch coverage
  • Remove all defects

 
FLURPS:

The FLURPS (functionality, localizability, usability, reliability, performance and supportability) model is the basis for this quality plan.  These various FLURPS aspects need to be balanced.
 
Quality Aspect
Importance
Comments
Functionality Medium blah blah
Localizability Low The system includes localization facilities for divisional use, but the base system doesn't need to be localized.
Usability High blah
Reliability High blah
Performance Medium The intent is to have good performance, but in the context of the use of the system, performance is not a huge driving issue.
Supportability Medium blah

 
 
Artifacts to be tested:

The specific artifacts and/or components that will be tested are:

  • Installation application
  • Readme file
  • FooBar application
  • BarFoo ActiveX/COM component
  • Help files
  • Xxyyz printed docutment
  • Uninstall application
Features to be tested:

The features that will be tested are:
 
Artifact
Features to be tested
FooBar application
  • xx
  • yy
BarFoo ActiveX component
  • integration with Visual Basic
  • yy
Help files
  • speelling
  • that there grummar thing
Xxyyz printed docutment
  • yy
  • zz

 
 
Metrics:

The specific project quality metrics are:
 
Quality Metric
Minimum
 Desired 
Achieved
Branch coverage 75% 90% to be determined
Critical defects none none to be determined
Serious defects none none to be determined
Regression test suite fully run fully run to be determined
Inspection on blah blah blah blah
Platforms tested blah blah blah
OS's tested blah blah blah

 
Tools:

 
Tool
Source
Comments
Regression test harness internal
DDTS commercial blah
BFA tool internal HP blah

 
Processes and Responsibilities:

 
Quality / Testing Task
Owner
Comments
Completed
Branch flow coverage X
Regression test suite Y

 
Plans:

 
Task
by
Owner
Status
Preliminary Quality plan written Initiation Project Manager
Preliminary Quality plan updated Requirements Complete X
Final Quality plan  Functionality Complete X
Regression tests run Release X
Branch flow analysis run Release X

 
Alpha and Beta Release Plans:

There will be no formal early release programs.
 

  Template Modified: 19990716            Template Author: Tim Mikkelsen