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 Architecture Decision Record |  Architecture Quality Attribute Workshop |  Architecture C4 Model |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 15-45 min | 2-4 h | 1-4 h | 60-90 min |
Participantsdifferent | 1-3 | 5-15 | 1-5 | 4-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Quality Scenarios, Priority List, Architecture Concerns | Context Diagram, Container Diagram, Component Diagram | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tags1 shared | ArchitectureRationaleDocumentationGovernance | RequirementsArchitectureWorkshop | ArchitectureCommunicationVisualization | RiskArchitectureWorkshopValidation |