Checking MISRA Compliance
There are several MISRA checker tools, each one producing results in a specific format.
To provide a standard MISRA compliance assessment, Squore introduces a generic feature, part of the standard Squore/Software Analytics rating model.
The Squore monitoring solution process is broken down into three steps:
Aggregation of MISRA Checking Results from Various Tools
As of today, Squore provides standard plugins for reports generated by tools such as Klocwork, PC-Lint, QA-C, Polyspace, …
This plugin technology is extensible, meaning that results from other tools can be aggregated into Squore when necessary.
Rating of Each Project Component with Respect to MISRA Compliance
Squore/Software Analytics is able to check MISRA compliance for the following versions:
- MISRA 2004: 146 rules in the ruleset
- MISRA 2008: 228 rules in the ruleset
- MISRA 2012: 159 rules in the ruleset
The ruleset contents can be adapted to any project rated with Squore. This means that Squore can be tailored to work with a subset of MISRA rules. The compliance (and rating) will be based on this configuration.
Dashboard Providing Misra-Related Monitoring Functions
Track MISRA Findings
The traceability feature allows us to attach each finding to the source code element it was found on.
In this example, MISRA findings found by Polyspace are shown, you can see that rule “R 16.7” was found in file “apsm_uds.c” at line 1918.
Track MISRA Metrics
The rating model computes MISRA rule violations counts, broken down by their severity.
The compliance ratio depends on the ruleset definition, and the violated rules.
Note that these metrics are computed.
Achieving Compliance to MISRA C and MISRA C++