Friday, October 26, 2007

Inspections review in software Development Project

An Inspection review is a formal verification technique in which software life cycle work products are examined in details by group of peers for explicit purpose of detecting and identifying the defects। Software Inspections are a rigorous form of peer reviews, a Key Process Area for improvement. It is one of the best technique among the different peer review techniques (e.g. Buddy checks, circulation review, Technical review, Walkthroughs etc.) to detect the defect effectively. Peer Reviews on the software lifecycle work products indicate the quality of the evolving system each step on the way, increasing dramatically the probability of the highest quality product being delivered.

2. Value of implementing inspections review for organizations
I. Effective peer reviews of all types of software work products are essential if software development organizations are to reduce their cost of producing software. Formal inspections of requirements specifications, designs, source code, and other work products are a proven means for finding errors and improving the quality of software products.
II. ROI of Software Inspection Review Process: Benefit/cost ratio for Software Inspection Review is statistically 34:1 and ROI is 3000%. Software Inspection is one of the most crucial SPI to generate ROI for company in term of reduced cost, of development and maintenance, statistically analyzed by David F. Rico on several project Data. (Book Ref: ROI of Software Process Improvement)
III. Minimal defect correction backlash at systems integration time.
IV. Peer Reviews aim to minimize the number of defects being passed along from one segment to the next, by finding and fixing the defects in the segment in which they were created.
a. 23% increase in coding productivity
b. 25% reduction of schedule plans
c. Each major defect found at inspection saves an average of nine hours of correction time later.
d. Up front costs are outweighed by benefit.
V. The role of inspection in software development process is not only directed to detect and correct faults as early as possible. It is a method for measuring and controlling the whole development process, and the way to predict and prevent faults in later phases.
a. The process is led by a moderator who is not the author and is impartial to the life-cycle work product under review.
b. Defect resolution is mandatory (performed off-line) and rework is formally verified.
c. Improvement in consequent product quality
VI. According to the IBM analysis Inspection reviews is most effective technique for detect Errors and defect removal. It effectiveness in term of percentage is 60-70%.
VII. Post-implementation maintenance costs can be reduced by ~50% with formal inspection reviews.
VIII. Data is analyzed to improve the product, the process and the effectiveness of the inspection process. This is added value to the organization in term of Maturity of the process (SEI’s Capability Maturity Model-Key Process Area).
a. Defect data is systematically collected and stored in an inspection database.
b. Data is analyzed to improve the product, the process and the effectiveness of the inspection process
c. Focus is on continuous quantitative improvement and also process is measured and controlled.
IX. At the first glance they may look very time consuming. But statistical evaluations have shown that over the whole life cycle of the software development they even save resources and thus money and improve the quality of the product. Refer the diagram below.

In all Peer Review are integral elements of a quality system, which bring high tangible and intangible benefits to organizations and Inspection review is best way to realize the benefits. They are known to deliver high economic value.




Google






















No comments:

Post a Comment