2015
DOI: 10.1007/s00502-015-0301-x
|View full text |Cite
|
Sign up to set email alerts
|

Filling the gap between automotive systems, safety, and software engineering

Abstract: Development of embedded automotive systems has become tremendously complex in recent years. The trend of replacing traditional mechanical systems by modern embedded systems, and the launch of automotive multi-core systems enable deployment of more advanced control strategies. However, these applications require different safety concepts with different levels of criticality; and providing consistency of the safety concept during the entire product lifecycle is a tedious task. Additionally, new automotive safety… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2016
2016
2020
2020

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 9 publications
(3 citation statements)
references
References 9 publications
0
3
0
Order By: Relevance
“…Security has been taken into account in the early phases of the development cycle of automotive electronics systems, both by enforcing software programming standards that prevent software defects that may enable cyber-attacks [15], as well as by implementing security mechanisms for secure communication [24,25], including software delivery, installation and flashing [1,35]. Factors like Required Resources and Required Know-How have been considered in the SAHARA (Security-Aware Hazard Analysis and Risk Assessment) method for defining threats criticality [27].…”
Section: Securitymentioning
confidence: 99%
“…Security has been taken into account in the early phases of the development cycle of automotive electronics systems, both by enforcing software programming standards that prevent software defects that may enable cyber-attacks [15], as well as by implementing security mechanisms for secure communication [24,25], including software delivery, installation and flashing [1,35]. Factors like Required Resources and Required Know-How have been considered in the SAHARA (Security-Aware Hazard Analysis and Risk Assessment) method for defining threats criticality [27].…”
Section: Securitymentioning
confidence: 99%
“…Moreover, current premium cars implement more than 90 Electronic Control Units (ECU) with close to 1 Gigabyte embedded software code [236]. In 2018, 30% of the overall vehicle cost is predicted to stem from vehicle electronics [237]. The independence of different applications (with different criticality levels) running on the same platform must be made evident.…”
Section: Sensorsmentioning
confidence: 99%
“…The authors of (Macher, Stolz, Armengaud, and Kreiner 2015) aimed at achieving consistency of information between several tools involved in the development process, through to a single source of information principle. In the goal of achieving dependability (safety, security) in the development process between different teams and stakeholders, they decided against a document-centric approach and used the capabilities of UML and SysML for their design.…”
Section: Related Workmentioning
confidence: 99%