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 Risk Storming.
Architecture
Risk Storming
Paper illustration of System Dynamics Simulation with its method-specific working model.
Systems Thinking
System Dynamics Simulation
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.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.A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics.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
LowHighHighHigh
Timedifferent
60-90 minMehrere Tage bis Wochen2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
4-121-5 Modellierende, Stakeholder asynchron1-6Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogSimulation Model, Scenario ReportsStock and Flow Model, Dynamics Notes, Simulation HypothesesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskArchitectureWorkshopValidation
Systems thinkingDynamicsSimulationAnalysis
DynamicsSimulationFeedbackSystems thinking
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods