methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of Linked Open Terms with its method-specific working model.
Knowledge Modeling
Linked Open Terms
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Purposedifferent
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.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.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
MediumHighMediumLow
Timedifferent
2-4 hPreparation, scenario analysis, and findings review; effort depends on scopeWochen bis Monate20-40 min pro Story
Participantsdifferent
2-8Architecture experts and stakeholders for scenarios and weighting2-83-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Competency Question Set, Required Concepts, Test Queries, Coverage MatrixDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesOntology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanAcceptance Criteria, Story Update
Tagsno overlap
OntologyKnowledge graphScopeRequirementsSemantic
ArchitectureChangeAnalysisComparisonQuality
OntologyMethodologyAgileSemantic
AgileRequirementsRefinementBehavior-Driven Development
Add more methods