Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Property Graph Schema Design Request for Comments Architecture Decision Record Competency Questions

Criterion	Knowledge Modeling Property Graph Schema Design	Architecture Request for Comments	Architecture Architecture Decision Record	Knowledge Modeling Competency Questions
Purposedifferent	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.	An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.	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.	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.
Complexitydifferent	Medium	Medium	Low	Medium
Timedifferent	4-8 h initial, dann iterativ	1-3 Wochen vom Draft bis zur Entscheidung	15-45 min	2-4 h
Participantsdifferent	1-6	3-20 Reviewer	1-3	2-8
Formatdifferent	Workshop + async	Async	Async	Workshop + async
Outputdifferent	Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	ADR File, Decision Log, Rationale	Competency Question Set, Required Concepts, Test Queries, Coverage Matrix
Tagsno overlap	Knowledge graphModelingSemantic	ArchitectureDecisionAsyncGovernance	ArchitectureRationaleDocumentationGovernance	OntologyKnowledge graphScopeRequirementsSemantic

Add more methods