Design for Safety 2017
DOI: 10.1002/9781118974339.ch9
|View full text |Cite
|
Sign up to set email alerts
|

Fault Tree Analysis for System Safety

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2018
2018
2024
2024

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(5 citation statements)
references
References 4 publications
0
5
0
Order By: Relevance
“…Based on the fault tree analysis and the bow-tie model analyzed the 10 most common accident mechanisms. Each of them has over 30 cases, which is deemed sufficient for this purpose [31,32]. The software utilized was SPSS version 22.…”
Section: Fig 3: Flowchart Of This Research Methodologymentioning
confidence: 99%
“…Based on the fault tree analysis and the bow-tie model analyzed the 10 most common accident mechanisms. Each of them has over 30 cases, which is deemed sufficient for this purpose [31,32]. The software utilized was SPSS version 22.…”
Section: Fig 3: Flowchart Of This Research Methodologymentioning
confidence: 99%
“…A broad range of methods and techniques already exist for both safety and security analysis. Examples of safety techniques are Functional Hazard Assessment (FHA) (Eurocontrol, 2004), Preliminary Hazard Analysis (PHA) (Ericson, 2005), HAZard and OPerability (HAZOP) (Ericson, 2005, Winther el al., 2001, Failure Mode and Effect Analysis (FMEA) (Stamatis, 1995), Fault Tree Analysis (FTA) (Ericson, 2005), Event Tree Analysis (ETA) (Ericson, 1999;, and Boolean-logic Driven Markov Processes (BDMP) that models malicious and accidental scenarios in a tree structure (Pietre-Cambacedes & Bouissou, 2010). Examples of security techniques are attack trees (Schneier, 1999;2000), threat trees (Amoroso, 1994), various adaptations of UML (Rodriguez et al, 2006, Jurjens, 2002, Lodderstedt et al, 2002, abuse cases (McDermott & Fox, 1999), misuse cases (Sindre & Opdahl, 2000;, security policies (Anton & Earp, 2000), KAOS with anti-goals (Dardenne et al, 1993;van Lamsweerde, 2000;van Lamsweerde & Letier, 2004), extensions of i* (Liu et al 2003;Elahi, 2012), Secure Tropos (Mouratidis et al, 2005;2007;Massacci & Zannone, 2006), abuse frames (Lin et al, 2003;2004), security patterns (Schumacher et al, 2005) and risk-based elicitation of security requirements (Matulevicius et al, 2008;Herrmann et al, 2011).…”
Section: Safety and Security Methodsmentioning
confidence: 99%
“…One of the most prevalent methods for effectively conducting risk analysis at system level is FTA, which is used to analyze, visually depict, and evaluate failure pathways within system [8]. The central feature of FTA lies in the use of a logic diagram to illustrate the correlation between system failure or accidents and the underlying causes, typically rooted in component failure [9].…”
Section: Fault Tree Analysis (Fta)mentioning
confidence: 99%