EKGF Use Case Tree Method
The EKGF Use Case Tree Method is a business-owned method for turning strategic enterprise knowledge graph use cases into reusable, governed, continuously tested semantic components.
The method centers on the Use Case Tree: a long-term business capability, requirements, scope, and dependency model that breaks strategic use cases into smaller use cases that can be delivered incrementally and reused.
Buyer question
“Can WWKG support a Use Case Tree operating model, where business capabilities, stories, personas, outcomes, concepts, data products, ontologies, tests, and dependencies are governed as part of the knowledge graph itself?”
WWKG fit
| Assessment area | WWKG fit | Status |
|---|---|---|
| Use Case Tree artifact | WWKG can store use cases, hierarchy, dependency, ownership, and scope metadata as RDF in governed workspaces with stable IRIs and named graphs. | Native fit |
| Stories, personas, outcomes, and concepts | WWKG’s Composable Business app treats EKGF use cases, stories, personas, outcomes, concepts, workflows, data products, and ontologies as first-class workspace resources. | Native fit |
| Executable semantic components | The Story Service, Named Statement Storage, Named Statement Execution, query services, and conformance scenarios make use cases executable semantic components. | Native fit |
| Governance and lifecycle | Branches, merge gates, signed commits, provenance, and configurable branch lifecycle mapping align closely with Use Case Tree governance from planning through production. | Native fit |
| Reuse and composition | Use-case graphs, shared IRIs, isPartOf ownership, usedIn reuse relationships, catalogs, and workspace metadata support discovery and composition of reusable capabilities. | Native fit |
| Continuous testing and quality | SHACL validation, branch gates, validation reports, and story-conformance scenarios support testable business requirements and production quality checks. | Native fit |
| Method implementation in product | Composable Business is WWKG’s native application surface for planning, authoring, governing, testing, and operating Use Case Tree content. | Native fit |
What WWKG can say
WWKG is a strong architectural fit for the Use Case Tree Method because the method expects business capability, requirements, semantic context, dependencies, and tests to become part of the enterprise knowledge graph instead of living only in slide decks or issue trackers.
In a WWKG implementation, a Use Case Tree can become graph data:
- Use cases can be identified by IRIs and organized into governed hierarchy and reuse relationships.
- Composable Business can author and manage the Use Case Tree as a product surface, not only as imported metadata.
- A use case can own the graph context for its stories, personas, outcomes, concepts, named statements, scenarios, data products, and ontology dependencies.
- Story Service, Named Statement Storage, and Named Statement Execution turn stories and named statements into executable semantic components.
- Branches can represent planning, development, staging, production, and archive states.
- Merge gates can enforce review and validation before a use case or story reaches a production branch.
- Commit provenance can show how the use case evolved and who approved the relevant changes.
- Query and API surfaces can expose use-case-scoped capabilities to people, applications, and AI agents without requiring them to write raw SPARQL.
Assessment boundary
The Use Case Tree Method is not only a data model. It is also a business, product, and delivery discipline. WWKG provides native product support through Composable Business, the Story Service, NSS/NSE, workspace versioning, validation, provenance, and execution services.
Buyers still need product owners, facilitation, prioritization, governance meetings, change management, and adoption discipline. WWKG’s claim is that the Use Case Tree itself can be a native, governed, queryable, testable, and executable part of the workspace, not a separate planning artifact.