Our software fault tree analysis training covers the most common root causes of software failures and guides brainstorming them during a system fault tree analysis. This class is intended for software engineers, system engineers, safety engineers, and RAM engineers. A common mistake in software safety is analyzing software faults in isolation, as a “black box” that either works or fails. For a Fault Tree Analysis or software (FTA) to be effective, software must be integrated into the system-level fault tree from a functional perspective.
Software doesn't wear out. So stop treating it like it does.
A CSCI is how software is managed. It's not how it fails.
Say how it can fail in a functional way. Ex: “The software allowed an inadvertent state change.”
Built from the world's largest defect density benchmarking study.
The hardware-centric approach doesn't work. Software doesn't wear out. The fault tree must focus on functional failures.
The root causes are built from the world's largest database of software failures analyzed by root cause
Analyzing software root causes in a structured manner is faster than analyzing them in an ad hoc manner.