methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Diary Study.
UX Research
Diary Study
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
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.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.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope1-4 Wochen2-8 h
Participantsdifferent
2-8Evaluation team, architects, and relevant stakeholders5-205-12
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsDiary Entries, Longitudinal Patterns, Experience TimelineEvent Timeline, Ubiquitous Language, Boundaries, Open Questions
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ArchitectureQualityRiskTradeoffsStakeholders
UX researchTrackingBehavior
Domain-Driven DesignEventsDiscoveryWorkshop
Add more methods