...
| Table of Content Zone | ||||||
|---|---|---|---|---|---|---|
| ||||||
Guideline Enforcement PlanThe 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.
Guideline Re-categorization Plan Anchor |
If you changed any of the MISRA guideline categories (see Profile Configuration), they will be processed and displayed in this report. Refer to the MISRA standard for additional information about guideline re-categorization plans.
By default, this report does not include the compiler used to build the code. You can add the compiler to your profile so that it appears in this report. See Profile Configuration for information on modifying the profile. Deviations ReportClick on the Deviations Report link in the MISRA Compliance report to open the Deviations Report.
The Deviations Report shows all guideline IDs and headers, but guidelines that have been suppressed will show additional information. You can perform the following actions:
Build Audit ReportThe main MISRA Compliance Report links to the Build Audit Report, which provides access to code analysis, test results, and coverage information sent to DTP under the selected 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. The Build Audit Report is a standard report shipped with DTP and is not specific to MISRA Compliance.
In order to download an archive, the build has to be locked. See Build Audit Report for additional details about this report. |
Suppressions and
...
Deviations
You may determine that some violation are acceptable because, for example, they are associated with non-safety-critical parts of the application or will not lead to actual defects when the application runs. In these instances, MISRA allows you to suppress violations and document a rationale. These violations These suppressions are added to the Deviations Report. False positives, however, are violations reported in error. The standard also allows you to mark violations as false positives when the code analysis tool incorrectly reports them.
Suppressions
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 violations that have been suppressed either in C/C++test or in the DTP Violations Explorer. See the C/C++test documentation for details on suppressing violations using the C/C++test suppression mechanism. See Suppressing Violations in the Violations Explorer documentation for information about suppressing violations in DTP.
...