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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
MediumHighHighLow
Timedifferent
1-3 h1-4 WochenSeveral meetings plus preparation and analysis; total effort depends on scope60-90 min
Participantsdifferent
2-81-6Evaluation team, architects, and relevant stakeholders4-12
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesExperiment results, Decision log, Learning summaryPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
ExperimentsGrowthAnalyticsValidation
ArchitectureQualityRiskTradeoffsStakeholders
RiskArchitectureWorkshopValidation
Add more methods