Table of Contents maxLevel 1
MISRA began as a set of technical guidelines to help organizations create safety-critical software for automotive applications. The standard has since been adopted by embedded software development organizations in other safety-critical industries. MISRA C:2012 is the most recent implementation for development using the C programming language and includes 159 base guidelines. Amendment 1 is a supplemental set of 14 guidelines that expanded the total to 173.
The Parasoft MISRA Compliance Pack configures code analysis to run against MISRA guidelines and conforms the data to meet the following reporting specifications defined in MISRA Compliance 2016.
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.
Required and Advisory guidelines can be re-categorized into to stricter categories (e.g., Advisory to Required), but only Advisory guidelines can be re-categorized into less strict categories (i.e., to Disapplied).
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-catorizations, etc.
See MISRA Compliance 2016: Achieving Compliance with MISRA Coding Standards for additional details and information.
How Parasoft Supports MISRA C:2012 Compliance
In addition to the MISRA Compliance Pack, the following Parasoft products are required:
- Development Testing Platform (DTP) Enterpise 5.3.2 or later
- DTP Extension Designer 5.3.2 or later (included with the DTP Enterprise license)
- C/C++test Desktop or C/C++test DTP Engine 10.3.2 with the Flow Analysis license feature enabled
- Deploy the MISRA Compliance Pack configuration files to DTP.
- Connect an instance of C/C++test to DTP. This enables C/C++test to analyze code according to MISRA guidelines by using the configurations stored on DTP, as well as report code analysis data to DTP for processing.
- Install, configure, and deploy the MISRA Compliance artifact into DTP Extension Designer. This enables DTP to process the code analysis data to output the compliance deliverables.
- Analyze the project with C/C++test using the MISRA configurations and report violations to DTP.
- The MISRA Compliance extension then generates DTP dashboard widgets and reports using the data.
- Interact with the widgets and reports to identify code that needs to be fixed, as well as print out the reports for auditing purposes.
What's Included in the Parasoft MISRA Compliance Pack
The Parasoft MISRA Compliance pack helps you create the documentation required for demonstrating compliance with MISRA C:2012. Download and unzip the pack to access the following artifacts.
This file remaps the output from the built-in C/C++test static analysis rules to the appropriate MISRA guidelines. The rule map does not change what the rules analyze or how the analyze the code. When applying the MISRA Compliance rule map, violations are reported with new rule IDs. As a result, violations will appear as new violations and any existing suppressions and/or prioritization will not apply to the remapped violations.
This file is located in the <PACK>/MISRA Rules directory.
MISRA C 2012 Compliance.properties
This is the test configuration that enables the rules specified in the rule map to run during code analysis. All Parasoft tools analyze code according to which rules are specified in a test configuration. C/C++test includes test configurations specifically for checking software security, for example. The MISRA Compliance Pack includes a test configuration that enables the Parasoft rules that validate MISRA’s guidelines.
This file is located in the <PACK>/MISRA Rules directory.
This is the DTP Workflow you must install and deploy in Extension Designer. It extends DTP’s data processing functionality to produce MISRA-specific dashboard widgets and reports. It helps you track compliance status and document guideline enforcement, deviations, and rule re-categorization.
This artifact is located in the <PACK>/Extension Designer Artifact directory
MISRA2012-Category.xml and MISRA2012-Guideline.xml
These configuration files enable additional compliance categories in DTP. The additional categories provide a place for the MISRA-specific dashboard widgets that are shipped with the MISRA Compliance extensions. DTP must be restarted after installing these.
These files are located in the <PACK>/DTP/conf/compliance directory.
This dashboard template file provides a DTP dashboard containing a pre-defined set of MISRA-related widgets. Refresh your browser after installing the template.
This file is located in the <PACK>/DTP/grs/dashboard directory.
MISRA C:2012 Compliance Data Sheet
This document shows the mapping between C/C++test rules and the guidelines they support. It shows the original C++test rule and the remapped rule.
Configuring DTP for MISRA Compliance Reporting
MISRA guidelines are defined as either "rules" or "directives" and can be categorized as Mandatory, Required, or Advisory. Parasoft static and flow analysis rules report violations according to a category (e.g., Possible Bug, Interoperability, etc.) and severity (I.e. 1-5). In the MISRA rulemap, the analysis rules are remapped so that the Parasoft category matches the MISRA guideline and output presented in both static HTML reports and DTP maps to MISRA guidelines. Additionally, the MISRA Compliance test configuration enables C/C++test to execute only the rules related to the remapped MISRA rules.
According to MISRA C:2012. there are four guidelines that cannot be statically analyzed. As a result, DTP will report 100% compliance against 169 guidelines.
Configuring Extension Designer
Installing the MISRA Compliance DTP Workflow
- Enterprise Pack artifacts are usually downloaded and installed from the Parasoft Marketplace, but the MISRA Compliance workflow must be uploaded manually. See Uploading Artifacts for instructions.
- Deploy the artifact after installation. See Deploying Services for instructions.
The MISRA Compliance DTP Workflow ships with a model profile (see Working with Model Profiles) configured to monitor compliance with MISRA C:2012. The profile include information necessary for generating compliance reports (see Viewing MISRA Compliance PackReports). It includes a field for you to specify your compiler, as well as guideline categorization and re-categoriziation information. 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 MISRA Compliance PackGuideline Re-categorization Plan.
We recommend creating a copy of the default profile and modifying the copy.
- 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:
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 MISRA Compliance Pack Guideline Re-categorization Plan. Making required and advisory guidelines stricter is acceptable.
- Click Save.
Add the MISRA Compliance widgets to your dashboard (see Adding Widgets). The widgets will appear in the Compliance category in the Add Widget overlay:
|Title||You can rename the widget in the Title field.|
|Filter||Choose a specific filter or Dashboard Settings from the drop-down menu. See Creating and Managing Filters for additional information.|
|Period||Choose a specific time period or Dashboard Settings from the drop-down menu.|
|Build||Choose a specific build from the drop-down menu. The last build is selected by default. See Using Build Administration for additional information about understanding builds.|
|Category||This setting is available in the MISRA Compliance Pack- Guidelines by Status widget. Choose an individual category or All from the drop-down menu.|
|Compliance Profile||Specify a compliance profile (see MISRA Compliance PackProfile Configuration). The compliance profile data is used to generate some of the compliance reports.|
Viewing MISRA Compliance Widgets
Each widget provides a different review 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, e.g., 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:
Code meets all guidelines with no deviations or changes to the guideline categories.
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 MISRA Compliance PackDeviations Report for additional information about deviations).
Compliant with Violations
Code meets all mandatory and required guidelines, but contains violations for advisory guidelines.
Code does not meet all mandatory and/or required 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 on the widget to open the MISRA Compliance Report.
MISRA Compliance - Guidelines by Status
This widget shows the compliance status for an individual guideline category (Mandatory, Required, or Advisory).
|Green||Guidelines that your code is complaint.|
Guidelines that your code is deviating from but are still considered compliant.
A deviation is when the guideline is not being followed according to the Parasoft static analysis rule, but is considered acceptable because it does not affect the safety of the software. Deviations represent Parasoft static analysis rules that have been suppressed.
Guidelines that your code is considered compliant with, even though the static analysis rules that enforce them contain violations.
Only advisory guidelines can have this status.
|Red||Guidelines that your code is not compliant with.|
|Maroon||Guidelines that are specified in the profile, but the Parasoft rule that enforces the guideline are missing.|
- 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 MISRA Compliance PackDeviations 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 (e.g., Dir 4.6, Rule 14.3, etc.) 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-guidline-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.
|Table of Content Zone|
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 MISRA Compliance PackProfile 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
If you changed any of the MISRA guideline categories (see MISRA Compliance PackProfile Configuration), they will be processed and displayed in this report. Refer to the MISRA standard for additional information about guideline re-categorization plans.
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 with comments or in the DTP Violations Explorer by setting the prioritization to Do Not Show.
Click 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 also filter the report by MISRA category.
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.