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)Linked Open TermsExample MappingSpecification by Example
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Linked Open Terms |  Agile Example Mapping |  Agile Specification by Example |
|---|---|---|---|---|
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. | 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. | 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 | High | Medium | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | Wochen bis Monate | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | 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 | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | OntologyMethodologyAgileSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |