View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Knowledge Mapping |  Domain Modeling Bounded Context Canvas |  Engineering Goal Question Metric |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 h | 90-180 min | 1-3 h |
Participantsdifferent | 3-12 | 3-8 | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Context Canvas, Glossary, Integration Notes | GQM Table, Metric Profiles | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | KnowledgeMappingRisk | Domain-Driven DesignBoundariesModeling | MetricsMeasurementEngineeringAlignment | Domain-Driven DesignBoundariesStrategy |