View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Specification by ExampleCompetency QuestionsAcceptance Criteria Workshop
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Specification by Example |  Knowledge Modeling Competency Questions |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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 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. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min pro Feature | 2-4 h | 20-40 min pro Story |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-6 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Example Table, Acceptance Tests | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | AgileRequirementsExamplesBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsRefinementBehavior-Driven Development |