The Parasoft MISRA Compliance artifact is a set of assets for your DTP infrastructure that enable you to readily demonstrate compliance with MISRA development guidelines. This artifact ships with the Automotive Compliance Pack. Contact your Parasoft representative for information about downloading and licensing the compliance pack.
In this section:
Table of Contents maxLevel 2
Overview
The Parasoft MISRA Compliance artifact configures code analysis to run against MISRA guidelines and conforms the data to meet the following reporting specifications defined in MISRA Compliance 2020.
Guideline Enforcement Plan
...
Required and Advisory guidelines can be re-categorized into to stricter categories (for example, Advisory to Required), but only Advisory guidelines can be re-categorized into less strict categories (that is, to Disapplied).
...
Deviation Report
A "deviation" is a documented violation of the guideline and supporting rationale for allowing the violation to remain. In the context of MISRA compliance with Parasoft, deviations take the form of suppressed code analysis violations. Your project can have deviations and still be considered compliant if the deviations are documented in the report and do not impact safety.
...
See MISRA Compliance 2020: Achieving Compliance with MISRA Coding Standards for additional details and information.
Prerequisites
Supported Guidelines
| Anchor | ||||
|---|---|---|---|---|
|
The MISRA Compliance artifact supports the following specific MISRA implementations:
- MISRA C 2023
- MISRA C 2025
- MISRA C++ 2023
Prerequisites
This compliance artifact supports code analysis executed by CThis compliance artifact supports code analysis executed by C/C++test (Standard or Professional) with the Flow Analysis license feature enabled.
...
- Analyze code with C/C++test using the MISRA C 2023 or MISRA C++:2023 test a corresponding MISRA test configuration and report violations to DTP.
- Install the Automotive Compliance Pack into DTP Extension Designer, which also installs the MISRA Compliance assets.
- Deploy the MISRA DTP Workflow to your DTP environment and add the MISRA dashboard and widgets to your DTP interface.
- Interact with the widgets and reports to identify code that needs to be fixed, as well as print out the reports for auditing purposes.
| Note | ||
|---|---|---|
| ||
DTP reports compliance against MISRA C 2023 and MISRA C++:2023 the corresponding MISRA compliance guidelines that are enforceable with Parasoft static analysis and enabled in the MISRA C 2023 and MISRA C++:2023 compliance reporting.corresponding compliance reporting. |
MISRA Compliance Extension MISRA Compliance Extension Assets
The Parasoft MISRA Compliance artifact helps you create the documentation required for demonstrating compliance with MISRA C 2023 or MISRA C++:2023 supported MISRA guidelines. The following assets are included:
- Compliance categories and guidelines: These files add the MISRA Compliance option to DTP interfaces, such as widget configuration settings. The following compliance categories and guidelines are included in the artifact:
- MISRA C:2023 Categories
- MISRA C:2023 Guidelines
- MISRA C++:2023 Categories
- MISRA C++:2023 Guidelines
- MISRA C:2025 Categories
- MISRA C:2025 Guidelines
- Test configurations: These files specify which code analysis rules to execute. You can configure CTest configurations: These files specify which code analysis rules to execute. You can configure C/C++test to run the local test configuration or to run the test configuration uploaded to DTP when the compliance pack is installed.
The following test configurations are included in the artifact:- MISRA C 2023 (MISRA C 2012)
- MISRA C++ 2023
- MISRA C 2025
- Dashboard Dashboard template: This file enables you to add the MISRA C 2023 or MISRA C++:2023 dashboard corresponding MISRA compliance guidelines that includes a pre-defined set of MISRA-related widgets.
- Model and profile: These files drive the report compliance reports necessary for demonstrating MISRA compliance. See Profile Configuration for additional information.
- The following template files are included in the artifact:
- MISRA C 2023 (MISRA C 2012) Compliance
- MISRA C++ 2023 Compliance
- MISRA C 2025 Compliance
- Model and profile: These files drive the report compliance reports necessary for demonstrating MISRA compliance. See Profile Configuration for additional information. The following models and profiles are included in the artifact:
- Models
- MISRA Compliance
- Profiles
- MISRA C 2023 (MISRA C 2012)
- MISRA C++ 2023
- MISRA C 2025
- Models
- DTP Workflow: This is the DTP Enterprise Pack artifact that includes the widgets, reports, and processing logic that show violations in the context of MISRA guidelines.
...
The MISRA dashboard is configured to show custom widgets shipped as part of the MISRA artifact. The dashboard also contains select native DTP widgets configured to show code analysis data within the context of the corresponding MISRA C 2023guidelines. The information in this section is also covered in the Adding Dashboards chapter.
- Click Add Dashboard and specify a name when prompted.
- (Optional) You can configure the default view for the dashboard by specifying the following information:
- Choose the filter associated with your project in the filter menu. A filter represents a set of run configurations that enabled custom views of the data stored in DTP. See DTP Concepts for additional information.
- Specify a range of time from the Period menu.
- Specify a range of builds from the Baseline Build and Target Build menus.
- Enable Create dashboard from a template and choose MISRA C 2023 (MISRA C 2012) Compliance or MISRA C++:2023 Compliance from a MISRA compliance guideline from the menu.
- Click Create to finish adding the dashboard.
See Viewing MISRA Compliance Widgetsfor information about understanding the widgets shipped with the MISRA compliance artifact.
Manually Adding Widgets to Your Existing Dashboard
You can also add the MISRA widgets shipped with the artifact to an existing dashboard. See Adding Widgets for general instructions on adding widgets to a dashboard. After deploying the artifact, the MISRA widgets will appear in the MISRA category in the Add Widget overlay:
for information about understanding the widgets shipped with the MISRA compliance artifact.
Manually Adding Widgets to Your Existing Dashboard
After deploying the artifact, you can add MISRA widgets to a dashboard. See Adding Widgets for more information about this process. MISRA widgets can be found in the MISRA category.
You can configure the following widget settingsSpecify the following information when adding the MISRA Compliance - Percentage, MISRA Compliance - Status, and MISRA Violations by Category - TreeMap widgets:
| Scroll Table Layout | ||
|---|---|---|
|
...
- Mouse over a pie slice to view details.
- Click on a section to open the MISRA Compliance report filtered by the category and status.
- Click on the number of violations counter to open the MISRA Compliance report filtered by the category and status.
- Click on the number of deviations counter to open the Deviations Deviation Report filtered by the category selected in the widget.
...
This widget provides a representation of the highest concentration of static analysis violations per MISRA category (mandatory, required, and advisory). The widget also shows the guidelines (for example, Dir 4.6, Rule 14.3, and so on) within each category in which violations were reported. Finally, the Parasoft rule(s) enforcing each guideline are also presented. Tiles are proportional to the number of static analysis violations reported for each rule.
The widget uses the hierarchy established in the model profile to correlate rules, guidelines, and categories. You can mouse over a tile in the widget to view the number of violations associated with each rule/guideline/category.
...
- Compliant: Code meets all guidelines with no deviations or changes to the guideline categories.
- Not Compliant: Code does not meet all mandatory and/or required guidelines.
- Missing rule(s) in analysis: Parasoft code analysis rules documented in your profile were not included in the specified build. Make sure all rules are enabled in C/C++test the Parasoft tool and re-run the analysis.
- Compliant with Deviations: Code meets all guidelines, but deviations have been applied. Deviations are violations that you have determined to be acceptable (see Suppressions and False Positives for additional information about deviations).
- Compliant with Violations: Code meets all mandatory and required guidelines but contains violations for advisory guidelines.
- No Rules Enabled: There are no Parasoft code analysis rules mapped to the guideline.
...
| 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 PlanAnchor |
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 ReportDeviation Report
Click the Deviations Deviation Report link in the MISRA Compliance report to open the Deviations Deviation Report. The Deviations Deviation Report shows all guideline IDs and headers, but guidelines that have been suppressed will show additional informationIDs and headers with deviations. 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 refer to code analysis violations that you have determined to be acceptable. False positives, however, are violations that match the coding pattern as described in the analysis rule but do not lead to actual defects when the application runs. MISRA allows you to suppress violations and document a rationale. These violations are added to the Deviations Deviation Report. The standard also allows you to mark violations as false positives when the code analysis tool incorrectly reports them.
...
The MISRA Compliance DTP Workflow ships with model profiles (see Working with Model Profiles) configured to monitor compliance with MISRA C 2023 and MISRA C++ 2023the corresponding MISRA compliance guideline. The profile includes information necessary for generating compliance reports (see Viewing MISRA Compliance Reports), such as fields for specifying your compiler and guideline categorization and re-categoriziationcategorization. You You can modify the profile if you want to re-categorize guidelines to meet you specific goals or specify additional metadata for your reports. Changes will be reflected in the Guideline Re-categorization Plan.
...
- Click Export Profile to download a copy.
- Rename the copy and click Import Profile.
- Browse for the copy and confirm to upload.
- Click on a guideline and specify your changes. If you are changing MISRA categories, the following strings are acceptable:
- Mandatory
- Required
- Advisory
Disapplied
Making Mandatory and/or Required guidelines less strict will result in an invalid use of the guideline in the Parasoft Guideline Re-categorization Plan Report per the requirements outlined by MISRA (see Guideline Re-categorization Plan). Making required and advisory guidelines stricter is acceptable.
- Click Save.