have confirmation bias so they are blind to some trouble spots in their work and other people do not have the same blind spots.The author points out that code inspection has higher effectiveness compared to software testing or unit testing and the defect discovered by reviews are different from testing.
Technical reviews help in assessing the progress and quality of the project.
The author then discuss about inspections and how they differ from other kind of reviews. The author then discuss different roles played during an inspection including:
- Moderator
- Author
- Scribe
- Reviewer
- Management
The author then outlines the general procedure for inspection:
- Planning
- Overview
- Preparation
- Inspection meeting
- Inspection report
- Rework
- Follow-up
- Third-hour meeting
- Fine-tuning the inspection
The author then discusses about other kind of reviews including:
- Walkthroughs: The author presents several things common for all walkthroughs
- The purpose of a walkthrough is to improve the quality of a program rather than assess it.
- It is a chance for senior programmers to pass on experience and corporate culture to junior programmers.
- The author then compares inspections with walkthroughs on several properties.
- Code Reading: The author cites a study saying that more defects are discovered in code reading than in testing per hour of effort. It is different from walkthrough or review such that there is no meeting done.
- Dog and Pony shows: The product is demonstrated to a customer.
No comments:
Post a Comment