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 arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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.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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.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
LowHighMediumLow
Timedifferent
1-2 TagePreparation, scenario analysis, and findings review; effort depends on scope1-4 h15-30 min
Participantsdifferent
1-4Architecture experts and stakeholders for scenarios and weighting3-82-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureChangeAnalysisComparisonQuality
Root causeProblem solvingQualityIncident
Root causeIncidentLeanProblem solving
Add more methods