View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Domain StorytellingEventStormingATAM (Architecture Tradeoff Analysis Method)Assumption Surfacing
| Criterion |  Knowledge Modeling Domain Storytelling |  Domain Modeling EventStorming |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 1-2 h | 2-8 h | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 2-8 | 5-12 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Domain-Driven DesignEventsDiscoveryWorkshop | ArchitectureQualityRiskTradeoffsStakeholders | AssumptionsRiskDecisionDiscovery |