Book Review of Software Project Survival Guide 3. Quality Assurance

xiaoxiao2021-03-06  57

Of this chapter is actually nothing new, are some of the methods have to find out about, for example: 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. but there is a very useful form, ready to change it on the application stand up.

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 close

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, Ando ON

Date the Defect Was Corred

Person WHO CORRECTED THE DEFECT

Effort Required to Correct The Defect

In Staff Hours

Work Product or Products Corred

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

转载请注明原文地址:https://www.9cbs.com/read-83664.html

New Post(0)