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)
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
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 recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.
Complexitydifferent
HighLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope20-60 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders1-4
Formatdifferent
Workshop + asyncAsync
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRunbook, Checklist, Escalation Path
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
OperationsReliabilityDocumentation
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond