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 Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
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.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.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.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
MediumMediumHighHigh
Timedifferent
2-4 h2-4 hSeveral meetings plus preparation and analysis; total effort depends on scope2-6 h
Participantsdifferent
2-62-6Evaluation team, architects, and relevant stakeholders3-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Barrier Inventory, Failure Analysis per Barrier, Action BacklogFamily Tree Diagram, Pattern Notes, Systemic MeasuresPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
Root causeSafetyIncident
Root causePatternsIncidentSystemic
ArchitectureQualityRiskTradeoffsStakeholders
RiskRoot causeSafety
Add more methods