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 MORT Analysis with its method-specific working model.
Operations
MORT Analysis
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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.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.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
HighMediumLowLow
Timedifferent
Mehrere Tage bis Wochen2-4 h1-2 Tage15-45 min
Participantsdifferent
2-62-61-41-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
MORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsFamily Tree Diagram, Pattern Notes, Systemic MeasuresArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
Root causeSafetySystemicIncident
Root causePatternsIncidentSystemic
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods