methodatlas
Compare

View methods side by side.

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

Criterion
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Purposedifferent
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.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 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.The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 h2–4 h review as a planning range; preparation and evaluation additional1-3 h5-15 min
Participantsdifferent
3-8Designers, developers as users, and facilitation2-81-5
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsContext Map, Integration Patterns, Boundary NotesVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step
Tagsno overlap
Domain-Driven DesignBoundariesModeling
ArchitectureEngineeringFeedbackValidationTasks
Domain-Driven DesignBoundariesStrategy
StartupValidationCompetition
Add more methods