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 Property Graph Schema Design | ![]() Knowledge Modeling Competency Questions | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | 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. | 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 | Low | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 4-8 h initial, dann iterativ | 2-4 h | 15-45 min |
Participantsdifferent | 1-4 | 1-6 | 2-8 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDocumentationCommunication | Knowledge graphModelingSemantic | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureRationaleDocumentationGovernance |



