The ability to discover defects is great but a tool should also facilitate clear and informative reporting, allowing users to fix and manage defects efficiently (e.g. deviations for MISRA Compliance Report/Matrix).

Klocwork uses a Client-Server architecture to realise this, as shown in the diagram below:

Klocwork Architecture

Klocwork Server

Klocwork’s server consists of two parts: a web interface running over an SQL database and analysis tools to run full-system analyses (that publish results to the SQL database). The analysis tools are typically installed on your build machines to run analyses after your project build. The web interface allows you to manage Klocwork findings, such as deviations and suppressions, and also to generate reports and connect to 3rd party tools (e.g. task management, dashboards).

Klocwork Client

The Client tools come as integrations with Visual Studio and Eclipse, or as a command line utility. The point is; developers check code as it is being written, to identify, fix and suppress issues. This is the absolute best place to do this.

Klocwork and CI

Klocwork’s Continuous Integration (CI) capability enables your organisation to identify and communicate errors faster, without waiting for nightly builds. By identifying and communicating issues faster, developers can fix problematic code earlier.

As developers update and commit code, the CI build system picks up the changes and performs many small, incremental builds throughout the day. Instead of waiting for nightly builds, Klocwork CI analyses the new code and notifies developers of problems right away. For more information on Klocwork with CI click the link below or see the Klocwork Community Jenkins Plugin.

KlocworkKlocwork and ISO 26262 – Klocwork for a DeveloperKlocwork and Continuous Integration