Let’s face it, we all know that fixing issues early is better—it’s easier and less expensive. That’s why we do developer test. But some developers think that static analysis tools are less of a hassle than code review and will find enough of the bugs anyway. While static analysis tools are great at automatically checking code against pre-defined criteria, they only find certain kinds of violations of good coding practice. Peer code review finds additional classes of defects, the kinds of problems that only skilled humans excel at finding.
Join Capers Jones and Tom McCabe as they show you the metrics that prove that when used together, static analysis and code review find more bugs and inconsistencies than either technique alone.
“A synergistic combination of formal inspections, static analysis, and formal testing can achieve combined defect removal efficiency levels of 99%.”
- Capers Jones, Combining Inspections, Static Analysis, and Testing to Achieve Defect Removal Efficiency Above 95%, January 2012.
Attend this Webinar and learn:
Register for this exciting Webinar event now!
|
|
Capers Jones Capers Jones and his colleagues from SPR have collected historical data from hundreds of corporations and more than 30 government organizations. This historical data is a key resource for judging the effectiveness of software process improvement methods. | |
|
|
Tom McCabe Thomas J. McCabe is a mathematician, entrepreneur, and author. He is the founder of McCabe Software (McCabe.com) which he grew to 175 people with European subsidiaries. Tom has authored three books and is highly published in computer science; he lectures in the US and overseas on software development as well as on entrepreneurship. |