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:

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

A guideline enforcement plan (GEP) lists each MISRA guideline to indicate how compliance is checked. In the context of MISRA compliance with Parasoft, the GEP maps MISRA guidelines to Parasoft code analysis rules and DTP functionality.

Guideline Re-categorization Plan

A guideline re-categorization plan (GRP) documents agreed-upon changes to how MISRA guidelines are categorized. Guidelines are categorized as Mandatory, Required, and Advisory. A fourth category, Disapplied, may also be used for instances in which the guideline truly does not apply.

All mandatory guidelines must be followed to achieve compliance. Required guidelines should be followed, but documented exceptions are allowed. Advisory guidelines are considered best practice.

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).

Deviations 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.

Guideline Compliance Summary

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-categorizations, and so on. The MISRA Compliance Report shipped with the Parasoft MISRA Compliance extension fulfills this requirement.

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

Prerequisites

This compliance artifact supports code analysis executed by C/C++test (Standard or Professional) with the Flow Analysis license feature enabled.

Process Overview

1. Analyze code with C/C++test using the MISRA C 2023 or MISRA C++:2023 test configuration and report violations to DTP.
2. Install the Automotive Compliance Pack into DTP Extension Designer, which also installs the MISRA Compliance assets.
3. Deploy the MISRA DTP Workflow to your DTP environment and add the MISRA dashboard and widgets to your DTP interface.
4. Interact with the widgets and reports to identify code that needs to be fixed, as well as print out the reports for auditing purposes.

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. The following assets are included:

• Compliance categories and guidelines: These files add the MISRA Compliance option to DTP interfaces, such as widget configuration settings.  
• Test 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. 
  
• Dashboard template: This file enables you to add the MISRA C 2023 or MISRA C++:2023 dashboard 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.
• 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.   

Installing and Deploying the DTP Workflow

1. The MISRA Compliance artifact is installed as part of the Automotive Compliance Pack. See Installation for instructions.
2. Choose Extension Designer from the DTP settings (gear icon) menu.
   
3. Click the Services tab and choose a service category. You can deploy the artifact to an existing service or add a new service. We recommend deploying compliance pack artifacts to a service within the DTP Workflows category. 
   
   The number of artifacts deployed to a service affects the overall performance (see Extension Designer Best Practices for additional information). If you are deploying the artifact to an existing service, choose it and continue to the next step. If you are adding a new service for the artifact, click Add Service then specify a name for the service and click Confirm.
4. The tabs interface within the service allows you to organize your artifacts. Organizing your artifacts across one or more tabs within the service does not affect the performance of the system. Click on a tab (or click the + icon to add a new tab) and choose Import from the vertical ellipses menu in the upper right.
   
5. Choose Local > Flows > Workflows > Automotive > MISRA Compliance and click Import.
6. Click anywhere in the open area to drop the artifact into the service.
7. Click Deploy to finish deploying the artifact to your DTP environment. 
8. Return to DTP and refresh your dashboard. 

You will now be able to add the MISRA dashboard and widgets, as well as access MISRA reports.  

Adding the MISRA Dashboard

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 MISRA C 2023. The information in this section is also covered in the Adding Dashboards chapter.

1. Click Add Dashboard and specify a name when prompted.
2. (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.  
3. Enable Create dashboard from a template and choose MISRA C 2023 (MISRA C 2012) Compliance or MISRA C++:2023 Compliance from the menu.
   
4. 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:

Specify the following information when adding the MISRA Compliance - Percentage, MISRA Compliance - Status, and MISRA Violations by Category - TreeMap widgets:

Viewing MISRA Compliance Widgets 

Each widget provides a different view of the test and analysis data to help you achieve MISRA compliance. The following widgets are shipped with the MISRA Compliance DTP Workflow.

MISRA Compliance - Status Widget

This widget shows you the general state of compliance. You can add multiple instances of the widget configured to use a different profile, for example, a profile with disapplied guidelines, to view your current compliance status. Click on the widget to open the MISRA Compliance Report. 

The widget can show five possible states:

• 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 and re-run 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.

MISRA Compliance - Percentage Widget

This widget shows the completeness of MISRA compliance as a percentage. Completeness is based on number of guidelines being enforced in the profile. Click the widget to open the MISRA Compliance Report.

MISRA Compliance - Guidelines by Status

This widget shows the compliance status for individual guideline categories (Mandatory, Required, Advisory) or for all categories.

The pie chart can represent up to five different guideline statuses for the selected category:

You can perform the following actions:

• 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 Report filtered by the category selected in the widget.

MISRA Violations by Category - TreeMap 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.

Click on a rule to see the violation in the Violations Explorer.

Viewing MISRA Compliance Reports

The MISRA Compliance Report provides an overview of your MISRA compliance status and serves as the primary document for demonstrating compliance.

You can perform the following actions:

• Use the menus to sort by MISRA Category or by Compliance status.
• Click a guideline link in the Guideline column to open the Guideline Enforcement Plan. The link goes directly to the specific guideline so that you can review the Parasoft code analysis rule or rules enforcing the guideline. 
• Click a link in the # of Violations column to view the violations in the Violations Explorer.
• Click a link in the # of Deviations column to view the suppressed violations in the Violations Explorer.
• Open one of the MISRA Compliance sub-reports.
• Click Download PDF to export a printer-friendly PDF version of the report data. If you added a custom graphic to DTP as described in Adding a Custom Graphic to the Navigation Bar, the PDF will also be branded with the graphic. 

The MISRA Compliance Report contains the following sub-reports:

Suppressions and False Positives

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 Report. 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 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.

False Positives

If the tool incorrectly reports a violation, you can mark it as a false positive, which will filter the violations out of the compliance widgets and reports. 

1. Open the Violations Explorer view and choose a violations in the search results table. You can access the Violations Explorer view by clicking on a link in the #of Violations column in the main MISRA Compliance Report (see Viewing MISRA Compliance Reports).
2. Click the Prioritization tab in the actions panel and enable Suppress the selected violations in subsequent analysis runs.
3. In the Reason field, enter false positive followed by any notes related to the violations.
4. Click Apply to save your changes. 

When DTP receives the next build, suppression information will be processed. If the message in the Suppression details field begins with 'false positive', the violation will be excluded from MISRA Compliance reports, including from the Deviation report. 

You can also mark violations as false positives in C/C++test by applying a suppression and specifying false positive as the suppression reason. The reason must begin with false positive in order to be excluded from MISRA Compliance reports. Refer to the C/C++test documentation for details on how to suppress violations. 

Profile Configuration

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++ 2023. 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-categoriziation. 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.

We recommend creating a copy of the default profile and modifying the copy. 

1. Click Export Profile to download a copy. 
2. Rename the copy and click Import Profile. 
3. Browse for the copy and confirm to upload.  
4. 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. 

5. Click Save.