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
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)
Paper illustration of System Dynamics Simulation with its method-specific working model.
Systems Thinking
System Dynamics Simulation
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Purposedifferent
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.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 Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations.
Complexitydifferent
MediumHighHighMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additionalSeveral meetings plus preparation and analysis; total effort depends on scopeMehrere Tage bis Wochen1-3 h
Participantsdifferent
Designers, developers as users, and facilitationEvaluation team, architects, and relevant stakeholders1-5 Modellierende, Stakeholder asynchron2-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Prioritized 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 investigationsSimulation Model, Scenario ReportsCausal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureQualityRiskTradeoffsStakeholders
Systems thinkingDynamicsSimulationAnalysis
FeedbackSystems thinkingCausalityDynamics
Add more methods