Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:ARID (Active Reviews for Intermediate Designs)Architecture Decision Record Specification by Example Example Mapping

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Architecture Architecture Decision Record	Agile Specification by Example	Agile Example Mapping
Purposedifferent	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.	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.	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.	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	Low	Medium	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	15-45 min	60-90 min pro Feature	30-60 min
Participantsdifferent	Designers, developers as users, and facilitation	1-3	3-6	3-7
Formatdifferent	Workshop + async	Async	Workshop	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	ADR File, Decision Log, Rationale	Example Table, Acceptance Tests	Example Map, Acceptance Criteria, Open Questions
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	ArchitectureRationaleDocumentationGovernance	AgileRequirementsExamplesBehavior-Driven Development	Behavior-Driven DevelopmentRequirementsExamplesRefinement

Add more methods