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)Example Mapping Architecture Decision Record arc42

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

Add more methods