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)
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
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.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.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots.
Complexitydifferent
MediumHighHighLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional2-6 hPreparation, scenario analysis, and findings review; effort depends on scope20-45 min
Participantsdifferent
Designers, developers as users, and facilitation1-6Architecture experts and stakeholders for scenarios and weighting1-10
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsStock and Flow Model, Dynamics Notes, Simulation HypothesesDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesBehavior Over Time Graph, Trend Hypotheses, Key Events
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
DynamicsSimulationFeedbackSystems thinking
ArchitectureChangeAnalysisComparisonQuality
Systems thinkingPatternsDynamics
Add more methods