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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
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.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.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
MediumHighHigh
Timedifferent
1-3 Wochen vom Draft bis zur EntscheidungPreparation, scenario analysis, and findings review; effort depends on scopeSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-20 ReviewerArchitecture experts and stakeholders for scenarios and weightingEvaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tags1 shared
ArchitectureDecisionAsyncGovernance
ArchitectureChangeAnalysisComparisonQuality
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record