An Introduction to Residuality Theory
summary
Residuality theory proposes a new unit, the residue, and a workflow of random simulation plus NKP analysis to design architectures that survive off‑spec events. It uses stressor lists, an incidence matrix (Design Structure Matrix), and a computed residual index (Y−X divided by number of stressors) to show measurable improvement. Empirical claims: huge state space (2^100000) collapses to ~3177 attractors; building residues for cases like key‑fob failure, license‑plate fallback and per‑minute billing produces architectures that statistically improve survival (p values reported).
AI-written summary · about
chapters (11)
- 0:00Residuality Theory intro
- 2:10Software architecture difficulty
- 10:54Complexity science meets SE
- 21:11Two-step software algorithm
- 24:00Defining residue in systems
- 30:25Stressor analysis example
- 37:30Monoliths vs microservices
- 40:42Coupling in architectures
- 46:18Measuring architecture improvement
- 51:17Residuality vs risk management
- 53:45Learning resources & closing
related talks
54mAn Introduction to Residuality Theory
53mAn Introduction to Residuality Theory
53mResiduality Theory
48mAn Introduction to Residuality Theory
50mKEYNOTE: Residuality Theory in Software Architecture
22mResilience Is Not Enough
20mFunctional Resonance Analysis: Diagramming Your System
03mBarry O'Reilly im Interview