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 Fault Isolation.
Engineering
Fault Isolation
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
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
In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected.The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list.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
MediumLowHighLow
Timedifferent
30-180 min5-15 minSeveral meetings plus preparation and analysis; total effort depends on scope60-90 min
Participantsdifferent
1-61-5Evaluation team, architects, and relevant stakeholders4-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepPrioritized 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
TroubleshootingDiagnosisEngineering
StartupValidationCompetition
ArchitectureQualityRiskTradeoffsStakeholders
RiskArchitectureWorkshopValidation
Add more methods