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 System Dynamics Simulation with its method-specific working model.
Systems Thinking
System Dynamics Simulation
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports.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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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
HighHighLowHigh
Timedifferent
Mehrere Tage bis Wochen2-6 h30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-5 Modellierende, Stakeholder asynchron3-102-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
Simulation Model, Scenario ReportsFMEA Table, Risk Priority, Mitigation ActionsFishbone Diagram, Cause Categories, Investigation BacklogPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
RiskQualityOperationsRoot cause
Root causeQualityOperations
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods