...
- The AUTOSAR Compliance artifact is installed as part of the Automotive Compliance Pack. See Installation for instructions.
- Choose Extension Designer from the DTP settings menu (gear icon).
- Click the Services tab tab and choose a service category. You can deploy the artifact to any service category you want. You can also create a new category (see Working with Services), but we recommend deploying compliance pack artifacts to the DTP Workflows service category.
You can deploy the artifact to an existing service or add a new service. 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 (see Extension Designer Best Practices for for additional information. Choose ). If you are deploying the artifact to an existing service, choose it and continue to step 6 or click Add Service.Specify 4. If you are adding a new service for the artifact, click Add Service then specify a name for the service and click click Confirm.
- The tabs interface within the service allows you to organize your artifacts within the service. 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 the + button to add a new tab) and choose Import from the vertical ellipses menu in the upper right.
- Choose Local> Flows> Workflows> Automotive> AUTOSAR 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 browser.
...
- 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 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 the Create dashboard from a template option and choose AUTOSAR C++14 Compliance from the drop-down menu.
- Click Create to finish adding the dashboard.
In addition to the AUTOSAR-specific widgets shipped with the artifact (see Viewing AUTOSAR Compliance Widgets), the dashboard includes three implementations of the native Categories - Top 5 Table DTP widget. The widgets are configured to use the AUTOSAR C++14 compliance categories shipped with the artifact.
Top 5 AUTOSAR Violations
- Enable the Create dashboard from a template option and choose AUTOSAR C++14 Compliance from the drop-down menu.
- Click Create to finish adding the dashboard.
In addition to the AUTOSAR-specific widgets shipped with the artifact (see Viewing AUTOSAR Compliance Widgets), the dashboard includes three implementations of the native Categories - Top 5 Table DTP widget. The widgets are configured to use the AUTOSAR C++14 compliance categories shipped with the artifact.
Top 5 AUTOSAR Violations
This widget shows the five Parasoft rules with the most This widget shows the five Parasoft rules with the most number of violations. Click on a link in the Name column to open the Violations by Rule report. Click on the more... link to open the Violations by Compliance Category report. 
AUTOSAR AUTOSAR Violations by Analysis
This widget shows the breakdown of violations by ability to be enforced (see Ability to be Enforced by Static Analysis). Click on a link in the Name column to open the Violations by Rule report.
Top 5 AUTOSAR Guidelines
This widget shows the five AUTOSAR guidelines with the most number of violations. Click on a link in the Name column to open the Violations by Rule report. Click on the more... link to open the Violations by Compliance Category report.
Widget Configuration
...
- AUTOSAR Compliance - Guidelines by Status
- AUTOSAR Compliance - Percentage
- AUTOSAR Compliance - Status
- AUTOSAR Violations by Obligation - TreeMap
You can manually add the AUTOSAR Compliance widgets to your dashboard (see Adding Widgets). The widgets will appear in the Compliance category in the Add Widget overlay:
You can configure the following settings:
...
This widget shows you the general state of compliance. Click on the widget to open the AUTOSAR Compliance Report.
The widget can show five possible states:
...
This widget shows the completeness of AUTOSAR compliance as a percentage. Completeness is based on number of guidelines being enforced in the profile. Click on the widget to open the AUTOSAR Compliance Report.
AUTOSAR Compliance - Guidelines by Status
This widget shows the compliance status for an individual obligation category (All, Required, or Advisory).
The pie chart can represent up to five different guideline statuses for the selected category:
...
This widget provides a representation of the highest concentration of static analysis violations per AUTOSAR obligation (required, advisory). The widget also shows the guidelines 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.
...
The AUTOSAR Compliance Report provides an overview of your AUTOSAR compliance status and serves as the primary document for demonstrating compliance. It includes an entry for each guideline, its level of compliance, any deviations and/or re-catorizations, etc.
You can perform the following actions:
...
| Table of Content Zone | ||||||
|---|---|---|---|---|---|---|
| ||||||
Guideline Enforcement PlanThe Guidelines Enforcement Plan (GEP) lists the AUTOSAR guidelines mapped to Parasoft code analysis rules and other information to demonstrate how compliance is checked. 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 |
You can change a guideline's obligation level from advisory to required and still claim compliance with AUTOSAR C++14. Guidelines cannot, however, be re-categorized as advisory. If you changed any of the AUTOSAR guideline categories (see Profile Configuration), they will be processed and displayed in this report.
Deviation ReportA "deviation" is a documented violation of the guideline and supporting rationale for allowing the violation to remain. In the context of AUTOSAR 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. Your code can contain violations and still be AUTOSAR-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. Click on the Deviations Report link in the AUTOSAR 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 AUTOSAR 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 AUTOSAR during a regulatory audit. The Build Audit Report is a standard report shipped with DTP and is not specific to AUTOSAR Compliance.
In order to download an archive, the build has to be locked. See Build Audit Report for additional details about this report. |
...
Custom Configuration of Profile
The AUTOSAR Compliance DTP Workflow ships with a model profile (see Working with Model Profiles) configured to monitor compliance with AUTOSAR C++14. The profile include information necessary for generating compliance reports (see Viewing AUTOSAR Compliance Reports). 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 your 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.
- Choose Extension Designer from the DTP settings menu (gear icon).
- Click the Model Profile tab and expand the AUTOSAR Compliance menu.
- Click AUTOSAR C++14 and click Export Profile to download a copy.
- Click Add Profile and provide a name when prompted.
- Click Confirm. An empty profile is added.
- Rename the exported copy of the default profile and click Import Profile.
- Browse for the copy and confirm to upload.
- Click on a guideline and specify your changes. You are allowed to change a guideline's obligation level from advisory to required and claim compliance with AUTOSAR C++14, but required rules cannot be re-categorized as advisory.
- Click Save.
Upgrading AUTOSAR Compliance
You should update any extensions when you upgrade DTP. Extensions are designed to be forward compatible, but Parasoft does not guarantee that older extensions will function as expected with newer versions of DTP. We strongly recommend installing the latest version of the artifact and removing the older version to ensure proper functionality.
- Install the latest version of the Automotive Compliance Pack as described in the Installation section.
- Open Extension Designer from the DTP settings menu (gear icon) and click the Settings tab.
- Expand the DTP Workflow compliance category (or the category containing the service with the older AUTOSAR artifact) and click on the service.
- Click on the tab containing the AUTOSAR flow and delete all nodes. You can use your mouse to click and drag over all nodes or use the select-all keyboard shortcut.
- Import the new AUTOSAR Compliance artifact by choosing Import> Local> Flows> Workflows> Automotive> AUTOSAR Compliance from the vertical ellipses menu.
- Click Deploy to finish deploying the newer AUTOSAR assets.
- Click the Configuration tab and click the delete button (trash icon) for the older extension.