Functional Safety: What’s around?

ISO 26262 processes and requirements

Joe Wlad from Verocel and David Barnett and Bob Leigh from Real-Time Innovations (RTI) discuss ISO 26262 compliance using approved software components for road vehicles

Software-driven systems are now the mainstay of innovation in every industry, especially in automotive applications. Use of software in cars has spread from basic diagnostics to information and entertainment systems to complete autonomous driving features.

Modern vehicles are now shipped with tens of millions of lines of software that manage engine and transmission controls, braking, steering, and a host of diagnostic information on every subsystem. This trend has compelled automotive designers to address safety in a way that includes system, hardware and software design.

The automotive industry has adopted ISO 26262 as its functional safety standard for electronic systems that include both hardware and software.

A common problem is how to use commercial-off-the-shelf (cots) software that may or may not have a proven safety pedigree in a system destined for ISO 26262 approval,

 

Standard

ISO 26262 edition one is composed of ten parts and covers the safety lifecycle aspects of electric and electronic automotive systems. The diagram summarises the key requirements of each part. Parts three to seven are the core parts that deal with product development from the concept phase through design and production.

The document provides a list of objectives for each general requirement such as initiation of product development at the software level, inputs such as the safety plan, requirements such as activities for product development at the software level shall be planned, and work products, for example the software verification plan.

From a holistic point of view, all the sections of ISO 26262 must be addressed at the appropriate Asil automotive safety integrity level to be considered compliant.

Additionally, the structure of ISO 26262 is encapsulated in a way that permits activities, validation and assessment for each major part of development to take place independently. Therefore, one conceivably can take a hardware or software component, assess and approve it in one system or element and then reuse the approval in other systems and assessments. In fact, parts 8-12 and 8-13 directly address requirements for approval of software and hardware components, respectively.

 

Software requirements

Part six is a core process requirement of ISO 26262 and as such does not include supporting processes of functional safety managements, configuration management and change management and more. While ISO 26262 does not assume any particular model of software development such as agile, iterative and so on, it is convenient to document requirements in a way as if the software were designed in a waterfall model. The first requirement in developing software to be compliant with ISO 26262 is to initiate a safety plan and software verification plan. These plans would of course be supported by other process plans defined in parts two and eight.

Once the initiation activities are complete, the specification of the software safety requirements process takes place. Here there is an inexorable link to the safety concept and overall system design. The system design and/or hardware design will place limitations and burdens on software and these constraints need to be considered as part of the requirements process.

A good candidate for a software component approved under ISO 26262 would likely have a well-defined and exposed interface into any system or hardware design. This does not mean that any system or hardware would support a given software component but that any limitations or conditions be exposed to an integrator, for example, memory and CPU constraints would be specific requirements if needed.

The work products resulting from this phase include a software requirements specification, refined hardware-software interface specification and results of the software verification activities.

 

Cots approach

The organisation of ISO 26262 part six and other parts are highly conducive to approval, assessment and reuse of cots software components intended for various applications. First, the organisation of the software lifecycle requirements and activities in part six are staged, meaning the outputs of one phase are the inputs to the next. There are three levels of software testing defined in part six and each of these is the result of increased software integration.

The other parts of ISO 26262 that are relevant to software components include part two for management of functional safety and part eight covering supporting processes.

The software component developer would need to demonstrate that its internal planning processes are aligned with part two requirements. At a minimum, this would include a functional safety management plan and a quality management plan as well as evidence of a safety culture and personnel who are trained and responsible for enforcing the safety culture in the development and production phases.

The planning process will also include references to any applicable tool qualification plans. This could include software modelling tools, coverage analysis tools and any other tools used in the development or verification activities.

ISO 26262 part eight is relevant for software component suppliers. Part eight defines requirements for documentation control, configuration management, change management and requirements for qualification of tools used under ISO 26262. Clause 12 of part eight defines the requirements for qualification of software components, thereby making explicit the notion that approval of software components under ISO 26262 is possible.

The requirements to qualify a software component under clause 12 of part eight include:

 

  • • Requirements that address functionality, resource usage, response times, behaviour under failure conditions and robustness;
  • • Description of the configuration, interfaces and how to integrate the component, description of operation under abnormal conditions, and a description of known limitations and workarounds to include existing defects and limitations;
  • • Verification results showing full coverage of all applicable software requirements, including robustness for normal and abnormal conditions and including the required structural coverage analysis applicable to the proposed Asil;
  • • Documentation of the software identification and configuration, targeted Asil, hardware compatibility limitations, organisation performing the qualification, and the results of the verification measures applied to the software component; and
  • • The qualification results and the validity of the results must be verified and, if required, additional activities may need to be performed.

 

The last point becomes a key factor in determining the value of software component reuse in ISO 26262. Establishing the validity of the qualification results in a different environment will always compel some additional activities on the part of the integrator. If the supplied software component does not adequately document the scope of usage, approval and limitations, the integrator may be challenged in trying to apply ISO 26262 credit for the component in their respective environment.

 

Qualified software

Connectivity platforms exist that can provide software developers and integrators with high-level interfaces for distributing real-time data between devices, applications and subsystems. For example, they can be used to stream video, radar and lidar data to analytics and autonomous driving applications as well as to integrate those applications with traditional ECUs.

This is often referred to as communications middleware since it is a library that sits between applications and the underlying operating system and network stack, providing developers with high-level publish and subscribe interfaces that abstract low-level networking details.

It should support the DDS data distribution service family of standards and be a certifiable middleware available with a complete, commercially supported certification package to support ISO 26262 certification, including Asil D. The package should include all of the evidence required by a certification authority such as TÜV SÜD.

Using certified middleware that conforms to a widely used industry standard has a number of benefits such as cost savings, reduced risk, leverage experience, reliability, interoperability, open architecture and component isolation.

Certified middleware can continue to return costs savings through the entire product life cycle.

In the automotive market, this especially applies to in-car adas and autonomous driving applications where multiple software components must share data. In a well architected system, these interdependent systems should be loosely coupled and will need varying levels of certification, depending on their function.

For example, a sense-and-avoid braking system would likely need certification to Asil D and any software critical to the sensing, decision making and resulting action would need this certification, such as, sensors, ECUs, software algorithms, braking and steering modules. However, functions such as navigation and path planning may need to interact with some of the same components but would likely need a much lower certification level or no certification at all.

Without certified middleware to isolate and separate these functions, every component would need to be certified to the highest certification, which would be very expensive and would limit the possible features and functions of a system.

 

Software components

ISO 26262 part eight, clause 12 addresses the requirements for software reuse. Reuse could apply to a vendor’s own software or cots software procured from a third party.

It is expected that any approved software component will be used in a variety of applications or it would not be of much use to an integrator. Examples of good reusable software components are operating systems, communications and messaging software, language and graphics libraries, and file system interfaces, among others.

By providing guidance on how to use and apply the software component and its certification data into various applications, the integrator’s certification burden and risk can be reduced. A software component approved under ISO 26262 should include the following data and information so the integrator can increase its familiarity with the component and represent it more easily when submitted for ISO 26262 approval:

 

  • • ISO 26262 compliance certificate from an approved entity, such as TÜV;
  • • Software safety plan;
  • • Functional safety manual;
  • • Compliance matrix, which may be part of the safety manual;
  • • Configuration index or version description document;
  • • User’s guides and manuals;
  • • Verification results;
  • • Test vectors;
  • • Tool qualification data and results;
  • • Vulnerability analysis or hazard analysis;
  • • Traceability data;
  • • Partitioning analysis, optional; and
  • • Integration guide.

 

Conclusion

The trends in automotive design include the ever-increasing use of software, integration of software components at various levels of safety and regulatory compliance with ISO 26262. Additionally, there is a trend for more autonomous features in road vehicles that bring about complex safety goals and requirements.

Teams seeking to integrate cots software into their automotive projects will need to vet those software components closely. Beyond just the hardware compatibility, the integrator will need to show regulatory compliance with part six, among others, of ISO 26262. For a software component, this can be tricky because not all certifiable software components are equal in value and capability.

It is important to recognise that beyond an ISO 26262 accreditation for a cots component lies integration activity that imposes burdens on the integrator. Any software component used in an ISO 26262 system should have some evidence, guidance and documentation that ensures the integrator can reuse that certification evidence without undue burden or risk.

Before integrators attempt to use a cots component, they should determine how the component supports the considerations raised here. Lack of a vulnerability analysis, safety manual, partitioning guidance as well as users guides and manuals will make ISO 26262 approval using a cots component more burdensome.

 

Joe Wlad is vice president for business development at Verocel, David Barnett is vice president of products and markets at Real-Time Innovations (RTI) and Bob Leigh is director of market development at RTI

 

www.verocel.com

www.rti.com

 

Recommend to Colleagues: