Arguing Software Compliance with ISO 26262

Hocking, Ashlie B.; Knight, John; Aiello, M. Anthony; Shiraishi, Shinichi

doi:10.1109/issrew.2014.88

Cited by 13 publications

(3 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…One way to manage complexity is to increase uniformity of the argument with patterns. Much work has been done in this area, some examples for the automotive domain are [19], [20], [21], and for a multi-concern assurance case [22]. We use argument patterns to make the assurance case fragments more uniform and efficient to update.…”

Section: Argument Patternsmentioning

confidence: 99%

Continuous Deployment for Dependable Systems with Continuous Assurance Cases

Warg

Blom

Borg

2019

2019 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)

View full text Add to dashboard Cite

An assurance case contains a structured argument supported by evidence, demonstrating that a system fulfils a certain quality attribute such as safety, cybersecurity or reliability. The traditional way of building assurance cases is, however, not well suited to continuous deployment, and difficult to maintain with a product structure where many variants and frequent new versions must be managed. By integrating the assurance work with product development in continuous assurance cases, which are updated and assessed iteratively, we claim continuous deployment of dependability-critical products is possible to achieve. In this paper we propose a work process combining the use of component-based design, contracts, modular assurance cases, and continuous assessment to enable continuous deployment in the context of product lines.

show abstract

Section: Argument Patternsmentioning

confidence: 99%

Continuous Deployment for Dependable Systems with Continuous Assurance Cases

Warg

Blom

Borg

2019

2019 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW)

View full text Add to dashboard Cite

show abstract

“…Aircraft & avionics Delange et al 2009;Delmas et al 2015Denney and Pai 2013b;Dias and Iyoda 2011;Gobbo and Mili 2001;Littlewood and Rushby 2012;Lopez-Jaquero et al 2012;Miller et al 2009;Steiner and Rushby 2011;Zeng et al 2016] Automotive [Antonino and Trapp 2014;da Penha et al 2015;Dardar et al 2012;de Oliveira et al 2015;Ebnenasir and Cheng 2007;Gallina 2014;Hocking et al 2014;Konrad et al 2004;Lin et al 2016;Luo et al 2017a;Martorell et al 2016;Nasser et al 2017;Oertel et al 2014 [Fayad et al 2003;Lakhani and Pont 2012;Murugesan et al 2015;Pont and Banner 2004;Preschern et al 2014a;Sun 2014;Tan et al 2015] Networks & telecommunication [Giuntini et al 2017;Petroulakis et al 2016;Saridakis , 2003 Process & power plants [Larrucea et al , 2016Mahemoff et al 2001;Rauhamäki and Kuikka 2015;Wilson 1992] Generic [Alho and Rauhamäki 2011;Armoush 2010;Armoush et al 2008aArmoush et al ,b, 2009Ba...…”

Section: Application Domain Selection Of Studiesmentioning

confidence: 99%

Assurance of System Safety: A Survey of Design and Argument Patterns

Gleirscher,

Kugele

2019

Preprint

View full text Add to dashboard Cite

The specification, design, and assurance of safety encompasses various concepts and best practices, subject of reuse in form of patterns. This work summarizes applied research on such concepts and practices with a focus on the last two decades and on the state-of-the-art of patterns in safety-critical system design and assurance argumentation. We investigate several aspects of such patterns, for example, where and when they are applied, their characteristics and purposes, and how they are related. For each aspect, we provide an overview of relevant studies and synthesize a taxonomy of first principles underlying these patterns. Furthermore, we comment on how these studies address known challenges and we discuss suggestions for further research. Our findings disclose a lack of research on how patterns improve system safety claims and, vice versa, on the decomposition of system safety into separated local concerns, and on the impact of security on safety. CCS Concepts: • General and reference → Design; Reliability; • Computer systems organization → Architectures; Dependable and fault-tolerant systems and networks; • Hardware → Safety critical systems; • Software and its engineering → Software safety; Error handling and recovery; Software verification and validation; Risk management; • Security and privacy → Security in hardware.

show abstract

“…Instead, it emphasizes that the safety requirements to prevent hazards must be documented, complete and verified, e.g. using coding guidelines, static analysis, manual review or testing (see [2,16]). The handling of exceptional cases can therefore take place in any way, as long as it is suitable to be verified against the safety requirements, which at least means that it is defined and deterministic.…”

Section: Concepts Of Functional Safetymentioning

confidence: 99%

Handling index-out-of-bounds in safety-critical embedded C code using model-based development

Blache

2018

Softw Syst Model

View full text Add to dashboard Cite

Embedded C code for safety critical systems faces some substantial challenges: like every other embedded SW code it must be efficient in terms of code size, data size and execution time, but it must also behave safely under all circumstances, without a user or operator who could handle the errors. One kind of problem is array accesses where the index is outside the specified value range. The C language does not specify the behaviour in such cases, which clearly violates the requirements for safe code. In this paper, the approach of the model-based development tool "ASCET" is explained, and the experiences of three case studies that describe the adoption of index protection by the users are presented.

show abstract

Arguing Software Compliance with ISO 26262

Cited by 13 publications

References 6 publications

Continuous Deployment for Dependable Systems with Continuous Assurance Cases

Continuous Deployment for Dependable Systems with Continuous Assurance Cases

Assurance of System Safety: A Survey of Design and Argument Patterns

Handling index-out-of-bounds in safety-critical embedded C code using model-based development

Contact Info

Product

Resources

About