The benefits of finding and fixing defects early in the Software Development Lifecycle (SDLC) are widely acknowledged. And these benefits are not limited to quality, but simultaneously have a positive impact on schedule and cost.
There is also a large body of research* into the effectiveness of different tools and methodologies in identifying and removing defects (Defect Removal Efficiency (DFE)) at the different stages in the SDLC. The key conclusion from these studies is the fact that effective code inspection (as opposed to ad-hoc code reviews) are one of the most effective means to identify and remove defects (typically these identify 60-70% of all defects) and they achieve this at the earliest possible stage in the development process. The ideal approach is early and frequent inspections, which approach a state of CCI.
We have identified three primary areas that determine the effectiveness of code inspection: the inspection criteria, the inspection process and the enabling tools.
A brief scan of the inspection criteria immediately reveals the appropriateness of Static Analysis – PRQA’s core competency – as the underlying technology to cover these.
In addition, the other critical aspects of the broader code inspection process need to be addressed, including:
Continuous Code Inspection – Advancing Software Quality At Source webinar recording
Try our products and request an evaluation
Read our white papers about CCI and other software quality issues.
Contact us for more info
* eg: see “A Survey of Software Inspection Technologies” by Oliver Laitenberger’s for a consolidated analysis of ~120 articles and reports on code inspections.