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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree 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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.
Complexitydifferent
HighHighLowHigh
Timedifferent
Mehrere Tage bis WochenSeveral meetings plus preparation and analysis; total effort depends on scope30-60 min2-6 h
Participantsdifferent
2-6Evaluation team, architects, and relevant stakeholders2-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
MORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsFishbone Diagram, Cause Categories, Investigation BacklogFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
Root causeSafetySystemicIncident
ArchitectureQualityRiskTradeoffsStakeholders
Root causeQualityOperations
RiskRoot causeSafety
Add more methods