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 for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
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.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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
MediumMediumMediumHigh
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung45-90 min1-3 TageSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-20 Reviewer3-81-4Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsCATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsArchitecture Views, Cross-view Notes, RationalePrioritized 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
Systems thinkingFramingStakeholders
DocumentationStakeholdersArchitecture
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods