When reviews are needed? or What are the reasons for reviews?

Reviews are necessary due to following reasons:

• Reviews are useful not only for finding and eliminating defects, but also for gaining consensus among the project team, securing approval from stakeholders, and aiding in professional development for team members.

• Reviews help teams find defects soon after they are injected making them cost less to fix than they would cost if they were found in test.

• All work products in a software project should be either reviewed or tested.

 For Example :Software requirements specifications(SRS) Software Functional Specifications(SFS), schedules, design documents, code, test plans, test cases, and defect reports should all be reviewed.

What are six software defect origins?

These are the defect origins

• Requirements
  
• Design
• Source code
• User manuals/training material
• “Bad fixes” or mistakes made during repairs
• Flawed test cases used by the application

• Requirements

There may ambiguous or unclear or unrelated requirements later which produce defects in the saoftware

• Design

If the design is not proper then it may arise the software defects

• Source code

The source code may not be proper or buggy against requirements

• User manuals/Training material

If the user manual or training materials are not according to business then defect can come in the software

• “Bad fixes” or mistakes made during repairs

If bugs reported are not fixed properly or when when repairing does not care for the ripple effects or dependency

• Flawed test cases used by the application

When test cases written for testing were not proper as per requirement of the software.