scope:

Introduction

There are four parts to this specification, two are normative and two informative. The normative parts are:

1. The UAF Domain Metamodel (DMM) (this document) that provides the definition of concepts, relationships and viewpoints for the framework. The UAF DMM is the basis for any implementation of UAF including non- UML/SysML implementations.

2. The UAF Profile (UAFP) (see document dtc/19-06-15) is a UML/SysML implementation of the UAF DMM

The informative parts are:

3. The UAF Traceability, Annex A (see document dtc/19-06-17), which details the mappings between the UAF and the various frameworks and languages that contribute to the UAF.

4. The UAF Example Model, Annex B (see document dtc/19-06-18), which illustrates a practical usage of UAF.

UAF Background

UAF evolved from the Unified Profile for DoDAF and MODAF (UPDM), version 2.1. UAF extends the scope of UPDM and generalizes it to make it applicable to commercial as well as military architectures. The intent of UAF is to provide a standard representation for describing enterprise architectures using a Model Based Systems Engineering (MBSE) approach.

The core concepts in the UAF are based upon the DoDAF 2.0.2 Domain Metamodel (DM2) and the MODAF ontological data exchange mechanism (MODEM), Security Views from Canada's Department of National Defense Architecture Framework (DNDAF) and the North Atlantic Treaty Organization (NATO) Architecture Framework (NAF) v 4.

UAF models describe a system1 from a set of stakeholders' concerns such as security or information through a set of predefined viewpoints. Developed models can also reflect custom viewpoints or users can develop more formal extensions for new viewpoints.

The UAFP can be used to develop architectures compliant with:

• Department of Defense Architecture Framework (DoDAF) version 2.02

• Ministry of Defence Architecture Framework (MODAF) version 1.3

• North Atlantic Treaty Organization (NATO) Architecture Framework (NAF) version 3.1

• North Atlantic Treaty Organization (NATO) Architecture Framework (NAF) version 4

UAF v 1.1 supports the capability to:

• model architectures for a broad range of complex systems, which may include hardware, software, data, personnel, and facility elements,

• model consistent architectures for system-of-systems (SoS) down to lower levels of design and implementation,

• support the analysis, specification, design, and verification of complex systems; and

• improve the ability to exchange architecture information among related tools that are SysML based.

Intended Usage

The UAF enables the modeling of strategic capabilities, operational scenarios, services, resources, personnel, security, projects, standards, measures and requirements; which supports best practices through, separation of concerns and abstractions. In addition, the UAF enables the modeling of related architecture concepts such as:

• System of Systems (SoS),

• information exchanges consistent with the National Information Exchange Model (NIEM),

• DoD's doctrine, organization, training material, leadership & education, personnel, and facilities (DOTMLPF)

• UK Ministry of Defence Lines of Development (DLOD) elements,

• Human Computer Interfaces (HCI).

Further, The UAF conforms to terms defined in the ISO/IEC/IEEE 42010 standard for architecture description, where the terms: architecture, architecture description (AD), architecture framework, architecture view, architecture viewpoint, concern, environment, model kind, stakeholder [ISO/IEC/IEEE 42010:2011] form correspondence rules specified as constraints on UAF.

Related Documents

The specification includes a metatmodel and description as separate documents. Other appendices are also provided as separate documents. The table below provides a listing of these documents: