P. 1
Software Testing

Software Testing


|Views: 15,957|Likes:
Published by api-3781097
Explains in detail about Testing and types
Explains in detail about Testing and types

More info:

Published by: api-3781097 on Oct 16, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





The review summary report is typically is a single page form. It becomes part of the project historical
record and may be distributed to the project leader and other interested parties. The review issue lists
serves two purposes.

1.To identify problem areas within the product

PDF created with pdfFactory Pro trial version www.pdffactory.com


MSIT 32 Software Quality and Testing

2.To serve as an action item. Checklist that guides the producer as corrections are made. An
issues list is normally attached to the summary report.

It is important to establish a follow up procedure to ensure that item on the issues list have been
properly corrected. Unless this is done, it is possible that issues raised can “fall between the cracks”. One
approach is to assign responsibility for follow up for the review leader. A more formal approach as signs
responsibility independent to SQA group.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->