Case Study: Spirent achieves higher code quality and fewer field errors with Perforce Klocwork

A Perforce Case Study

Preview of the Spirent Case Study

Ensuring Code Quality, Reducing Field Errors with Static Code Analysis

Spirent Communications, which builds software used by major network communications providers and equipment manufacturers, needed a better way to ensure code quality and avoid costly field errors. To augment manual testing and replace a static analysis tool that was difficult to scale across its large, distributed code base, Spirent chose Perforce Klocwork Insight.

Perforce implemented Klocwork Insight into Spirent’s development workflow so developers could detect defects earlier, directly in their IDEs, before code check-in. The result was fewer late-stage and field-found bugs, faster repairs, and stronger ROI: Spirent estimated field fixes cost about $962 per defect versus $96 with static analysis, making early detection far more cost-effective.


View this case study…

Spirent

Marc Hornbeek

Engineering Manager, SCM Systems


Perforce

172 Case Studies