Automotive Software Architecture Views and Why we need a new one – Safety view - CARS 2016 - Critical Automotive applications : Robustness & Safety Access content directly
Conference Papers Year : 2016

Automotive Software Architecture Views and Why we need a new one – Safety view

Abstract

The growth of the size and complexity of automotive software has been driven by the increased number of software-dependent innovations in modern cars. The growth of the size and complexity drives the usage of multiple abstraction levels in automotive software designs. One of these levels is the architecture level where the high level design of software is documented using multiple views such as logical, function, deployment. In this paper we review these architectural views and argument that they require one more view – safety view – which is compliant with the ISO/IEC 26262 and links the design of software systems (both the functional and system views) with the safety goals. We advocate the need for this view that would help the designers to understand and trace the design of software safety throughout the software lifecycle.
Fichier principal
Vignette du fichier
CARS2016_paper_1.pdf (275.51 Ko) Télécharger le fichier
Origin : Files produced by the author(s)
Loading...

Dates and versions

hal-01372336 , version 1 (27-09-2016)

Identifiers

  • HAL Id : hal-01372336 , version 1

Cite

Miroslaw Staron. Automotive Software Architecture Views and Why we need a new one – Safety view. Workshop CARS 2016 - Critical Automotive applications : Robustness & Safety, Sep 2016, Göteborg, Sweden. ⟨hal-01372336⟩

Collections

CARS2016
165 View
1315 Download

Share

Gmail Facebook X LinkedIn More