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
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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.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.
Complexitydifferent
LowHighHighLow
Timedifferent
1-4 h1-6 WochenPreparation, scenario analysis, and findings review; effort depends on scope15-30 min
Participantsdifferent
1-54-10Architecture experts and stakeholders for scenarios and weighting2-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Context Diagram, Container Diagram, Component Diagram8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureCommunicationVisualization
QualityProblem solvingRoot cause
ArchitectureChangeAnalysisComparisonQuality
Root causeIncidentLeanProblem solving
Add more methods