View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Event Modeling |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  UX Research Diary Study |
|---|---|---|---|
Purposedifferent | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 2-6 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 Wochen |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 5-20 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Diary Entries, Longitudinal Patterns, Experience Timeline |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | ArchitectureQualityRiskTradeoffsStakeholders | UX researchTrackingBehavior |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
