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 |  Architecture Architecture Decision Record |  Decision Making RAPID |  Architecture Request for Comments |
|---|---|---|---|---|
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. | 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. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 60-90 min pro Feature | 15-45 min | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 3-6 | 1-3 | 3-12 | 3-20 Reviewer |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Example Table, Acceptance Tests | ADR File, Decision Log, Rationale | RAPID Role Map, Recommendation, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance | DecisionRolesGovernance | ArchitectureDecisionAsyncGovernance |