View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Architecture C4 Model |  Domain Modeling EventStorming |  Architecture Quality Attribute Workshop |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 15-45 min | 1-4 h | 2-8 h | 2-4 h |
Participantsdifferent | 1-3 | 1-5 | 5-12 | 5-15 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Quality Scenarios, Priority List, Architecture Concerns |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | Domain-Driven DesignEventsDiscoveryWorkshop | RequirementsArchitectureWorkshop |