News & Analysis
DO-178 software reuse in the ISO 26262 domain reduces cost for automotive suppliers
Christoph Hammerschmidt
5/21/2012 5:49 AM EDT
Is the reuse of avionics software feasible or even recommendable in automotive applications? This was one of the questions the research project VirtuOS tried to straighten out. The research team also addressed the question if such software meets the requirements of the safety standard ISO 26262.
The VirtuOS team - researchers from the Berlin Technical University, the Fraunhofer FIRST Institute for Computing Architectures and Software Technology and from software company OpenSynergy - came to a clear conclusion: Yes - almost all artifacts meeting the avionics safety standard DO-178 can be reused in an ISO 26262 context. For automotive suppliers and OEMs, this option can help to significantly reduce development efforts while at the same time it improves functional safety at reasonable costs.
Within the scope of the project, a variety of processes, tools and methods to create safe automotive software has been assessed and developed. Fraunhofer FIRST analyzed existing safety standards in various domains including avionics (DO-178B) and automotive (ISO 26262). Since the validation of schedules is an important prerequisite for deployment of software in safety-critical applications, Fraunhofer FIRST got granular on scheduling methods and developed a scheduling concept for safe software partitioning. These methods are one of the foundations for the development of tools which can be used to generate safe automotive software.
The Institute of Software Technology and Theoretical Informatics of the Berlin Technical University developed a verification concept aiming at identifying errors when using external software libraries, making use of static code analysis. This method helps developers to improve safety in software already at an early stage of development.
The researchers also assessed and improved development processes and they scrutinized the requirements to the OpenSynergy's open software platform COQOS; parts of the platform have been adapted to these requirements. In connection with the integration of the PikeOS avionics microkernel into the COQOS platform, the research partners also checked and acknowledged the transferability of avionics safety standards to the automotive applications universe. The project analysis allowed OpenSynergy to optimize its software in with respect to safety and security.
Courtesy of EETimes Europe
----------------------
If you found this article to be of interest, visit Military/Aerospace Designline where you will find the latest and greatest design, technology, product, and news articles with regard to all aspects of military, defense and aerospace. And, to register to our weekly newsletter, click here.
The VirtuOS team - researchers from the Berlin Technical University, the Fraunhofer FIRST Institute for Computing Architectures and Software Technology and from software company OpenSynergy - came to a clear conclusion: Yes - almost all artifacts meeting the avionics safety standard DO-178 can be reused in an ISO 26262 context. For automotive suppliers and OEMs, this option can help to significantly reduce development efforts while at the same time it improves functional safety at reasonable costs.
Within the scope of the project, a variety of processes, tools and methods to create safe automotive software has been assessed and developed. Fraunhofer FIRST analyzed existing safety standards in various domains including avionics (DO-178B) and automotive (ISO 26262). Since the validation of schedules is an important prerequisite for deployment of software in safety-critical applications, Fraunhofer FIRST got granular on scheduling methods and developed a scheduling concept for safe software partitioning. These methods are one of the foundations for the development of tools which can be used to generate safe automotive software.
The Institute of Software Technology and Theoretical Informatics of the Berlin Technical University developed a verification concept aiming at identifying errors when using external software libraries, making use of static code analysis. This method helps developers to improve safety in software already at an early stage of development.
The researchers also assessed and improved development processes and they scrutinized the requirements to the OpenSynergy's open software platform COQOS; parts of the platform have been adapted to these requirements. In connection with the integration of the PikeOS avionics microkernel into the COQOS platform, the research partners also checked and acknowledged the transferability of avionics safety standards to the automotive applications universe. The project analysis allowed OpenSynergy to optimize its software in with respect to safety and security.
Courtesy of EETimes Europe
----------------------
If you found this article to be of interest, visit Military/Aerospace Designline where you will find the latest and greatest design, technology, product, and news articles with regard to all aspects of military, defense and aerospace. And, to register to our weekly newsletter, click here.
|
|
|
|
|
Navigate to related information
Sanjib.Acharya
5/21/2012 11:33 PM EDT
If I've understood correctly, can this be assumed that if a piece of aviation software, which is compliant to DO-178, can be reused in automobile domain, the same software will automatically get compliant to ISO 26262 without any major qualification and assessment effort? That will save a lot of time and cost for the automotive industries.
Sign in to Reply
Supersonico
5/30/2012 3:31 AM EDT
I am sorry but there are no miracles here! the article is speculative and misleading. Event if the theory is right, in practice you would still need to comply with ISO 26262 Proven-in-Use clause (Part8, Clause 14) which states that you can claim PiU for "candidates being used in other safety-related industries". Bottom line is there is no automatic compliance without the necessary integration and validation measures...let's not repeat history here !
Sign in to Reply