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 for Risk Storming.
Architecture
Risk Storming
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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.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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
2-6 h2-8 h60-90 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-85-124-12Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsAnnotated Diagram, Prioritized Risk List, Action BacklogPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignEventsDiscoveryWorkshop
RiskArchitectureWorkshopValidation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods