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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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
HighMediumHigh
Timedifferent
Mehrere Tage bis Wochen2–4 h review as a planning range; preparation and evaluation additionalSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-5 Modellierende, Stakeholder asynchronDesigners, developers as users, and facilitationEvaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
Simulation Model, Scenario ReportsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsPrioritized 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
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Risk Storming.
Architecture
Risk Storming