Code Inspection: why, when and what
Research over five decades has consistently shown that code inspection is remarkably cost-effective when compared to other ways to find the defects in computer software. Take a look at the answers to these three questions:
Why should you inspect software?
- Code Inspection Pays For Itself—Software code inspection offers both immediate and long-term return on investment.
- Code Inspection Powers Up Testing Strategies—Software code inspection is more cost-effective and isolates defects more efficiently than testing. Combine inspection and testing to get the best strategy for defect removal.
- Code Inspection Boosts Productivity—When preparing for code reviews, developers find the majority of bugs that would otherwise be found by testers and users.
- Code Inspection Makes Testing Cheaper—Software code inspection identifies defect indicators from Day One, making it more cost-effective than functional and system testing.
- Code Inspection Increases Agility—Regular code inspection helps make software more receptive to change. Improve the maintainability of software so that you can implement changes in a uniform and consistent manner.
When should you inspect software?
- Inspect during development—Software maintenance starts from day one of a project and inspected software is less expensive to alter, fix and maintain.
- Inspect before testing—Software should be inspected before it is tested: when it comes to finding defects, inspection is much cheaper and faster.
What should you look for?
- Entry Level Compliance—Look for Defect Indicators which are easy to find but are correlated with instability, errors and unnecessary complexity.
- Professional Software Development—Look for Defect Indicators which have been correlated with low reliability, design flaws and high maintenance costs.
- Industry Best Practice—Perform code walkthroughs to ensure that inappropriate techniques have been avoided.