View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:C4 ModelAcceptance Criteria WorkshopATAM (Architecture Tradeoff Analysis Method)Example Mapping
| Criterion |  Architecture C4 Model |  Agile Acceptance Criteria Workshop |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 1-4 h | 20-40 min pro Story | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 1-5 | 3-6 | Evaluation team, architects, and relevant stakeholders | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Acceptance Criteria, Story Update | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ArchitectureCommunicationVisualization | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureQualityRiskTradeoffsStakeholders | Behavior-Driven DevelopmentRequirementsExamplesRefinement |