2014
DOI: 10.1007/978-3-319-10557-4_43
|View full text |Cite
|
Sign up to set email alerts
|

Towards a Cross-Domain Software Safety Assurance Process for Embedded Systems

Abstract: In this work, we outline a cross-domain assurance process for safety-relevant software in embedded systems. This process aims to be applied in various different application domains and in conjunction with any development methodology. With this approach we plan to reduce the growing effort for safety assessment in embedded systems by reusing safety analysis techniques and tools for the product development in different domains.

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2015
2015
2024
2024

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(6 citation statements)
references
References 1 publication
0
6
0
Order By: Relevance
“…This is understandable for those deriving from IEC 61508. However, even other non‐IEC 61508 related standards have strong commonalities which enable the definition of a cross‐domain safety assurance process sketched in Figure 3 36 and also discussed in previous works 37,38 . It consists of the following generic and domain‐specific steps:…”
Section: State Of the Art On Safety And Security Standardsmentioning
confidence: 81%
“…This is understandable for those deriving from IEC 61508. However, even other non‐IEC 61508 related standards have strong commonalities which enable the definition of a cross‐domain safety assurance process sketched in Figure 3 36 and also discussed in previous works 37,38 . It consists of the following generic and domain‐specific steps:…”
Section: State Of the Art On Safety And Security Standardsmentioning
confidence: 81%
“…This can be a reason of why very few attempts have been made. Zeller et al [35] propose a cross-domain assurance process in conjunction with a development methodology for safety-relevant software. The objective was to reduce the effort required to perform a safety assessment by reusing safety analysis techniques and tools as well as artefacts produced during the safety assurance process.…”
Section: Related Literaturementioning
confidence: 99%
“…To argue the safety of a developed system, a safety case is compiled as a result of a safety assurance process [Zeller et al 2014]. The safety argument needs to make clear that all safety risks were identified and to demonstrate how these risks were mitigated.…”
Section: Research Question 3: Feasibility Of Software Lifecycle Activmentioning
confidence: 99%
“…One important aspect of developing safety critical software is the compilation of a safety case to argue that the developed system is safe for use [Zeller et al 2014]. The safety argument needs to demonstrate that all safety risks have been identified and how exactly they have been mitigated.…”
Section: Introductionmentioning
confidence: 99%