...
Required and Advisory guidelines can be re-categorized into to stricter categories (e.g.for example, Advisory to Required), but only Advisory guidelines can be re-categorized into less strict categories (i.e.that is, to Disapplied).
Deviations Report
...
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-catorizationscategorizations, etcand 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.
...
- 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.
...
- The MISRA Compliance artifact is installed as part of the Automotive Compliance Pack. See Installation for instructions.
- Choose Extension Designer from from the DTP settings menu (gear icon) menu.
- 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 If you are deploying the artifact to an existing service, choose it and continue to the next step 4. If you are adding a new service for the artifact, click Add Service then specify a name for the service and click Confirm. - 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 + button icon to add a new tab) and choose Import from the vertical ellipses menu in the upper right.
- Choose Local> Flows> Workflows> Automotive> Local > Flows > Workflows > Automotive > MISRA Compliance and click Import.
- Click anywhere in the open area to drop the artifact into the service.
- Click Deploy to finish deploying the artifact to your DTP environment.
- Return to DTP and refresh your dashboard.
...
- 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 drop-down menu. A filter represents a set of run configurations that enabled custom views of the data stored in DTP. See See DTP Concepts for additional information.
- Specify a range of time from the Period drop-down menu.
- Specify a range of builds from the Baseline Build and Target Build drop-down menus.
- Enable Create dashboard from a template and choose MISRA C 2023 (MISRA C 2012) Compliance or MISRA C++:2023 Compliance from the menu.
- Click Create to finish adding the dashboard.
...
You can also add the MISRA widgets shipped with the artifact to an an existing dashboard. See 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:
...
| Title | You can rename the widget in the Title field. |
|---|---|
| Filter | Choose a specific filter or Dashboard Settings from the drop-down menu. See Configuring Filters for additional information. |
| Target Build | Choose a specific build from the drop-down menu. The build selected for the entire dashboard is selected by default. See See Using Build Administration for additional information about understanding builds. |
| Category | This setting is available in the MISRA Compliance - Guidelines by Status and MISRA Compliance - Status widgets. Choose an individual category or All from the drop-down menu. |
| Compliance Profile | Specify a compliance profile (see Profile Configuration). The compliance profile data is used to generate some of the compliance reports. |
...
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.for example, a profile with disapplied guidelines, to view your current compliance status. Click on the widget to open the MISRA Compliance Report.
...
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 the MISRA Compliance Report.
MISRA Compliance - Guidelines by Status
...
This widget provides a representation of the highest the highest concentration of static analysis violations per MISRA category (mandatory, required, and advisory). The widget also shows the guidelines (e.g.for example, Dir 4.6, Rule 14.3, etc.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 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-/guideline/category.
Click on a rule to see the violation in the Violations Explorer.
...
You can perform the following actions:
- Use the drop-down menus to sort by MISRA Category or by Compliance status.
- Click on a guideline link in the Guideline column to open the 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 on a link in the # of Violations column to view the violations in the the Violations Explorer.
- Click on a link in the # of Deviations column to view the suppressed violations in the 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.
...
| 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 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.
...
- 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).
- Click on the Prioritization tab in the actions panel and enable the Suppress the selected violations in subsequent analysis runs option.
- In the Reason field, enter
false positivefollowed by any notes related to the violations. - Click Apply to save your changes.
...