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 ExampleLinked Open TermsExample Mapping
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Specification by Example |  Knowledge Modeling Linked Open Terms |  Agile Example Mapping |
|---|---|---|---|---|
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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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 | High | Medium | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min pro Feature | Wochen bis Monate | 30-60 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-6 | 2-8 | 3-7 |
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 | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | AgileRequirementsExamplesBehavior-Driven Development | OntologyMethodologyAgileSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement |