DoDAF vs UAF: what's the difference (and which do you model in)?

What DoDAF is

DoDAF—the Department of Defense Architecture Framework—is the US DoD's standard set of viewpoints and views that defense architectures are expected to produce. Current version is DoDAF 2.02, organized into eight viewpoints:

• All (AV) — overview and summary information
• Capability (CV) — capability requirements and evolution
• Data and Information (DIV) — data standards and relationships
• Operational (OV) — operational activities and exchanges
• Project (PV) — programs and relationships to capabilities
• Services (SvcV) — service resources and behavior
• Standards (StdV) — applicable standards and guidance
• Systems (SV) — systems and interconnections

DoDAF is the framework your deliverables are judged against on a DoD program. It defines the shape of the outputs—not the tool or modeling language used to produce them.

What UAF is

UAF—the Unified Architecture Framework—is an OMG standard built on UML/SysML. Its core purpose is to unify the three major defense architecture frameworks — DoDAF (US), MODAF (UK), and NAF (NATO) — into a single modeling profile. Rather than learning three overlapping frameworks and maintaining separate models for each, you build the architecture once in UAF and generate conformant views for whichever framework your program requires.

UAF is the successor to UPDM (the Unified Profile for DoDAF/MODAF), which was an earlier attempt at the same unification. UPDM is the profile UAF replaces; DoDAF, MODAF, and NAF are the delivery frameworks that UAF supports and continues to target. UAF did not replace DoDAF—DoDAF remains the DoD standard. UAF replaced the older UPDM profile used to model against it.

How they relate in practice

The clean mental model: UAF is how you model; DoDAF is one of the things you produce. This is not a pick-one decision. On a DoD program the two work as a stack:

• You build the architecture in the UAF modeling environment inside Cameo / CATIA Magic.
• You produce DoDAF 2.0-conformant views—OVs, SVs, CVs, and so on—from that model using the DoDAF framework environment and reporting.
• The same underlying model can also produce MODAF or NAF views if the program spans US, UK, or NATO partners.

Thinking of them as “DoDAF vs UAF” misframes the relationship. The question is not which framework to adopt; it's understanding that UAF is the modeling layer and DoDAF is a delivery target sitting on top of it.

In the tool: framework environments

In Cameo / CATIA Magic, framework support works through selectable framework environments layered over the shared UAF profile. Selecting the DoDAF 2.0 environment switches the GUI templates, diagram types, and reporting to match DoDAF's viewpoint structure. The underlying model stays in the shared UAF profile, so the same model can be presented through different framework lenses—and the environment can be changed by converting the model if the program's delivery target shifts.

The practical workflow is: model in the UAF environment, configure the DoDAF 2.0 framework environment for the views the program requires, and generate reports against DoDAF's prescribed view specifications. The tool handles the alignment between UAF model elements and DoDAF view definitions—you're not manually translating between two separate models.

NOTE Framework environment details and exact menu paths vary by release. Verify the workflow against your installed version before briefing a program team.

MSOSA: the DoD bundle name

In US DoD shops you'll frequently hear MSOSA—Magic Systems of Systems Architect. That's the product name for the CATIA Magic / Cameo bundle that pairs MBSE and systems-engineering modeling with the architecture-framework extensions (UAF plus DoDAF 2.0, MODAF, NAF), co-branded with Cameo Enterprise Architecture.

If your program runs “MSOSA,” you're in the Cameo family with the full framework tooling—UAF profile, DoDAF 2.0 environment, and the reporting stack— already present. The UAF-to-DoDAF workflow above applies directly.

What changed in 2026x

The 2026x release implements UAF 1.3 (OMG formal specification, published April 2026). Framework support is listed as: UAF, EA-BPMN, DoDAF, DoDAF 2.0, MODAF, NAF, and NAF 4.0. Two housekeeping changes worth knowing:

• UAF 1.2 is no longer supported in 2026x. Models on the 1.2 plugin need to migrate.
• The UAF Enterprise Architecture framework is renamed EA-BPMN, and the stereotype «DODAFProperties» is renamed «UAFProperties».
• Updated library versions ship alongside: UJTL 20250715 and DISR 20240606.

NOTE Version-specific details above apply to the 2026x release. Confirm exact framework support and library versions against your installation before planning a migration.

FAQ