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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
MediumMediumHighLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung60-120 minSeveral meetings plus preparation and analysis; total effort depends on scope1-2 Tage
Participantsdifferent
3-20 Reviewer2-8Evaluation team, architects, and relevant stakeholders1-4
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsArchitecture Document, Context View, Runtime View, Deployment View
Tags1 shared
ArchitectureDecisionAsyncGovernance
ArchitectureCommunicationStakeholdersCanvas
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureDocumentationCommunication
Add more methods