2019 49th Annual IEEE/IFIP International Conference on Dependable Systems and Networks Workshops (DSN-W) 2019
DOI: 10.1109/dsn-w.2019.00021
|View full text |Cite
|
Sign up to set email alerts
|

Component-Level ASIL Decomposition for Automotive Architectures

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
8
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
4
2

Relationship

1
5

Authors

Journals

citations
Cited by 15 publications
(8 citation statements)
references
References 12 publications
0
8
0
Order By: Relevance
“…To perform our quantitative evaluation, we extend the model of [3] (which considered only failure probability, cost, and cable length related to an application) by adding the functional load and the communication load to the application nodes, and the two-dimensional coordinates to the physical nodes. To calculate the failure probability and the cost of the system we use the algorithms presented in [4]. Fault tree analysis is used to calculate the system failure probability, where the failure rates of the hardware resources are related to their ASIL specification on a logarithmic scale, as seen in Table 1.…”
Section: Proposed Methodology a System Modelmentioning
confidence: 99%
See 3 more Smart Citations
“…To perform our quantitative evaluation, we extend the model of [3] (which considered only failure probability, cost, and cable length related to an application) by adding the functional load and the communication load to the application nodes, and the two-dimensional coordinates to the physical nodes. To calculate the failure probability and the cost of the system we use the algorithms presented in [4]. Fault tree analysis is used to calculate the system failure probability, where the failure rates of the hardware resources are related to their ASIL specification on a logarithmic scale, as seen in Table 1.…”
Section: Proposed Methodology a System Modelmentioning
confidence: 99%
“…The authors of [6] improve the technique by adding additional checking elements to prove that the original Functional Safety Requirements (FSRs) are met. These additional checks can be found also in [3] and [4], where we define splitter and merger functionality to manage the redundant parts of the application. A splitter replicates its input to multiple output ports that are connected to redundant parts of the application; a merger decides which of its inputs, connected to the redundant parts of the application, should be forwarded on its output port.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…ISO 26262 abides to analyze dependent failures, portrayed in Figure 3, to show independence between software components used to implement independence requirements coming from ASIL decomposition at system level [26]. Thus, neither cascading failures nor common cause failures shall propagate among SWCs whether they are successive or placed in different paths, accordingly.…”
Section: Figure 3 Example Of Ffi Due To Information Exchange Interfementioning
confidence: 99%