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 |  Innovation TRIZ |  Architecture C4 Model |  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. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | High | Low | Low |
Timedifferent | 15-45 min | 1-4 h | 1-4 h | 1-2 Tage |
Participantsdifferent | 1-3 | 2-8 | 1-5 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Contradiction Statement, Inventive Principles, Solution Concepts | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | InnovationProblem solvingContradictionsCreativity | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication |