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 StorytellingArchitecture Communication CanvasATAM (Architecture Tradeoff Analysis Method)C4 Model
| Criterion |  Knowledge Modeling Domain Storytelling |  Architecture Architecture Communication Canvas |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture C4 Model |
|---|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 1-2 h | 60-120 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 h |
Participantsdifferent | 2-8 | 2-8 | Evaluation team, architects, and relevant stakeholders | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | ArchitectureCommunicationStakeholdersCanvas | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureCommunicationVisualization |