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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
HighMediumHighLow
Timedifferent
Mehrere Tage bis Wochen1-3 hPreparation, scenario analysis, and findings review; effort depends on scope15-30 min
Participantsdifferent
1-5 Modellierende, Stakeholder asynchron2-8Architecture experts and stakeholders for scenarios and weighting2-6
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Simulation Model, Scenario ReportsCause Tree, Evidence Notes, CountermeasuresDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesRoot cause notes, Countermeasures
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
Root causeTreeIncidentQuality
ArchitectureChangeAnalysisComparisonQuality
Root causeIncidentLeanProblem solving
Add more methods