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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.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.CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.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
MediumLowMediumHigh
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung1-2 Tage45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-20 Reviewer1-43-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArchitecture Document, Context View, Runtime View, Deployment ViewCATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureDecisionAsyncGovernance
ArchitectureDocumentationCommunication
Systems thinkingFramingStakeholders
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods