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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for 3-Circle Venn Diagram
Facilitation
3-Circle Venn Diagram
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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.When three perspectives matter at the same time, a Three-Circle Venn Diagram shows the overlaps and remainders precisely. It makes visible where shared effect arises and where only a partial perspective applies.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
LowHighLowHigh
Timedifferent
20-40 min initial, dann laufendPreparation, scenario analysis, and findings review; effort depends on scope15-45 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-15Architecture experts and stakeholders for scenarios and weighting2-8Evaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
ROAM Board, Owner ListDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesVenn Diagram, Overlap Notes, DifferentiatorsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskAgileTrackingAlignment
ArchitectureChangeAnalysisComparisonQuality
ComparisonFacilitationAlignment
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods