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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.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.
Complexitydifferent
HighLowHighLow
Timedifferent
Mehrere Tage bis Wochen1-4 hPreparation, scenario analysis, and findings review; effort depends on scope1-2 Tage
Participantsdifferent
1-5 Modellierende, Stakeholder asynchron1-5Architecture experts and stakeholders for scenarios and weighting1-4
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Simulation Model, Scenario ReportsContext Diagram, Container Diagram, Component DiagramDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
ArchitectureCommunicationVisualization
ArchitectureChangeAnalysisComparisonQuality
ArchitectureDocumentationCommunication
Add more methods