View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Knowledge Modeling Ontology Design Patterns | ![]() Architecture Views and Beyond | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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. | 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 | 30 min Setup, dann laufend | 1-3 h pro Pattern | 1-3 Tage | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-6 | 1-4 | 1-3 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | OntologyPatternsReuseSemanticModeling | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance |



