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
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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)
Purposedifferent
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.
Complexitydifferent
HighLowHighMedium
Timedifferent
2-6 h1-2 TageMehrere Tage bis Wochen2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-61-41-5 Modellierende, Stakeholder asynchronDesigners, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Stock and Flow Model, Dynamics Notes, Simulation HypothesesArchitecture Document, Context View, Runtime View, Deployment ViewSimulation Model, Scenario ReportsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
DynamicsSimulationFeedbackSystems thinking
ArchitectureDocumentationCommunication
Systems thinkingDynamicsSimulationAnalysis
ArchitectureEngineeringFeedbackValidationTasks
Add more methods