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 C4 Model |  UX Research Empathy Mapping |  Architecture Quality Attribute Workshop |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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. | When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. | 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. | 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 | Low | Medium | Low |
Timedifferent | 1-4 h | 30–60 min | 2-4 h | 60-90 min |
Participantsdifferent | 1-5 | 4-8 | 5-15 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Empathy Map, Assumptions List, Research Gaps | Quality Scenarios, Priority List, Architecture Concerns | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureCommunicationVisualization | SynthesisQualitativeWorkshop | RequirementsArchitectureWorkshop | RiskArchitectureWorkshopValidation |