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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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
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.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.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
HighMediumHighMedium
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope2–4 h review as a planning range; preparation and evaluation additionalMehrere Tage bis Wochen1-3 h
Participantsdifferent
Architecture experts and stakeholders for scenarios and weightingDesigners, developers as users, and facilitation1-5 Modellierende, Stakeholder asynchron2-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsSimulation Model, Scenario ReportsCausal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
ArchitectureEngineeringFeedbackValidationTasks
Systems thinkingDynamicsSimulationAnalysis
FeedbackSystems thinkingCausalityDynamics
Add more methods