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 for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration for Risk Storming.
Architecture
Risk Storming
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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
MediumLowMediumHigh
Timedifferent
30-240 min60-90 min60-120 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-64-122-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryAnnotated Diagram, Prioritized Risk List, Action BacklogCommunication Canvas, Stakeholder Messages, Architecture Communication 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
TroubleshootingProblem solvingDiagnosis
RiskArchitectureWorkshopValidation
ArchitectureCommunicationStakeholdersCanvas
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods