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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 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
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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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
LowMediumHighLow
Timedifferent
1-2 Tage45-90 minPreparation, scenario analysis, and findings review; effort depends on scope15-30 min
Participantsdifferent
1-42-5Architecture experts and stakeholders for scenarios and weighting2-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewA3 Report, Action Plan, Root Cause AnalysisDomain 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
ArchitectureDocumentationCommunication
LeanProblem solvingCoachingOperations
ArchitectureChangeAnalysisComparisonQuality
Root causeIncidentLeanProblem solving
Add more methods