Whitepaper: Achieving AUTOSAR C++14 Compliance with Parasoft C/C++test

Parasoft C/C++test supports AUTOSAR C++ 14 (19.03) with the most comprehensive rule coverage and unique compliance reporting on the market.

Learn about Parasoft C/C++test Support for the AUTOSAR C++14 Coding Standard.

Achieve AUTOSAR C++14 Compliance-27

Download the whitepaper for the details on how the Parasoft testing tool suite helps testers and developers ensure AUTOSAR compliance.

Key takeaways:
  • Overview of Parasoft Support for AUTOSAR C++14
  • AUTOSAR C++14 guidelines classifications
  • Parasoft testing tool suite coverage
  • Parasoft C/C++test (unified testing tool for C/C++ development) and Parasoft DTP (reporting and analytics dashboard) provide a comprehensive solution to help organizations overcome the challenges associated with automotive software quality and compliance.
  • Parasoft C/C++test and Parasoft DTP support AUTOSAR C++ 14 (19.03) with the most comprehensive coverage of static analysis checkers for the AUTOSAR C++14 guidelines and unique compliance reporting.
  • Parasoft C/C++test is certified by TÜV SÜD for functional safety according to ISO 26262, IEC 61508, and IEC 62304 standards, helping development teams achieve the desired safety integrity level (SIL/ASIL).
  • In addition to leading support for AUTOSAR C++14, Parasoft C/C++test also provides a set of built-in checkers (rules) for verifying compliance with standards including MISRA C 2012, MISRA C++ 2008, JSF AV C++, SEI CERT C/C++, HIC++, CWE Top 25 (and CWE ‘on the cusp’), OWASP and more.
  • Parasoft Compliance Packs provide users with standard-specific configurations, automatic generation of compliance documentation, risk assessment framework, along with dynamic compliance reporting dashboards DTP, to help stakeholders easily aggregates, correlates, and applies analytics to centralize reporting for each step along the complex software supply chain.

With 100% coverage for required and automated rules, the Parasoft testing tool suite ensures AUTOSAR compliance throughout the software development life cycle, improves code quality and reduces cost associated with resources and time-to-market.

Below, we’ve listed a sampling of rule coverage for the Parasoft testing tool suite, including how AUTOSAR 18.10 guidelines map to the Parasoft Static Analysis Rules for C/C++. For the complete list, download the white paper.

Obligation Level

Enforcement by Static Analysis

Supported

Unsupported

All

Percent Coverage

Required

Automated

301

0

301

100%

Required

Partially

18

2

20

90%

Required

Non-Automated

19

22

41

46%

Required

All

338

24

362

93%

 

Obligation Level

Supported

Unsupported

All

Percent Coverage

Required

336

26

362

93%

Advisory

25

10

35

71%

All

361

36

397

91%

 

Enforcement by Static Analysis

Supported

Unsupported

All

Percent Coverage

Automated

320

9

329

97%

Partially Automated

19

3

22

86%

Non-Automated

22

24

46

48%

All

361

36

397

91%

 

ID

Description

Obligation Level

Enforcement by Static Analysis

Parasoft Rule ID

A0-1-1

A project shall not contain instances of non-volatile variables being given values that are not subsequently used

Required

Automated

AUTOSAR-A0_1_1

A0-1-2

The value returned by a function having a non-void return type that is not an overloaded operator shall be used

Required

Automated

AUTOSAR-A0_1_2

A0-1-3

Every function defined in an anonymous namespace, or static function with internal linkage, or private member function shall be used

Required

Automated

AUTOSAR-A0_1_3

A0-1-4

There shall be no unused named parameters in non-virtual functions

Required

Automated

AUTOSAR-A0_1_4

A0-1-5

There shall be no unused named parameters in the set of parameters for a virtual function and all the functions that override it

Required

Automated

AUTOSAR-A0_1_5

A0-1-6

There should be no unused type declarations

Advisory

Automated

AUTOSAR-A0_1_6

A0-4-1

Floating-point implementation shall comply with IEEE 754 standard

Required

Non-Automated

N/A

A0-4-2

Type long double shall not be used

Required

Automated

AUTOSAR-A0_4_2

A0-4-3

The implementations in the chosen compiler shall strictly comply with the C++14 Language Standard

Required

Automated

Configure your compiler to enforce C++14 strict compilation, scan the compilation log for related problems, and use DTP Custom Analyzers from Multi- Language Pack to report a violation in the AUTOSAR C++ 14 compliance report. This procedure assumes that your compiler reports a compilation error if the source code does not conform with the C++14 standard.
 

About Parasoft

Parasoft’s software testing solutions support the entire software development process, from when the developer writes the first line of code all the way through unit and functional testing, to performance and security testing, leveraging simulated test environments along the way. Parasoft's unique analytics platform aggregates data from across all testing practices, providing insights up and down the testing pyramid to enable organizations to succeed in today's most strategic development initiatives, including Agile/DevOps, Continuous Testing, and the complexities of IoT. Parasoft’s automated software testing innovations fuel software development organizations, helping teams reduce the time, cost, and effort of delivering high-quality software to the market.