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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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
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.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.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.
Complexitydifferent
HighLowLowMedium
Timedifferent
Mehrere Tage bis Wochen15-45 min1-2 Tage2-4 h
Participantsdifferent
2-61-31-42-6
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
MORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment ViewBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Root causeSafetySystemicIncident
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Root causeSafetyIncident
Add more methods