NATO Architecture Framework

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

NATO Architecture Framework[edit]

The aim of the NATO Architecture Framework Version 4 (NAFv4) is to provide a standard for developing and describing architectures for both military and business use. It provides a standardized way to develop architecture artefacts, by defining the following:

  • Introduction – an overview of NAF, what it is and who uses it (Chapter 1)
  • Methodology – how to develop architectures and run an architecture project (Chapter 2)
  • Viewpoints – conventions for the construction, interpretation and use of architecture views for communicating the enterprise architecture to different stakeholders (Chapter 3)
  • Meta-Models – the application of commercial meta-models identified as compliant with NATO policy (Chapter 4)
  • Glossary, References and Bibliography (Chapter 5)

The NATO Architecture Framework v4 (NAFv4), issued by the Architecture Capability Team (ACaT) of the NATO Consultation, Command and Control Agency (C3B) in January 2018, provides guidance on describing both enterprise architectures and systems architectures.

The objectives of the framework are to:

Methodology[edit]

NAFv4 Chapter 2 provides a methodology which includes how to set up an architecting environment, govern, manage, define and evaluate architectures. The methodology has been developed from accepted best practice and standards, detailing the following:

  • Terms and concept for architecting.[1]
  • A foundation for architecture activities[2]
  • Architecture principles[3]
  • Architecture activities at enterprise and project levels [4]
  • Architecture repositories and libraries enabling reuse and improved interoperability between communities, and to formalize architecture-based references.[4]

Viewpoints (Grid representation)[edit]

NAFv4 Chapter 3 defines Viewpoints, Views and Architecture Descriptions. It details a two-dimensional classification scheme for the standardized architecture viewpoints, this serves as the baseline for any NAF-Compliant architecture effort. To aid architects, these viewpoints are organized into a logical and consistent manner and presented as a “grid”. This ‘grid’ structure, represents the various ‘subjects of concern’ (rows) and ‘aspects of concern’ (columns), as shown below:


Behaviour
Taxonomy Structure Connectivity Processes States Sequences Information Constraints Roadmap
Concepts C1

Capability Taxonomy

NAV-2, NCV-2

C2

Enterprise Vision

NCV-1

C3

Capability

Dependencies

NCV-4

C4

Standard Processes

NCV-6

C5

Effects

NOV-6b

C7

Performance Parameters

NCV-1

C8

Planning Assumptions

Cr

Capability Roadmap

NCV-3

C1-S1 (NSOV-3)
ServiceSpecifications S1

Service Taxonomy

NAV-2, NSOV-1

S3

Service

Interfaces

NSOV-2

S4

Service Functions

NSOV-3

S5

Service States

NSOV-4b

S6

Service Interactions

NSOV-4c

S7

Service I/F Parameters

NSOV-2

S8

Service Policy

NSOV-4a

Sr

Service Roadmap

LogicalSpecifications L1


Node Types

NAV-2

L2

Logical Scenario

NOV-2

L2-L3 (NOV-1)
L3

Node

Interactions

NOV-2, NOV-3

L4

Logical Activities

NOV-5

L5

Logical States

NOV-6b

L6

Logical Sequence

NOV-6c

L7

Logical Data Model

NSV-11a

L8

Logical Constraints

NOV-6a

Lr

Lines of Development

NPV-2

L4-P4 (NSV-5)
PhysicalResourceSpecifications P1

Resource Types

NAV-2, NSV-2a,7,9,12

P2

Resource Structure

NOV-4,NSV-1

P3

Resource

Connectivity

NSV-2, NSV-6

P4

Resource Functions

NSV-4

P5

Resource States

NSV-10b

P6

Resource Sequence

NSV-10c

P7

Physical Data Model

NSV-11b

P8

Resource Constraints

NSV-10a

Pr

Configuration Management

NSV-8

ArchitectureManagement A1

Meta-Data Definitions

NAV-3

A2

Architecture Products

A3

Architecture

Correspondence

ISO42010

A4

Methodology Used

NAF Ch2

A5

Architecture Status

NAV-1

A6

Architecture Versions

NAV-1

A7

Architecture Meta-Data

NAV-1/3

A8

Standards

NTV-1/2

Ar

Architecture Roadmap

The selection of Viewpoints must be tailored to the specific architecture effort; i.e. suitable Viewpoints need to be identified in the grid, should additional Viewpoints be required they must defined.

A View is specified by a Viewpoint, this prescribes the concepts, models, analysis techniques and visualizations that are provided by the View.

The Architecture Description typically addresses a set of related concerns and is tailored for specific stakeholders.

  • A View specifies what you see
  • A Viewpoint is where you are looking from, focusing on particular subjects or stakeholder concerns

Note: the NAFv4 specifies how views of NAF version 3 (NAFv3) can be reused, i.e. each cell of the “grid” refers to the NAFv3 views and the NAFv4 methodology explains how forward and backward compatibility can be ensured.

Adoption of Industry Meta-Models[edit]

Chapter 4 of the NATO Architecture Framework identifies the commercial meta-models which can be used to creation viewpoints described in chapter 3:

Glossary, References and Bibliography[edit]

Chapter 5 of the NATO Architecture Framework define major definitions and references in line with the major standards and reference documents used in Architecture activities.

Web access to download NAFv4[edit]

Official site to download the latest version of NAF is available (here) or on the (NATO Portal).

Search for “Architecture” and select the “NATO Architecture Framework, Version 4” entry.

See also[edit]

References[edit]