View Categories

System – Identification of Software Safety Requirements at Function Level

OTA update mechanism faciliates, the download of the most recent firmware or software leveraging the wireless internet connections to interact with an OEM cloud service through V2N. This capaibilty to enhance the vehicle’s performance without the need for a dealership visit, woudld need a comprehensive set of software safety requirements designed to ensure the security and reliability of the update process. 

It’s crucial to recognize and integrate the pertinent software safety requirements into the design, both from a holistic perspective and on a function-by-function basis. As safety standards evolve, modifications must be made to the system’s Functional Safety (FuSa) to ensure compliance with future regulations.

For the most recent information, refer to the following documents:

  • “Safe and Secure Automotive Over-the-Air Updates – Operational and Functional Requirements” (Sena, M.,  2015)
  • ISO 26262 -1-12 (2018) 
  • ISO 21448 (2022)
  • ISO/SAE 21434 (2021)

Main Question

Are software safety requirements identified at a function level?

Sub-Questions

  1. Where applicable, are relevant standards (ISO 26262, ISO/SAE 21434 etc.) followed during the definition of software updates for both safety critical and non-safety critical SW?
  2. Are the relevant standards considered during the defintion of OTA processes for the respective software?

References