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 Concept Mapping |  Decision Making Red Teaming |  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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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 | High | Low |
Timedifferent | 1-2 Tage | 1-2 h | 1-4 h | 15-45 min |
Participantsdifferent | 1-4 | 1-8 | 3-8 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Concept Map, Relationship Labels, Knowledge Gaps | Challenge Findings, Risk Register, Mitigation Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDocumentationCommunication | KnowledgeConceptsMappingSensemaking | RiskDecisionSensemaking | ArchitectureRationaleDocumentationGovernance |