AUTOSAR (AUTomotive Open System ARchitecture) is a worldwide development partnership of vehicle manufacturers, suppliers, service providers and companies from the automotive electronics, semiconductor , and software industry. AUTOSAR is focused on the standardization of basic system functions and functional interfaces. The organization supports these initiatives by creating and publishing standards that provide guidance on the development of these systems.
Rules are classified as either "automated," "partially automated," or "non-automated." According AUTOSAR, automated rules are automatically enforceable with static analysis. Partially automated rules can be enforced supported with a combination of static code analysis and as support for a manual code review. Non-automated rules cannot be reasonably supported with static analysis and require other means of verification, such as manual code review.
- Install the Automotive Compliance Pack into DTP Extension Designer.
- Deploy the AUTOSAR DTP Workflow to your DTP environment. This action also deploys the AUTOSAR Compliance extension assets.
- Analyze code with C/C++test using the AUTOSAR C++14 Coding Guidelines test configuration and report violations to DTP. You can configure C/C++test to use the local test configuration or the test configuration shipped with the Automotive Compliance Pack.
- Add the AUTOSAR 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.
- Compliance categories and guidelines: These files add the AUTOSAR 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 AUTOSAR C++14 dashboard that includes a a pre-defined set of AUTOSAR-related widgets.
- Model and profile: These files provide the framework for rendering the report data required to demonstrate 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 AUTOSAR guidelines.
|Green||Guidelines that your code is complaint.|
Guidelines that your code is deviating from but are still considered compliant.
Deviations refer to instances in which the code violates a guideline, but the violation instance is 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 are implemented with represent Parasoft as suppressed static analysis violations. Deviations enable you to safely reduce static analysis noise and remain compliant with AUTOSARstatic 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 is missing.|