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 Architecture Decision Record |  Product Discovery Context Canvas |  Knowledge Modeling Linked Open Terms |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 45-90 min | Wochen bis Monate | 1-2 Tage |
Participantsdifferent | 1-3 | 3-10 | 2-8 | 1-4 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Context canvas, Open questions, Shared context notes | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ContextFramingRequirementsCanvas | OntologyMethodologyAgileSemantic | ArchitectureDocumentationCommunication |