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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Rich Picture workspace showing the question, observations, and next decision.
Systems Thinking
Rich Picture
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration of Scatter Diagram with its method-specific working model.
Operations
Scatter Diagram
Purposedifferent
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.A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data.
Complexitydifferent
HighLowHighLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope30-90 min2-6 h30-90 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-103-101-4
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRich Picture, Problem Framing NotesFMEA Table, Risk Priority, Mitigation ActionsScatter Plot, Korrelationsnotiz, Hypothesenliste
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
Systems thinkingSoft systemsFramingVisualization
RiskQualityOperationsRoot cause
Root causeQualityVisualization
Add more methods