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 arc42 |  Product Discovery Outcome-Driven Innovation |  Architecture Views and Beyond |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. | 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. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 1-2 Tage | Mehrere Wochen | 1-3 Tage | 1-4 h |
Participantsdifferent | 1-4 | 2-6 researchers plus sample | 1-4 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Architecture Views, Cross-view Notes, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ArchitectureDocumentationCommunication | OutcomesInnovationResearchQuantitative | DocumentationStakeholdersArchitecture | ArchitectureCommunicationVisualization |