methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
MediumLowHighLow
Timedifferent
2-4 h15-45 min2-6 h1-2 Tage
Participantsdifferent
2-61-33-81-4
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Barrier Inventory, Failure Analysis per Barrier, Action BacklogADR File, Decision Log, RationaleFault Tree, Critical Paths, Cause Hypotheses, Control ActionsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
Root causeSafetyIncident
ArchitectureRationaleDocumentationGovernance
RiskRoot causeSafety
ArchitectureDocumentationCommunication
Add more methods