WBA Guide
WBA Guide
Overview
A Why-Because Analysis (WBA) [Ladkin 01, Ladkin 02] starts with gathering information about the incident (Figure 1). This information is then used to construct either a
List of Facts (facts listed alone) or a Why-Because List.
The construction of the Why-Because Graph (WB Graph, WBG) starts with determining the mishap (the top node). Then the necessary causal factors (NCF) that finally
led to the mishap are determined, using the Why-Because List, until a chosen level of
detail is reached. Finally, the quality (correctness and explanatory completeness) of the
WBG is assured by detecting and correcting errors. A report can then be written using
the WBG.
The WBA process is factored here into eight subprocesses, explained using flowchart
notation.
Gather Information
As shown in Figure 2, the first step is information gathering. First, the sources of information must be identified. These can be, for example, witness reports, responsible
authorities, or applicable documentation. (It has proven useful to get printed copies of
the material.)
The quality of the information must be assessed. Checking the sources and doing
some background research helps. If a team is performing the WBA, the information
material can be discussed. Finally, the useful information material is selected.
If inadequacies or errors are found, they are corrected by changing or adding causal
relations, removing nodes, or adding nodes. Adding nodes requires carefully extending the List of Facts / Why-Because List and then returning to the process of determining NCFs (Figure 9).
If it is determined that the quality of the WBG must be improved, the Counterfactual
Test should be applied once again to check the causal relations. When the entire WB
Graph has been checked in this manner, it is finished.
Glossary
Auxiliary List of Facts (auxLoF) Auxiliary List of Facts are optional. The facts are
arranged according to a classification system, such as timestamp or actor involved.
Auxiliary List of Facts help to gain a better understanding of an incident. The facts
are notated with a serial number, a short description, their class, and a reference
to their source.
Causal Completeness Test (CCT) A technical criterion for determining sufficiency of
causal explanation. The CCT applies between a collection A1 , A2 , ....., An of facts
and a fact B. The CCT is satisfied when (a) each Ak is an NCF of B; and (b) the
Causal Sufficiency Criterion holds between the set A 1 , A2 , ....., An and B. The technical definition may be found in [Ladkin 01].
Causal Sufficiency Criterion The Causal Sufficiency Criterion between a set of facts
A1 , A2 , ....., An and a fact B is that, given the world as it more or less is, it is impossible for B not to have happened if all of the Ak have happened. That is, had the
world been just sufficiently different that B did not happen, then at least one of
the Ak (not necessarily the same one for each different circumstance) would not
have happened either. The technical definition may be found in [Ladkin 01].
Counterfactual Test (CT) The criterion for determining a Necessary Causal Factor.
Given two facts, A and B, CT asks whether, if the world had been just sufficiently
different that A had not happened, whether B would have happened anyway.
If B would not have happened in this situation in which A did not happen, the
Counterfactual Test is passed, and A is a Necessary Causal Factor of B.
List of Facts (LoF) The List of Facts contains the significant facts that are causal factors of the incident. The facts are notated with a serial number, a short description,
and a reference to their source.
Necessary Causal Factor (NCF) A fact that causally affects the occurrence of another
fact in the course of events of the incident. This is determined by applying the
Counterfactual Test. In Why-Because Graphs, NCFs are represented by child
nodes.
Topnode The top node of the Why-Because Graph represents the failure of the examined system (mishap).
Why-Because Graph (WB Graph, WBG) The Why-Because Graph shows as edges the
causal relations between the facts, shown as nodes, that led to the failure of a system.
Why-Because List (WB List) The Why-Because List contains the facts that are causal
factors of the incident, arranged in pairs consisting of a necessary causal factor
and its effect. Every single fact is notated with a serial number, a short description,
and a reference to its source.
References
[IBM 69]
[Ladkin 01]
[Ladkin 02]
[Paul-Stve 05] Thilo Paul-Stve. Formal Task Analysis of Graphical System Engineering Software Use. Rapport technique, RVS Group, Faculty of Technology, University of Bielefeld, March 2005. Available at www.rvs.unibielefeld.de Publications Theses Written in the Group.
incident occurred
Gather Information
(GI)
Determine Facts
(DF)
use List of
Facts?
yes
no
Create List of
Facts (CL)
clear picture of
course of events /
participants?
no
yes
Determine Mishap /
Topnode (DM)
Determine Necessary
Causal Factors (DN)
Assure Quality
(AQ)
Correct WB-Graph
(CW)
create
report
finished
incident occurred
Gather Information
identify sources of information (consult
(GI)
expert sources and responsible authorities,
do internet research, ...)
get copies
information
material
document
sources
sift through
information material
yes
working in a
team?
no
select useful
information material
Determine Facts
(DF)
information
material
Gather Information
information
material
Determine Facts
(DF)
read selected
information material
identify statements
concerning the course
of events
sort out
presumptions
use List of
Facts?
notated
facts
10
Create Auxiliary
List of Facts (CA)
List of
Facts
notated
facts
no
Determine Mishap /
Topnode (DM)
yes
clear picture of
course of events /
participants?
no
yes
use List of
Facts?
Determine Facts
(DF)
yes
check for
completeness and
consistency:
sound?
yes
do counterfactual
test: sound?
do counterfactual
test
no
no
WhyBecause
List
clear picture of
course of events /
participants?
yes
no
WhyBecause
List
List of
Facts
Determine Mishap /
Topnode (DM)
11
Auxiliary
List of
Facts
Create Auxiliary
List of Facts
(CA)
no
clear picture of
course of events /
participants?
yes
Determine Mishap /
Topnode
review facts
WhyBecause
List
assess facts
List of
Facts
yes
discuss facts in group
working in a
team?
no
Determine Necessary
Causal Factors (DN)
12
WhyBecause
Graph
Determine Mishap /
Topnode (DM)
WhyBecause
List
Determine Necessary
Causal Factors
(DN)
CW 5
DN 1:
review List of Facts /
Why-Because List
assess facts
List of
Facts
yes
discuss facts in group
WhyBecause
Graph
working in a
team?
no
contemplate node to
examine further
WhyBecause
Graph
desired level of
detail reached?
no
yes
Assure Quality
(AQ)
CW Correct WB-Graph
CW 5: extend List of Facts / Why-Because List
13
Determine Necessary
Causal Factors (DN)
WhyBecause
List
Assure Quality
(AQ)
CW 3
AQ 1:
do causal
completeness test
CW 4
AQ 2:
incident described
sufficiently?
List of
Facts
no
yes
CW 1
look at WB-Graph
WhyBecause
Graph
sift through
causalities of graph
yes
discuss causalities
of graph
working in a
team?
no
AQ 3:
errors? unsound?
yes
no
AQ 4:
do counterfactual
test
improve quality?
yes
CW 2
no
yes
create
report
finished
AQ 5:
counterfactual test
passed?
CW Correct WB-Graph
CW 1: detected wrong or missing causal relation?
CW 2: further factors required to explain causal factor?
CW 3: change or add causal relation
CW 4: remove node
CW 5: extend List of Facts / Why-Because List
14
no
15
yes
no
CW 2:
further factors
required to explain
causal factor?
no
AQ 5
yes
yes
detected superfluous
node?
no
CW 1:
detected wrong
or missing causal
relation?
AQ 3
AQ 4
WhyBecause
Graph
AQ 2
List of
Facts
WhyBecause
List
CW 5:
extend List of Facts /
Why-Because List
CW 4:
remove node
CW 3:
change or add
causal relation
Correct WB-Graph
(CW)
DN 1
WhyBecause
Graph
AQ 1