View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Competency QuestionsDecision Rights MappingArchitecture Decision RecordRequest for Comments
| Criterion |  Knowledge Modeling Competency Questions |  Decision Making Decision Rights Mapping |  Architecture Architecture Decision Record |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | 90-180 min | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-8 | 4-12 | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Decision Rights Matrix, Agreement | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | DecisionGovernanceAlignmentResponsibility | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |