NAFv4 in Enterprise Architect: NATO Architecture Framework Guide

The NATO Architecture Framework version 4 (NAFv4) is a viewpoint-based framework issued by the NATO C3 Board's Architecture Capability Team in January 2018. Its methodology cites ISO/IEC/IEEE 42010 for its terms and concepts, and its meta-model is based on ArchiMate and the OMG Unified Architecture Framework (UAF) Domain Meta-Model. This is a reference guide for architects working on NATO and allied defense programs in Sparx EA.

A defense architect's job on a NAFv4 program is to give the customer architecture views that address their concerns and to keep those views consistent with each other as the program changes. Much of the effort goes into mechanics: creating elements, keeping correspondences between views current, and checking the model against the framework's conventions. In AI-augmented work the architect decides which concerns the architecture must address and what each view must show, and AI builds and maintains the views in the model. The skill this asks for is knowing the framework and the customer's requirements well enough to say what the architecture must contain, and to review what comes back. The rest of this article is the reference for that.

What NAFv4 is, and where it fits

NAF began as NATO's adaptation of the UK MODAF, which was itself developed from the US DoDAF. The UK government has withdrawn MODAF and states that it has been replaced by NAF v4. NAFv4 is a substantial redesign of earlier NAF releases rather than an incremental update, and it presents its viewpoints as a grid.

ISO/IEC/IEEE 42010 supplies the vocabulary for describing and organizing architecture: Architecture Description, Viewpoint, View, and Correspondence. An Architecture Description holds a set of Views, each produced according to a Viewpoint. A Viewpoint specifies the concerns being addressed, the stakeholders who hold them, and the kinds of models used to address them. Correspondences define how elements relate to one another across different views.

The NAFv4 viewpoint grid

NAFv4 arranges its viewpoints in a grid. Rows are subjects of concern and columns are aspects of concern, and each cell is named by its row letter and column number. The first column is taxonomy, so C1 is a capability taxonomy, S1 a service taxonomy and P1 a resource taxonomy. The first three rows below correspond to viewpoints of NAF v3, which helps teams moving from older programs.

The NAFv4 viewpoint grid

Row	What it addresses	Closest NAF v3 equivalent
Concepts (C)	Capabilities and strategic intent.	Capability viewpoint
Service (S)	The services provided and consumed.	Service-oriented viewpoint
Logical (L)	The logical architecture: activities, performers and flows, independent of how they are realized.	Operational viewpoint
Physical (P)	The physical resources, systems, software, hardware, facilities and personnel that realize the logical architecture.	No single equivalent

The grid has further cells beyond these four rows. Use the NATO NAFv4 documentation for the full grid and the definition of each cell, because the exact set of views a program produces is set by the customer's requirements, not by this guide.

NAFv4 in Sparx EA

Sparx EA supports NAFv4 through MDG extensions rather than the base installation. Sparx Systems' European partner site describes NAFv4 MDG extensions developed by the German and Swiss armed forces with BWI and CONET, offered with an example, documentation and presentation slides, and says they require Enterprise Architect 15.1 or later. Check the current version and edition coverage with Sparx Systems or your distributor. UPDM is a different technology: it is the profile for DoDAF and MODAF.

An MDG of this kind gives the architect framework-specific element types, relationship types and diagram templates, so a NAFv4 view starts with the right palette and conventions. Program-specific customization is then added on top, such as extra stereotypes, controlled value lists and validation rules. A common repository pattern is one package branch per viewpoint row plus a shared area for canonical, reusable definitions, so a capability or organization defined once is referenced from every view that uses it. That reuse is what keeps correspondences between views honest.

When NAFv4 is required

NAFv4 is the framework NATO publishes, and it is the one a program's architecture authority will name in the requirements. Two contexts are common.

NATO and allied programs. Programs procured through NATO bodies or national contributions to NATO capability targets are typically asked for architecture in NAFv4. Confirm the required views with the program's architecture authority.

UK MoD projects. The UK government states that MODAF has been withdrawn and replaced with NAF v4, so UK defense contractors and integrators working on MoD programs should expect NAFv4-based requirements. Confirm the required view set and framework version with the program.

NAFv4 vs DoDAF: choosing the right framework

For architects moving between NATO and US programs, the choice between NAFv4 and DoDAF is driven by customer requirements rather than preference. The differences that matter in practice:

NAFv4 vs DoDAF: choosing the right framework

Dimension	DoDAF 2.0	NAFv4
Structure	Eight viewpoints and 52 model types.	A grid of viewpoints, with rows for subjects of concern and columns for aspects of concern.
Meta-model	The DoDAF Meta-Model (DM2).	Based on ArchiMate and the OMG UAF Domain Meta-Model.
Origin and standards alignment	A US DoD framework.	A NATO framework whose methodology cites ISO/IEC/IEEE 42010.
Tooling in Sparx EA	UPDM profile.	NAFv4 MDG extensions.

Programs that span NATO and US customers can hold both in one Sparx EA repository, with shared definitions and an explicit mapping between the two sets of views.

Frequently asked questions

Work with Sparx Services

A NAFv4 program needs a configured Sparx EA environment and a model built to the framework, not a blank repository. We build and update the model, including the MDG configuration and the program package structure, and Configure the Solution covers the environment and multi-user access. For the wider view of how this fits into a defense architecture practice, see how we help architecture leaders turn requirements into a working environment.