View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Knowledge Modeling IBIS |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. | 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 | Medium | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 1-3 h | 15-45 min | 1-2 Tage |
Participantsdifferent | 3-6 | 2-8 | 1-3 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Issue Map, Positions, Argument Notes | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RationaleKnowledgeDecision | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |