View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Agile Example Mapping |  Architecture Software Architecture Canvas |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 60-90 min | 30-60 min | 1-2 h | 60-90 min pro Feature |
Participantsdifferent | 4-12 | 3-7 | 3-10 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Example Map, Acceptance Criteria, Open Questions | Architecture Canvas, Goals, Constraints, Quality Attributes | Example Table, Acceptance Tests |
Tagsno overlap | RiskArchitectureWorkshopValidation | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CanvasArchitectureAlignmentWorkshop | AgileRequirementsExamplesBehavior-Driven Development |