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 Views and Beyond |  Agile Example Mapping |  Agile Acceptance Criteria Workshop |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 | 1-3 Tage | 30-60 min | 20-40 min pro Story | 1-2 Tage |
Participantsdifferent | 1-4 | 3-7 | 3-6 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | DocumentationStakeholdersArchitecture | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureDocumentationCommunication |