View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Quality Attribute Workshop |  Product Discovery Context Canvas |  Architecture arc42 |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2-4 h | 45-90 min | 1-2 Tage | 15-45 min |
Participantsdifferent | 5-15 | 3-10 | 1-4 | 1-3 |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Context canvas, Open questions, Shared context notes | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | RequirementsArchitectureWorkshop | ContextFramingRequirementsCanvas | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |