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 Views and Beyond |  Knowledge Modeling Concept Mapping |  Architecture C4 Model |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | 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 | Medium | Low | Low |
Timedifferent | 1-3 Tage | 1-2 h | 1-4 h | 15-45 min |
Participantsdifferent | 1-4 | 1-8 | 1-5 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Concept Map, Relationship Labels, Knowledge Gaps | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale |
Tagsno overlap | DocumentationStakeholdersArchitecture | KnowledgeConceptsMappingSensemaking | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance |