View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)Competency QuestionsLinked Open TermsAcceptance Criteria Workshop
| Criterion | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() Knowledge Modeling Competency Questions | ![]() Knowledge Modeling Linked Open Terms | ![]() Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. | 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 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 | Preparation, scenario analysis, and findings review; effort depends on scope | 2-4 h | Wochen bis Monate | 20-40 min pro Story |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-8 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | OntologyKnowledge graphScopeRequirementsSemantic | OntologyMethodologyAgileSemantic | AgileRequirementsRefinementBehavior-Driven Development |



