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