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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Purposedifferent
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 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.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
HighHighMediumHigh
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scopeMehrere Tage bis Wochen2-4 h2-6 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-62-63-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsMORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsFamily Tree Diagram, Pattern Notes, Systemic MeasuresFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
Root causeSafetySystemicIncident
Root causePatternsIncidentSystemic
RiskRoot causeSafety
Add more methods