This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Evaluating Alternate Approaches for Co-Hosting Third Party Software within Safety Critical Applications in ISO 26262 Context
Technical Paper
2014-01-2422
ISSN: 0148-7191, e-ISSN: 2688-3627
Annotation ability available
Sector:
Language:
English
Abstract
Safety compliance has a new set of difficult questions to address due to the usage of COTS, OSS and externally supplied software code in automotive systems. The use of third-party software component is essential to business as it helps in reduction of cost and development cycle. However, there are many technical risks encountered when incorporating Third-Party Software (TPSW) components into safety related software. Moreover, safety systems conforming to new automotive safety standard ISO 26262 are expected to satisfy criteria for co-existence of TPSW with internal safety related software and legacy code. The purpose is to avoid a potential failure that may be triggered by TPSW which in turn may propagate to cause failure in other software partitions. There are several options available to address the above requirements. We should carefully evaluate the TPSW's functionality and pedigree and apply combination of techniques to assist in supporting the intent of ISO 26262. This paper discusses on the issues concerning insertion of third party software code (OEM supplied code, Tier 2 vendor software) into in-house developed ECU software. Multiple approaches have been evaluated and discussed to address integration related issues and ISO 26262 compliance.
Recommended Content
Authors
Citation
Krishnamurthy, R. and Mukherjee, R., "Evaluating Alternate Approaches for Co-Hosting Third Party Software within Safety Critical Applications in ISO 26262 Context," SAE Technical Paper 2014-01-2422, 2014, https://doi.org/10.4271/2014-01-2422.Also In
References
- ISO 26262-6:2011(E) Road vehicles - Functional safety - Part 6: Product development: software level
- ISO 26262-8:2011(E) Road vehicles - Functional safety - Part 8: Supporting processes
- ISO 26262-9:2011(E) Road vehicles - Functional safety - Part 9: ASIL-oriented and safety-oriented analysis
- Brewerton , S. and Schneider , R. Hardware Based Paravirtualization: Simplifying the Co-Hosting of Legacy Code for Mixed Criticality Applications SAE Technical Paper 2013-01-0186 2013 10.4271/2013-01-0186
- Eberhard , D. , Schneider , R. , Grosshauser , F. , and Brewerton , S. Timing Protection in Multifunctional and Safety-Related Automotive Control Systems SAE Technical Paper 2009-01-0757 2009 10.4271/2009-01-0757
- Brewerton , S. , Schneider , R. , and Grosshauser , F. Practical Use of AUTOSAR in Safety Critical Automotive Systems SAE Int. J. Passeng. Cars - Electron. Electr. Syst. 2 1 249 257 2009 10.4271/2009-01-0748
- Gandhi Swapnil , Brewerton Simon P. Techniques and Measures for Improving Domain Controller Availability while Maintaining Functional Safety in Mixed Criticality Automotive Safety Systems
- Schneider , R. , Kalhammer , M. , Eberhard , D. , and Brewerton , S. Basic Single-Microcontroller Monitoring Concept for Safety Critical Systems SAE Technical Paper 2007-01-1488 2007 10.4271/2007-01-1488
- Office of Aviation Research Washington, D.C. 20591 Commercial Off-The-Shelf (COTS)Avionics Software Study, May 2001, Final Report DOT/FAA/AR-01/26
- AUTOSAR Specification of Operating System V3.1.0 R3.1 0002
- Trew Tim , Soepenberg Gerben Identifying Technical Risks in Third-Party Software for Embedded Products
- Haddox Jennifer M. , Kapfhammer Gregory M. , Michael Christoph C. An Approach for Understanding and Testing Third Party Software Components
- Scanlon Taylor Zero Defects Needs Third Party Software to Succeed