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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.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
LowLowMediumHigh
Timedifferent
1-2 h60-90 min1-4 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-104-123-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesAnnotated Diagram, Prioritized Risk List, Action BacklogProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
RiskArchitectureWorkshopValidation
Root causeProblem solvingQualityIncident
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods