2008
DOI: 10.3182/20080706-5-kr-1001.00696
|View full text |Cite
|
Sign up to set email alerts
|

Non-coherent Modelling in Compositional Fault Tree Analysis

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
9
0

Year Published

2009
2009
2016
2016

Publication Types

Select...
4
1
1

Relationship

3
3

Authors

Journals

citations
Cited by 10 publications
(9 citation statements)
references
References 10 publications
0
9
0
Order By: Relevance
“…An extended version of the above paper was published as book chapter in . The material presented in chapter 6 was presented & published in (Sharvia & Papadopoulos, 2008), and contributed to (Adachi et al, 2010). Tables Table 1: Example of FHA on car brake function (source: Johannessen et al, 2001) .... 30 …”
Section: Specificallymentioning
confidence: 99%
See 2 more Smart Citations
“…An extended version of the above paper was published as book chapter in . The material presented in chapter 6 was presented & published in (Sharvia & Papadopoulos, 2008), and contributed to (Adachi et al, 2010). Tables Table 1: Example of FHA on car brake function (source: Johannessen et al, 2001) .... 30 …”
Section: Specificallymentioning
confidence: 99%
“…Despite these arguments, (Johnston & Mathews, 1983) and (Sharvia & Papadopoulos, 2008) reviewed several scenarios where inclusion of NOT benefits failure modelling.…”
Section: General Analysis Of Detectabilitymentioning
confidence: 99%
See 1 more Smart Citation
“…In aircraft industries, the symptom has many features for only one data source, that is, the possible responses of test may be more than one [3]. So the diagnostic dictionary for representing the relation between the faults and the test available to a system will not be a binary test matrix [4].…”
Section: Introductionmentioning
confidence: 99%
“…With respect to the previous example, if components and have failed, then should be the last component to be repaired to avoid system failure. Furthermore, PI identification allows taking additional counteracting measures to prevent system failure, for example by forcing the failure of component when components and have already failed [6].…”
mentioning
confidence: 99%