Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DTPDEVEL and version 5.4.1

...

A guideline compliance summary (GCS) is the primary record of overall project compliance. The GCS includes an entry for each guideline, its level of compliance, any deviations and/or re-catorizations, etc. The MISRA Compliance Report shipped with the Parasoft MISRA Compliance extension fulfills this requirement.  

See MISRA Compliance 2016: Achieving Compliance with MISRA Coding Standards for additional details and information.

...

The MISRA Compliance Report contains four supporting the following sub-reports:

Table of Content Zone
maxLevel2
minLevel2
locationtop

Guideline Enforcement Plan

The Guidelines Enforcement Plan (GEP)shows which static analysis rules are used to enforce the MISRA guidelines. It is intended to describe how you are enforcing each guideline.

This report uses the data specified in the compliance profile (see Profile Configuration). In the profile, you can add notes to the Compiler field, such as “no errors” or specific compiler settings that will be applied, to document your plan. These notes appear in the Compiler column.

The Analysis Tool column should refer to the static analysis rule. The Manual Review column should contain any manual verifications that will be performed in addition to the automated checks applied by the compiler and analysis tool.You can also click Download PDF to export a printer-friendly PDF version of the report data.

Image Modified

Guideline Re-categorization Plan
Anchor
gap-report
gap-report

If you changed any of the MISRA guideline categories (see Profile Configuration), they will be processed and displayed in this report. You can also click Download PDF to export a printer-friendly PDF version of the report data. Refer to the MISRA standard for additional information about guideline re-categorization plans.

Image Modified

Deviations Report 

Your code can contain violations and still be MISRA-compliant as long as the deviations from the standard are documented and that the safety of the software is unaffected. Deviations are code analysis rules that have been suppressed either directly in the code or in the DTP Violations Explorer. See the C++test documentation for details on suppressing violations in the code. See Suppressing Violations in the Violations Explorer documentation for information about suppressing violations in DTP.

Info
titleSuppressions versus the Do Not Show priority

In versions of DTP prior to 5.4, the only way to suppress static analysis violations was to set the priority to Do Not Show. This approach hides violations, but is not a true, programmatic suppression. You can convert violations flagged with the Do Not Show priority into true suppressions. See Upgrade Notes in the 5.4.0 release notes for details.

Click on the Deviations Report link in the MISRA Compliance report to open the Deviations Report.  

Image Modified

The Deviations Report shows all guideline IDs and headers, but guidelines that have been suppressed will show additional information.

You can filter the report by MISRA category, as well as enable the Only Deviations option to only show deviations. You can also click Download PDF to export a printer-friendly PDF version of the report data.

Build Audit Report

The Build Audit Report shows an overview of code analysis violations, as well as test results and coverage information, associated with the build. This report also allows you to download an archive of the data, which is an artifact you can use to demonstrate compliance with MISRA during a regulatory audit.

In order to download an archive, the build has to be locked. See Build Audit Report for additional details about this report.  

...