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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
LowHighLow
Timedifferent
20–45 minSeveral meetings plus preparation and analysis; total effort depends on scope15-45 min
Participantsdifferent
Small cross-functional groupEvaluation team, architects, and relevant stakeholders1-3
Formatdifferent
WorkshopWorkshop + asyncAsync
Outputdifferent
Risk list, Mitigation plan, Assumption logPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsADR File, Decision Log, Rationale
Tagsno overlap
RiskDecisionFailurePlanning
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureRationaleDocumentationGovernance
Add more methods

Often compared together

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

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)
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond