View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Mode and Effects AnalysisCompetency QuestionsSpecification by ExampleLinked Open Terms
| Criterion |  Operations Failure Mode and Effects Analysis |  Knowledge Modeling Competency Questions |  Agile Specification by Example |  Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
Purposedifferent | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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 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. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | 2-6 h | 2-4 h | 60-90 min pro Feature | Wochen bis Monate |
Participantsdifferent | 3-10 | 2-8 | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | FMEA Table, Risk Priority, Mitigation Actions | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Table, Acceptance Tests | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | RiskQualityOperationsRoot cause | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsExamplesBehavior-Driven Development | OntologyMethodologyAgileSemantic |