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 |  Knowledge Modeling Competency Questions |  Knowledge Modeling Property Graph Schema Design |  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. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together. | 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 | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 2-4 h | 4-8 h initial, dann iterativ | 1-4 h |
Participantsdifferent | 1-4 | 2-8 | 1-6 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ArchitectureDocumentationCommunication | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphModelingSemantic | ArchitectureCommunicationVisualization |