View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Facilitation Consensus Workshop |  Architecture Risk Storming |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | 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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 1-3 h | 60-90 min | 1-2 h |
Participantsdifferent | 2-8 | 5-30 | 4-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Consensus Clusters, Theme Titles, Priority Areas | Annotated Diagram, Prioritized Risk List, Action Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | FacilitationConsensusWorkshopAlignment | RiskArchitectureWorkshopValidation | CanvasArchitectureAlignmentWorkshop |