View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Domain Storytelling |  Architecture SAAM (Software Architecture Analysis Method) |  Operations A3 Problem Solving |
|---|---|---|---|
Purposedifferent | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | 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 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. |
Complexitydifferent | Low | High | Medium |
Timedifferent | 1-2 h | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 2-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Domain 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 | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | ArchitectureChangeAnalysisComparisonQuality | LeanProblem solvingCoachingOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
