Software Reviews
Software reviews are a filter for the software engineering procedure. Those are reviews applied at several points during Software development and serve to uncover errors which can then be erased. The Software reviews serve to purify the software work products which occur as a result of coding and analysis design. Weinberg and Freedman [FRE90] describe the requirement for reviews this way:
Technical work wants reviewing for the similar reason which pencils required removed to err is human. The 2nd reason we want technical reviews is which although people are good at catching some of their own errors in large classes of errors escape the originator more simply than they escape anyone else. The review process is thus, the answer to the prayer of Robert Burns:
O wad some power the giftie give us
To see ourselves as other set us
A review-any review-is a path of using the diversity of a set of people to:
1. Point out required improvement in the product of single person or team
2. Confirm those categories of a product in that improvement is either not desired or not needed; and
3. Achieve technical work of more uniform or at least more predictable. The Quality than can be achieved without reviews in order to make technical work more manageable.
There are several different kinds of reviews that can be conducted as category of software engineering. Every have its own place. An informal meeting around the coffee machine is a form of review if technical problems are described. A formal presentation of software design to an audience of management, customers and technical staff is a form of review. Moreover we focus on the formal technical review sometimes is called a walkthrough.
The formal technical review is the most effective filter from a quality assurance standpoint Conducted through software engineers and others for software engineers the FTR is an effectual means for improving software quality.