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 Concept Mapping |  Engineering Goal Question Metric |  Domain Modeling Context Map |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 h | 90-180 min | 1-3 h | 1-2 h |
Participantsdifferent | 1-8 | 3-6 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | GQM Table, Metric Profiles | Context Map, Integration Patterns, Boundary Notes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | MetricsMeasurementEngineeringAlignment | Domain-Driven DesignBoundariesStrategy | AlignmentStakeholdersStrategyFacilitation |