Automotive Software Architecture Views and Why we need a new one – Safety view - Archive ouverte HAL Accéder directement au contenu
Communication Dans Un Congrès Année : 2016

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

Résumé

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
Origine : Fichiers produits par l'(les) auteur(s)
Loading...

Dates et versions

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

Identifiants

  • HAL Id : hal-01372336 , version 1

Citer

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 Consultations
1316 Téléchargements

Partager

Gmail Facebook X LinkedIn More