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)Leverage Points Context Map Bounded Context Canvas

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Systems Thinking Leverage Points	Domain Modeling Context Map	Domain Modeling Bounded Context Canvas
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.	Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.	When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.	When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.
Complexitydifferent	Medium	High	Medium	Medium
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	Half day	1-3 h	1-3 h
Participantsdifferent	Designers, developers as users, and facilitation	3-12	2-8	3-8
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop + async
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Leverage Map, Action Strategy	Context Map, Integration Patterns, Boundary Notes	Context Canvas, Glossary, Integration Notes
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	Systems thinkingChangeStrategy	Domain-Driven DesignBoundariesStrategy	Domain-Driven DesignBoundariesModeling

Add more methods