Lesson plan

Why–because analysis

Why–because analysis (WBA) is a method for accident analysis using graph theory. It is independent of application domain and has been used to analyse, among others, aviation-, railway-, marine-, and computer-related accidents and incidents. It is mainly used as an after-the-fact (or a posteriori) analysis method, and it is applied to ensure that results are objective, falsifiable and reproducible. The result of such an analysis is a why–because graph (WBG), a type of causal notation used to represent interdependencies within a system and depict causal relations between factors of an accident. It is a directed acyclic graph, the nodes of which are factors. Directed edges denote cause–effect relations between the factors. Why–because analyses start with questions regarding the nature of an accident (which is easy to define in many cases), followed by an iterative process to determine causes. When causes for an accident have been identified, formal tests are applied to all potential cause-effect relations. This process can be iterated for newfound causes, and so on, until a satisfactory result has been achieved. At each node (factor), each contributing cause (related factor) must have been necessary to cause the accident, and the totality of causes must have been sufficient to do so.

Back to article

Article summary

Why–because analysis (WBA) is a method for accident analysis using graph theory. It is independent of application domain and has been used to analyse, among others, aviation-, railway-, marine-, and computer-related accidents and incidents. It is mainly used as an after-the-fact (or a posteriori) analysis method, and it is applied to ensure that results are objective, falsifiable and reproducible. The result of such an analysis is a why–because graph (WBG), a type of causal notation used to represent interdependencies within a system and depict causal relations between factors of an accident. It is a directed acyclic graph, the nodes of which are factors. Directed edges denote cause–effect relations between the factors. Why–because analyses start with questions regarding the nature of an accident (which is easy to define in many cases), followed by an iterative process to determine causes. When causes for an accident have been identified, formal tests are applied to all potential cause-effect relations. This process can be iterated for newfound causes, and so on, until a satisfactory result has been achieved. At each node (factor), each contributing cause (related factor) must have been necessary to cause the accident, and the totality of causes must have been sufficient to do so.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.