Managing an ISO 26262 Safety Case: A Software System Perspective

Paper #:
  • 2016-01-0137

Published:
  • 2016-04-05
DOI:
  • 10.4271/2016-01-0137
Citation:
Doerr, H. and Stuermer, I., "Managing an ISO 26262 Safety Case: A Software System Perspective," SAE Technical Paper 2016-01-0137, 2016, https://doi.org/10.4271/2016-01-0137.
Pages:
9
Abstract:
A key component of developing a safety-critical automotive system in compliance with ISO 26262 is developing what is known as the safety case. This delivery justifies that the system is free from unreasonable risk and that the safety requirements are complete and satisfied according to evidence from ISO 26262 work products. However, the standard provides neither practical guidance on how the safety case should be developed, nor how the safety argument should be evaluated in the functional safety assessment process.This paper discusses quality and product readiness of the system under development in the context of safety case generation. We will focus on the software level and ISO 26262-6 requirements that relate to this. We will look at the software lifecycle of the system and how to measure and deliver key data throughout this lifecycle. A major focus will be on how to best homogenize quality data and monitor critical software quality indicators that contribute to argumentation of the safety case. Finally, we will present a solution that helps managers tackle obstacles that may arise from project beginning to delivery of the safety case, particularly at software level.
Access
Now
SAE MOBILUS Subscriber? You may already have access.
Buy
Select
Price
List
Download
$27.00
Mail
$27.00
Members save up to 40% off list price.
Share
HTML for Linking to Page
Page URL

Related Items

Training / Education
2017-06-15
Standard
2017-06-09
Technical Paper / Journal Article
2014-04-01
Technical Paper / Journal Article
2013-05-13