View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by ExampleArchitecture Decision RecordARID (Active Reviews for Intermediate Designs)
| Criterion |  Agile Specification by Example |  Architecture Architecture Decision Record |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 60-90 min pro Feature | 15-45 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 3-6 | 1-3 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | ADR File, Decision Log, Rationale | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
