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 ARID (Active Reviews for Intermediate Designs) |  Architecture arc42 |  Agile Example Mapping |
|---|---|---|---|---|
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. | 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. | 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 2–4 h review as a planning range; preparation and evaluation additional | 1-2 Tage | 30-60 min |
Participantsdifferent | 3-6 | Designers, developers as users, and facilitation | 1-4 | 3-7 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Architecture Document, Context View, Runtime View, Deployment View | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureDocumentationCommunication | Behavior-Driven DevelopmentRequirementsExamplesRefinement |