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 for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.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.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.
Complexitydifferent
HighLowHighHigh
Timedifferent
2-6 h20-45 min2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-101-83-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
FMEA Table, Risk Priority, Mitigation ActionsOwnership Reflection, Action Commitment, Coaching NotesFault Tree, Critical Paths, Cause Hypotheses, Control ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskQualityOperationsRoot cause
ResponsibilityLeadershipTeam
RiskRoot causeSafety
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods