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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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.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
LowLowMediumHigh
Timedifferent
1-4 h15-30 min45-120 minPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
1-52-62-6Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Context Diagram, Container Diagram, Component DiagramRoot cause notes, CountermeasuresChange Matrix, Cause Hypotheses, Validation Questions, Action ListDomain 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
ArchitectureCommunicationVisualization
Root causeIncidentLeanProblem solving
ChangeRoot causeTroubleshootingComparison
ArchitectureChangeAnalysisComparisonQuality
Add more methods