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 of Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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.
Complexitydifferent
MediumHighHighMedium
Timedifferent
2-4 hSeveral meetings plus preparation and analysis; total effort depends on scope1-6 Wochen1-4 h
Participantsdifferent
2-6Evaluation team, architects, and relevant stakeholders4-103-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Family Tree Diagram, Pattern Notes, Systemic MeasuresPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causePatternsIncidentSystemic
ArchitectureQualityRiskTradeoffsStakeholders
QualityProblem solvingRoot cause
Root causeProblem solvingQualityIncident
Add more methods