1. Static analysis of the project, code, documents
and design etc. 2. Way of formal verifications. What are Reviews ? A process or meetings during which a work product or set of work products, is presented to project personnel, managers, users, customers and interested parties for comment or approval. Why Bother, We Test Don’t We? Reviews reduce rework. Reviews are proactive tests. Reviews are training. Who benefits? Technical review provide defect information to the author. Can be applied to untestable products. Can be applied earlier. Complements(does not supplant) testing. Formal Technical Review: True formal reviews are a well-defined activity. Well-defined process. Well-defined roles. Well-defined objectives. Well-defined metrics. Who, What And When Who decides what should be reviewed? o Senior Technical Personnel o Project Leader What should be reviewed? o Work Product When should reviews be planned? o Specify review method and target or work product in software development plan and quality plan Industrial Experience with Formal Technical Reviews:
AetnaInsurance Company oReviews found 82% of errors. o25% cost reduction. Software Inspections:
Software Inspections started in 1970s.
Inspections means formal verifications of work product. Software Inspections are considered a best industry practice for detecting software defects early and learning about software artifacts. It is important to note that inspections are a way to remove defects at a very low cost. Objectives of Inspections: Our objective with Inspections is to reduce the cost of achieving Quality by finding and removing defects earlier and at a lower cost. Stages in Software Inspection Process: The stages in the inspection process are: 1. Planning. 2. Overview Meeting. 3. Preparation. 4. Inspections Meeting. 5. Rework. 6. Follow-up.