Overview

The abridged version of the development process specifies the steps necessary to create ontologies based on an agile, iterative process. The process begins with collecting epics from working groups, users, and domain experts to guide development.

...

• Sufficient individuals are available to work on ontology, with the following mandatory roles filled:

  • Domain experts to provide business cases and industry terminology

  • Business architect to develop the use cases and scenarios

  • Ontologists to develop the ontology

• Adequate definition of the Epic.

Creating an Epic

Alternative Terms

...

Is there a better term than EPIC?

• Create a capability

• Fundamental notions that are not being made

  • Agile: enable capabilities (not create capabilities)

  • Mapping the ontology development process to Jira and agile processes

• Do we need to better define EPIC?

...

We making an early commitment Jira?

• We made a choice to use Jira early on

• Manage the process

...

GitHub only used for content management

...

Usage Scenarios that enable answering competency questions (capability)

• The ontology enables the capability

• Beginning of the development process

• Embed parts of the process to meet the requirements

...

IOF can’t specify the capabilities the ontology can support?

• Must solve some business problem

• We provide the foundation for the solution

System Engineering Experts

...

An Epic is a significant development initiative that may span multiple releases and working groups. The Epic aligns with a high-level need by the industry to provide some capability in the standard. It must be aligned with business objectives and provide someone with value or solve problems requiring an ontological approach.

...

• The high-level topics and concerns the working groups need to address.

• Known dependencies on this Epic by other groups and if other Epics are blocked.

• An estimate of the complexity of the Epic.

• The necessary stakeholders in each domain to create use cases.

Examples

• Title: Supply chain resistance. The manufacturing supply chain needs to reduce the dependency on a single source of parts because of areas of vulnerability that prevent a surge in production or incur delays due to a lack of available capabilities. To address this problem, standards are needed to provide capability-based agile manufacturing support for dynamic just-in-time sourcing, planning, scheduling, and executing from the supply chain, engineering, and manufacturing processes across the industrial base.

• Title: Lifecycle product data. The current manufacturing information systems cannot capture the lifecycle of products and all their parts to support the archival and retrieval of products across their complex mereological structure. To address this, the industry requires information across the entire product and lifecycle, including design, manufacturing, maintenance, and end-of-life, to understand how something was made and the provenance of the parts.

...