Review Techniques
Major Errors
the number of errors found that can be categorized as major (requiring more than some pre-specified effort to correct)
Minor errors
the number of errors found that can be categorized as minor (requiring less than some pre-specified effort to correct)
Defect density
= Errtot / WPS Work product Size, WPS- a measure of the size of the work product that has been reviewed (e.g, the number of UML models, or the number of document pages, or the number of lines of code)
What do we look for?
Errors and defects. Error- a quality problem found before the software is released to end users. Defect- a quality problem found only after the software has been released to end users.
Informal Reviews
Informal Reviews include: A simple desk check of a software engineering work product with a colleague. A casual meeting (involving more than 2 people) for the purpose of reviewing a work product, or the review-oriented aspects of pair programming. Pair programming- encourages continuous review as a work product(design or code) is created. The benefit is immediate discovery of errors and better work product quality as a consequence.
Review Meeting "Players"
Producer - The individual who has developed the work product. Review Leader- evaluates the product for readiness, generates copies of product materials, and distributes them to two or three reviewers for advance preparation. Reviewers(s) - expected to spend between one and two hours reviewing the product, making notes, and otherwise becoming familiar with the work. Recorder - reviewer who records (in writing) all important issues raised during the review.
Formal Technical Reviews
The objectives of an FTR are: To uncover errors in function, logic, or implementation for any representation of the software. To verify that the software under review meets its requirements. To ensure that the software has been represented according to predefined standards. To achieve software that is developed in a uniform manner. To make projects more manageable. The FTR is actually a class of reviews that includes walkthroughs and inspections.
What are reviews?
They are: A meeting conducted by technical people for technical people. A technical assessment of a work product created during the software engineering process A software quality assurance mechanism A training ground. They are not: A project summary or progress assessment A meeting intended solely to impart information A mechanism for political or personal reprisal.
Metrics - Effort
Total review effort Ereview = Ep + Ea + Er where... Preparation effort, Ep - the effort required to review a work product prior to the actual review meeting. Assessment effort, Ea - the effort that is expending during the actual review Rework effort, Ef- The effort that is dedicated to the correction of those errors uncovered during the review.