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 for Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration of System Dynamics Simulation with its method-specific working model.
Systems Thinking
System Dynamics Simulation
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
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.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.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.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.
Complexitydifferent
LowMediumHighHigh
Timedifferent
20-45 min45-120 minMehrere Tage bis WochenPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
1-102-61-5 Modellierende, Stakeholder asynchronArchitecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Behavior Over Time Graph, Trend Hypotheses, Key EventsChange Matrix, Cause Hypotheses, Validation Questions, Action ListSimulation Model, Scenario ReportsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives
Tagsno overlap
Systems thinkingPatternsDynamics
ChangeRoot causeTroubleshootingComparison
Systems thinkingDynamicsSimulationAnalysis
ArchitectureChangeAnalysisComparisonQuality
Add more methods