Book Review of Software Project Survival Guide 3. Quality Assurance

这一章的内容其实没有什么新意，都是一些已经了解过的方法，例如：
Quality assurance is initiated in parallel with requirements work.

Defect tracking software is placed online at requirements development time, and defects are tracked from the beginning of the project.

The Quality Assurance Plan calls for an independent quality assurance group.

The Quality Assurance Plan contains measurable criteria that are used to determine whether the software is ready to be released.
但是有一个表格还是很有用的，准备修改一下就应用起来。

Name	Content	Description
Defect ID		a number or other unique identifier
Defect description
Steps taken to produce the defect
Platform information		CPU type, memory, disk space, video card, and so on
Defect's current status		open or closed
Person who detected the defect
Date the defect was detected
Severity		based on a numeric scale such as 1-4, or a verbal scale such as cosmetic, serious, critical, and so on
Phase in which the defect was created		requirements, architecture, design, construction, defective test case, and so on
Phase in which the defect was detected		requirements, architecture, design, construction, and so on
Date the defect was corrected
Person who corrected the defect
Effort required to correct the defect		in staff hours
Work product or products corrected		requirements statement, design diagram, code module, User Manual/Requirements Specification, test case, and so on
Resolution		pending engineering fix, pending engineering review, pending quality assurance verification, corrected, determined not to be a defect, unable to reproduce, and so on
Other notes