방법 비교

	위험 기반 고장 트리 분석	베이지안 고장 수목 분석
분야	실험설계	실험설계
계열	Process / pipeline	Process / pipeline
기원 연도	1961 (FTA origin); risk-based integration formalised 1975–1981	2001 (BFTA mapping); Bayesian networks: 1988
창시자	H.A. Watson (Bell Labs) and developed further by Boeing/U.S. Air Force; risk-based extension via NRC probabilistic risk assessment programs	Andrea Bobbio, Luca Portinale et al. (mapping FTA to Bayesian networks); Judea Pearl (Bayesian networks)
유형	Quantitative safety and reliability analysis	Probabilistic reliability / safety analysis
원전	Vesely, W. E., Goldberg, F. F., Roberts, N. H., & Haasl, D. F. (1981). Fault Tree Handbook. U.S. Nuclear Regulatory Commission, NUREG-0492.	Bobbio, A., Portinale, L., Minichino, M., & Ciancamerla, E. (2001). Improving the analysis of dependable systems by mapping fault trees into Bayesian networks. Reliability Engineering & System Safety, 71(3), 249–260.
별칭	RB-FTA, risk-informed FTA, quantitative fault tree analysis, probabilistic fault tree analysis	BFTA, Bayesian FTA, Bayesian network fault tree, probabilistic fault tree analysis
관련	6	5
요약	Risk-based fault tree analysis (RB-FTA) combines classical fault tree analysis with explicit quantitative risk assessment. Starting from an undesired top event, the analyst decomposes it into contributing causes using AND/OR logic gates, assigns failure probabilities to basic events from reliability databases or historical data, and then propagates those probabilities through the tree to compute top-event likelihood. The result is expressed as risk — probability weighted by consequence severity — enabling prioritisation of safety interventions by their actual risk reduction impact.	Bayesian Fault Tree Analysis (BFTA) extends classical fault tree analysis by converting the fault tree structure into an equivalent Bayesian network, enabling probabilistic inference in both forward (prediction) and backward (diagnosis) directions. This integration allows analysts to update failure probability estimates with observed evidence, quantify uncertainty explicitly, and identify the most probable root causes of a top-level system failure.