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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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
HighLowLowHigh
Timedifferent
Mehrere Tage bis Wochen30 min Setup, dann laufend15-45 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-5 Modellierende, Stakeholder asynchron1-3 maintaining, briefing for everyone1-3Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncAsyncAsyncWorkshop + async
Outputdifferent
Simulation Model, Scenario ReportsRAID Log, Status Report SourceADR File, Decision Log, RationalePrioritized 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
RiskTrackingStakeholdersGovernance
ArchitectureRationaleDocumentationGovernance
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods