Posts Subscribe to CommentsSubscribe the QA and Software Testing Newsletter FREE!!

Recent Posts

QTP & Keyword Driven Testing

Tricky Questions in QTP

Asset Upgrade tool in QTP

New Features in QTP 10
Browse » Home » » Guidelines for Test Case/ Test Plan/ Requirements/ Project Plan Review Planning and Preparation

Dec 11, 2008

Guidelines for Test Case/ Test Plan/ Requirements/ Project Plan Review Planning and Preparation

Subscribe the QA and Software Testing Newsletter
Post Your Queries | QA and Testing - Table of Contents

SPONSORED LINKS Reading: Guidelines for Test Case/ Test Plan/ Requirements/ Project Plan Review Planning and PreparationTweet this Post

Review Planning

  1. Allocate resources and time schedule for reviews.
    For reviews to be effective, they should be scheduled as tasks during the software engineering process. You should plan for up to 20 % of the effort spent on creating the documents to be reviewed.
    In addition, time should be scheduled for the possible modifications that will occur as the result of a review. You should plan for up to 10 % of the effort spent on creating the documents to be reviewed (in case of one rework).

  2. Conduct meaningful training for all reviewers.
    The training should stress both process-related issues and the human psychological side of reviews.

  3. Choose a moderator for the review session.
    • The moderator must have the analytic expertise to be able to follow the review discussions.
Read More.. Click here to read the complete Article

SPONSORED LINKS

Reading: Guidelines for Test Case/ Test Plan/ Requirements/ Project Plan Review Planning and PreparationTweet this Post
at 9:39 AM

Comments :

0 comments to “Guidelines for Test Case/ Test Plan/ Requirements/ Project Plan Review Planning and Preparation”

Post a Comment

Subscribe to: Post Comments (Atom)

Software testing Metrices-Test Case Review

Metrics are the means by which the software quality can be measured; they give you confidence in the product.

 

Energize your test team

You're waist deep in your third month of late nights, weekends, and shipping stress; you can see and feel your team's energy waning.

 

The Value of Positive Testing

There is a school of thought in software testing that debunks the value of positive testing. This school basically states that any test that does not produce a defect is not a good test.

Impact Analysis Checklist for Req. Changes
___    Implications of the Proposed Change* Identify any existing requirements in the baseline that

The Process of Test Process Improvement

Software testing is still a pain-in-the-neck for many organizations. Because it is only marginally addressed in software process improvement models like CMMi

 

Software Defect-bug Management Philosphy

Imperfect processes cause most of the software defects. Thus to prevent defects, the development process needs to be overhauled.

 

Software testing Metrices-Test Case Review

Metrics are the means by which the software quality can be measured; they give you confidence in the product.

 

Energize your test team

You're waist deep in your third month of late nights, weekends, and shipping stress; you can see and feel your team's energy waning.

 

The Value of Positive Testing

There is a school of thought in software testing that debunks the value of positive testing. This school basically states that any test that does not produce a defect is not a good test.

Blog Archive