View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Diary Study |  Domain Modeling EventStorming |  Architecture C4 Model |  Architecture Quality Attribute Workshop |
|---|---|---|---|---|
Purposedifferent | When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. | 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. | 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. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-4 Wochen | 2-8 h | 1-4 h | 2-4 h |
Participantsdifferent | 5-20 | 5-12 | 1-5 | 5-15 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Context Diagram, Container Diagram, Component Diagram | Quality Scenarios, Priority List, Architecture Concerns |
Tagsno overlap | UX researchTrackingBehavior | Domain-Driven DesignEventsDiscoveryWorkshop | ArchitectureCommunicationVisualization | RequirementsArchitectureWorkshop |