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 | ![]() Business Strategy VRIO Framework | ![]() Architecture Architecture Decision Record | ![]() Architecture arc42 |
|---|---|---|---|---|
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. | The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions. | 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. | 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 | Low | Medium | Low | Low |
Timedifferent | 1-4 h | 90-180 min | 15-45 min | 1-2 Tage |
Participantsdifferent | 1-5 | 3-6 | 1-3 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | VRIO Table, Strategic Actions | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureCommunicationVisualization | StrategyDiagnosisBusiness modelCapability | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |



