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 Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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
Purposedifferent
For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.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.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
2-4 h1-2 Tage2-4 h15-45 min
Participantsdifferent
2-61-42-61-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Family Tree Diagram, Pattern Notes, Systemic MeasuresArchitecture Document, Context View, Runtime View, Deployment ViewBarrier Inventory, Failure Analysis per Barrier, Action BacklogADR File, Decision Log, Rationale
Tagsno overlap
Root causePatternsIncidentSystemic
ArchitectureDocumentationCommunication
Root causeSafetyIncident
ArchitectureRationaleDocumentationGovernance
Add more methods