View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordExample MappingQuality Attribute WorkshopSpecification by Example
| Criterion |  Architecture Architecture Decision Record |  Agile Example Mapping |  Architecture Quality Attribute Workshop |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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 | Medium | Medium |
Timedifferent | 15-45 min | 30-60 min | 2-4 h | 60-90 min pro Feature |
Participantsdifferent | 1-3 | 3-7 | 5-15 | 3-6 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Example Map, Acceptance Criteria, Open Questions | Quality Scenarios, Priority List, Architecture Concerns | Example Table, Acceptance Tests |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RequirementsArchitectureWorkshop | AgileRequirementsExamplesBehavior-Driven Development |