Route 11 - Testing

11.1 - Root Cause Analysis & Fishbone Diagrams

Root Cause Analysis

The process of identifying the root problem and solutions to that problem

What happened? ➡ How it happened? ➡ Why it happened? ➡ how can you stop it from happening again?

image

Fishbone Diagrams

A visual tool to help process the different processes that go into Root Cause Analysis


It can also be known as the Herringbone Diagram or the Ishikawa diagram

image

  1. The problem / statement that needs resolving
  2. Categorizations of causes to those issues in the form of branches
  3. All possible causes of that problem relating to each branch

11.2 - The process of applying Root Cause Analysis to Problem

5 Whys

Asking 5 increasingly deeper whys to get to the root cause of an issue by asking questions

When to use Root Cause Analysis?

During System Failure

When data within a server is lost

When an undefined process occurs

during system downtime

complaint / feedback from a stakeholder

How to use the Root Cause Analysis process

Identify the problem as well as the severity and impact it has on stakeholders

What information can you gather and infer from within the situation that could help you solve said issue

Identify the main cause(s) to that problem

Use the information you have gathered to formulate a plan to solve the issue

solve the issue

Testing methods and their application within the digital sector

Concept testing

Usability testing

Stress testing

Penetration testing

network penetration

physical penetration

social engineering testing

black box testing

white box testing