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 of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.
Complexitydifferent
MediumHighMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur EntscheidungSeveral meetings plus preparation and analysis; total effort depends on scope60-120 min30 min Setup, dann laufend
Participantsdifferent
3-20 ReviewerEvaluation team, architects, and relevant stakeholders2-81-3 maintaining, briefing for everyone
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanRAID Log, Status Report Source
Tagsno overlap
ArchitectureDecisionAsyncGovernance
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureCommunicationStakeholdersCanvas
RiskTrackingStakeholdersGovernance
Add more methods