An Ontological Implementation of UAF

A six-part series rendering the Unified Architecture Framework (UAF) Domain Metamodel (DMM) as an ontology and cross-checking it against the UAFML profile.

The OMG Unified Architecture Framework (UAF) unifies the defense architecture frameworks (DoDAF, MODAF, NAF, DNDAF) into a single grid of viewpoints and aspects. It is used to plan by capability, trace strategy down to fielded resources, and reason about system-of-systems architectures.

In this series we rendered the UAF Domain Metamodel (DMM) as a faithful, platform-neutral ontology on OML Code, and used it to cross-check every element and relationship against the normative UAF Modeling Language (UAFML) profile. Each part reads UAF in light of its own stated objectives, and shows what an ontological implementation adds: automated reasoning that checks the specification, queries that compute views, and AI grounded in a formal model.

Key terms

  • UAF: the Unified Architecture Framework, the OMG standard for enterprise and system-of-systems architecture, organized as a grid of viewpoints and aspects.
  • UAF DMM: the Domain Metamodel, UAF's platform-independent definition of its concepts and relationships. This is the part we render as an ontology.
  • UAFML: the UAF Modeling Language, the SysML profile that realizes the DMM in SysML tools.
  • OML: the Ontological Modeling Language, a description-logic modeling language designed for engineering, and the language of OML Code.

The series

Part 1

UAF Was Built for This

Part 1 of a series. Rendering a specification as an ontology, with AI reading it and automated reasoning checking it, is not just a way to implement it; it is a way to understand it. We put the OMG Unified Architecture Framework under that neurosymbolic len...

Part 2

How Far Platform Independence Reaches

Part 2 of a series reading UAF in light of its own objectives. UAF sets out to be platform-independent at the DMM level. Rendering it as an ontology shows exactly where that independence holds firm, in its relational core, and where, by deliberate design, i...

Part 3

Views Without Queries

Part 3 of a series holding UAF to its own objectives. UAF exists to support the analysis of complex systems, and its unit of analysis is the view. Yet a UAF view is specified as a static list of element types and a schema diagram, never as a query. UAF desc...

Part 4

Keeping a Large Specification Consistent

Part 4 of a series reading UAF in light of its own objectives. Any specification told across prose, diagrams, and a profile accumulates small inconsistencies; keeping them aligned is one of the hardest parts of maintaining a standard. A formal rendering cat...

Part 5

Keeping the Profile and the Metamodel Aligned

Part 5 of a series reading UAF in light of its own objectives. UAFML is the SysML profile that realizes the platform-neutral DMM. Maintaining two large artifacts in parallel is hard, and a formal rendering shows a few small places where they have drifted, o...

Part 6

What It Adds Up To

The closing part of a series reading UAF in light of its own objectives. Step back and the picture is encouraging: a genuinely valuable, relational domain model whose durable core an ontology can sharpen, align, and complete. Read this way, an ontological i...

Work with the UAF ontology

Want to reason over your own UAF architecture, or build a methodology on top of the DMM? Explore OML Code, or talk to us.