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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
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)
Purposedifferent
GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
1-3 h1-3 Wochen vom Draft bis zur Entscheidung20–45 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-83-20 ReviewerSmall cross-functional groupEvaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Gap Matrix, Action Plan, Risk NotesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRisk 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 investigations
Tagsno overlap
StrategyAnalysisPlanning
ArchitectureDecisionAsyncGovernance
RiskDecisionFailurePlanning
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods