View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations ABC Analysis |  Domain Modeling Context Map |  Engineering Goal Question Metric |
|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30-60 min | 1-3 h | 90-180 min |
Participantsdifferent | 1-5 | 2-8 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | ABC Classification, Focus Rules, Control List | Context Map, Integration Patterns, Boundary Notes | GQM Table, Metric Profiles |
Tagsno overlap | PrioritizationOperationsPortfolio | Domain-Driven DesignBoundariesStrategy | MetricsMeasurementEngineeringAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
