TRACED: A Multi-Lens Root Cause Analysis Framework for Software Failures

TRACED is a root cause analysis (RCA) method for software failures. It replaces the single causal chain of 5 Whys with six bounded lenses: Trigger, Root defect, Amplification, Catch gap, Exit (recovery), and Defense.5 Whys is inexpensive and widely taught, but in software engineering it tends to stop at the first fixable cause. It rarely asks why the fault spread, why testing missed it, or why recovery was slow. TRACED asks each of those questions explicitly. Each lens allows at most three whys, every answer must cite empirical evidence, and every lens must end in an owned action ranked on a control hierarchy (Eliminate, Prevent, Detect, Contain, Recover).We apply both methods to an anonymised production incident: a backend outage after a container rebuild pulled in an unpinned transitive dependency (kombu 5.5.0) incompatible with the pinned Redis client (5.2.1). 5 Whys produced one root cause and one instance-level fix. TRACED identified findings across all six lenses and produced class-level actions that prevent the same failure mode across all dependencies. We define the TRACED Coverage Score (TCS), Defense Depth (DD), and Weighted Control Score (WCS), and propose an empirical study design to evaluate the method across incidents.

Authors

Publication Details

Journal
Zenodo (CERN European Organization for Nuclear Research)
Published
2026-11-13
DOI
https://doi.org/10.5281/zenodo.24194365
Primary Topic
Software System Performance and Reliability
Type
preprint
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
preprint

TRACED: A Multi-Lens Root Cause Analysis Framework for Software Failures

Serin Thomas
2 links
Zenodo (CERN European Organization for Nuclear Research)
Software System Performance and Reliability
preprint

TRACED: A Multi-Lens Root Cause Analysis Framework for Software Failures

Serin Thomas
preprint en

Abstract

TRACED is a root cause analysis (RCA) method for software failures. It replaces the single causal chain of 5 Whys with six bounded lenses: Trigger, Root defect, Amplification, Catch gap, Exit (recovery), and Defense.5 Whys is inexpensive and widely taught, but in software engineering it tends to stop at the first fixable cause. It rarely asks why the fault spread, why testing missed it, or why recovery was slow. TRACED asks each of those questions explicitly. Each lens allows at most three whys, every answer must cite empirical evidence, and every lens must end in an owned action ranked on a control hierarchy (Eliminate, Prevent, Detect, Contain, Recover).We apply both methods to an anonymised production incident: a backend outage after a container rebuild pulled in an unpinned transitive dependency (kombu 5.5.0) incompatible with the pinned Redis client (5.2.1). 5 Whys produced one root cause and one instance-level fix. TRACED identified findings across all six lenses and produced class-level actions that prevent the same failure mode across all dependencies. We define the TRACED Coverage Score (TCS), Defense Depth (DD), and Weighted Control Score (WCS), and propose an empirical study design to evaluate the method across incidents.

Zenodo (CERN European Organization for Nuclear Research)
Software System Performance and Reliability
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon