View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Bounded Context Canvas |  UX Research HEART Framework |  Domain Modeling Domain Context Map |  UX Research Contextual Inquiry |
|---|---|---|---|---|
Purposedifferent | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 120 min initial, dann laufend | 1-3 h | 1-3 Wochen |
Participantsdifferent | 3-8 | 3-6 | 3-10 | 4-12 Beobachtungen |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Canvas, Glossary, Integration Notes | HEART-GSM Table, Dashboard | Domain Context Map, Boundary Notes, Ownership Map | Field Notes, Workflow Insights, Pain Points |
Tagsno overlap | Domain-Driven DesignBoundariesModeling | MetricsUX researchMeasurementSatisfaction | Domain-Driven DesignContextBoundaries | UX researchObservationContext |