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
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
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.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.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
MediumMediumHighLow
Timedifferent
2-6 h2-8 hSeveral meetings plus preparation and analysis; total effort depends on scope60-90 min
Participantsdifferent
2-85-12Evaluation team, architects, and relevant stakeholders4-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignEventsDiscoveryWorkshop
ArchitectureQualityRiskTradeoffsStakeholders
RiskArchitectureWorkshopValidation
Add more methods