Whitepaper: ISO 26262 Software Compliance with Parasoft – Achieving Functional Safety in the Automotive Industry

You have to implement quality process controls for developing safety-critical software that complies with ISO 26262. We’ve got a solution for that.

Get the detailed information you need to learn about ISO 26262 and potential policy-related challenges.

Parasoft Functional Safety & Compliance 2_1

Download the whitepaper to see how Parasoft can help automotive software development organizations achieve compliance with ISO 26262.

Here’s what you’ll learn about:
  • What ISO 26262 covers (and what it doesn’t)
  • Software-specific sections of ISO 26262
  • ISO 26262 compliance and policy-driven development
  • Parasoft support for ISO 26262
  • Initialization of product development at the software level
  • Software unit design and implementation
  • Software unit testing

This includes requirements specification, design, implementation, integration, verification, validation and configuration. ISO 26262 specifies the following requirements:

  • Functional safety management for automotive applications
  • The concept phase for automotive applications
  • Product development at the system level for automotive applications software architectural design
  • Product development at the hardware level for automotive applications software unit testing
  • Product development at the software level for automotive applications
  • Production, operation, service and decommissioning
  • Supporting processes: interfaces within distributed developments, safety management requirements, change and configuration management, verification, documentation, use of software tools, qualification of software components, qualification of hardware components and proven-in-use argument
  • Automotive Safety Integrity Level (ASIL)-oriented and safety-oriented analysis

ISO 26262 does not cover:

  • Unique E/E systems in special purpose vehicles such as vehicles designed for drivers with disabilities
  • Safety standards for large vehicles, such as those over 3500KB (7700 pounds) gross weight
  • Hazards related to electric shock, fire, smoke, heat, radiation, toxicity, flammability, reactivity, corrosion, release of energy and similar hazards, unless directly caused by malfunctioning behavior of E/E safety-related systems
  • Nominal performance of E/E systems

Part 6 of the standard specifically addresses product development at the software level. Requirements for the following development activities are specified:

  • Initialization of product development
  • Specification of software safety requirements
  • Software architectural design
  • Unit design and implementation
  • Unit testing
  • Software integration and testing
  • Verification of software safety requirements.

Methods defined by the ISO 26262 standard should be selected depending on the automotive safety integrity level. The higher the ASIL, the more rigorous the methods.

With public safety, potential litigation, market position and other consequences on the line, it behooves software development teams and people in the traditional business management positions to come together on policy and implement the strategy into their software development lifecycle.

Software engineers make business critical decisions every day in the form of their coding practices, quality activities and engineering processes. When software permeates critical functions associated with functional safety, engineering decisions can lead to significant business risks. E/E systems in automobiles that must conform to ISO 26262 are particularly vulnerable to risks because the standard specifies very detailed lifecycle processes to determine safety.

The key to reducing risks is aligning software development activities with organizational business goals through policy-driven development, which ensures engineers deliver software according to expectations. Policy-driven development involves:

  • Clearly defining expectations and documenting them in understandable policies
  • Training engineers on business objectives driving those policies
  • Enforcing policies in an automated, unobtrusive way

Adopting a policy-driven strategy allows businesses to accurately, objectively measure productivity and application quality, which lowers development costs and reduces risk.

Parasoft DTP facilitates the software quality tasks specified in ISO 26262 including static analysis, data flow static analysis, metrics analysis, peer code review, unit testing and runtime error detection. This provides teams a practical way to prevent, expose and correct errors in automotive functional safety systems. DTP collects data generated by software engineering processes, such as static code analysis violations, test results, code metrics, coverage analysis, source control check-ins, defect tracking systems, etc. and generates meaningful views of the correlated and prioritized data.

The real power of DTP is the Parasoft Process Intelligence Engine (PIE), which performs an additional post analysis on the development artifacts collected in order to pinpoint risk in the code while highlighting opportunities for improving development processes. DTP reports problematic code and a description of how to fix it to the engineer’s IDE based on the programming policy.

By offering a broad range of analysis tools and enabling you to automatically monitor compliance with your development policy, Parasoft bridges the gap between development activities and business processes. Development teams can also generate configurable test reports that contain a high level of detail, which helps facilitate the work required for the software verification process.

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.