View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Engineering Goal Question Metric | ![]() Architecture Views and Beyond | ![]() Architecture arc42 | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 90-180 min | 1-3 Tage | 1-2 Tage | 1-2 h |
Participantsdifferent | 3-6 | 1-4 | 1-4 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | GQM Table, Metric Profiles | Architecture Views, Cross-view Notes, Rationale | Architecture Document, Context View, Runtime View, Deployment View | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | MetricsMeasurementEngineeringAlignment | DocumentationStakeholdersArchitecture | ArchitectureDocumentationCommunication | AlignmentStakeholdersStrategyFacilitation |



