View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research HEART Framework |  Architecture Architecture Decision Record |  Engineering Goal Question Metric |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 120 min initial, dann laufend | 15-45 min | 90-180 min | 1-2 Tage |
Participantsdifferent | 3-6 | 1-3 | 3-6 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | HEART-GSM Table, Dashboard | ADR File, Decision Log, Rationale | GQM Table, Metric Profiles | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | MetricsUX researchMeasurementSatisfaction | ArchitectureRationaleDocumentationGovernance | MetricsMeasurementEngineeringAlignment | ArchitectureDocumentationCommunication |