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 |  Engineering Goal Question Metric |  Domain Modeling Domain Context Map |  UX Research HEART Framework |
|---|---|---|---|---|
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 technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 90-180 min | 1-3 h | 120 min initial, dann laufend |
Participantsdifferent | 3-8 | 3-6 | 3-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Canvas, Glossary, Integration Notes | GQM Table, Metric Profiles | Domain Context Map, Boundary Notes, Ownership Map | HEART-GSM Table, Dashboard |
Tagsno overlap | Domain-Driven DesignBoundariesModeling | MetricsMeasurementEngineeringAlignment | Domain-Driven DesignContextBoundaries | MetricsUX researchMeasurementSatisfaction |