Welcome to the Unified Architecture Framework (UAF) Wiki. This wiki provides information on the background of UAF, how to use UAF, and upcoming events and announcements related to the UAF.
UAF evolved from the Unified Profile for Department of Defense Architecture Framework (DoDAF) and Ministry of Defence Architecture Framework (MODAF) (UPDM), version 2.1. UPDM is not a new architectural framework- it merges pre-existing concepts from DoDAF and MODAF into a combined metamodel. UPDM has been adopted by a wide variety of organizations, extending beyond the military and into federal and industry applications. Because of this, there was an increasing demand for UPDM to become more industrialized and to support other frameworks other than just DoDAF and MODAF. This led to the creation of UAF.
The Unified Architecture Framework (UAF) is an architecture framework that provides visualization for specific stakeholders concerns through engineering domains organized by various views. The views are artifacts for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular or graphical means. UAFP enables the extraction of specified and custom views from an integrated architecture description (AD) in support of a model-based systems engineering (MBSE) approach. The views describe a system from a set of stakeholders' concerns such as security or information. The UAFP specification supports the Department of Defense Architecture Framework (DoDAF) 2.02, the Ministry of Defence Architecture Framework (MODAF), Security Views from Canada's Department of National Defense Architecture Framework (DNDAF) and the North Atlantic Treaty Organization (NATO) Architecture Framework (NAF) v 4. The core concepts in the UAF domain metamodel used to specify the UAFP are based upon the DoDAF 2.0.2 Domain Metamodel (DM2) and the MODAF ontological data exchange mechanism (MODEM, which is intended to provide the basis for the next version of NAF). The intent is to provide a standard representation for AD support for Industry, Government, and Defense Organizations. ADs as part of their Systems Engineering (SE) technical processes. UAFP supports the capability to:
The UAF Specification consists of four parts:
The UAF DMM and Profile are both normative components of the specification, while the traceability and example components are non-normative. UAF can be implemented directly using the UAF DMM, or by using UAFP (for tool vendors that support SysML/UML), or by some other proprietary implementation. Building from one of these implementations, we can create either NAF v4, UAF, or DoDAF 2.0 views.
The UAF grid shows how UAF is organized into different view specifications.
Each row in this grid represents a different domain, and each column represents a different “model kind”. The “domains” can be thought of as the different parts of the underlying information model, while the “model kinds” can be thought of as different standard ways of representing that information. Each cell in the grid is a different view specification or “viewpoint”. UAF defines a metamodel for each viewpoint- the main concepts and relationships you need to build this specific viewpoint. Although the grid is a flat view, think of the information behind each viewpoint in the grid as interrelated. However, this grid view doesn’t really illustrate how the information is interrelated.
A better representation of how the information of each domain is interrelated can be seen below.
In this diagram, the horizontal boxes are stacked to represent how the domain on top ties to the domain below it. For example, the Strategic view is tied to the Operational view, which is tied to the Resources view, etc. The vertical boxes indicate that that domain spans across all the domains horizontally stacked within the vertical box’s height. For example, the Security view spans across the Operational view and the Personnel and Resources views because the Operational views help define the problem in the Security domain, whereas the Personnel and Resources views help define the solution for that domain. However, this diagram is a very high-level representation. If you would like to see more detail on which elements tie each of the domains together, a simplified version of the UAF information model can be seen below.
The “Behavior” column shows a thread between Capabilities (Strategic domain), the Operational Activities (Operational domain) which break down these Capabilities into logical domains, and the Functions (Resource domain) which maps these Operational Activities onto how they might be realized in the physical domain. The “Agent” column shows who exhibits the Capabilities or performs those behaviors.
The UAF model kinds can be mapped to some SysML diagrams, as seen in the table below.
|Model Kind||SysML Diagram|
|Taxonomy (Tx)||Block Definition Diagram (bdd)|
|Structure (Sr)||Block Definition Diagram (bdd) & Internal Block Diagram (ibd)|
|Connectivity (Cn)||Internal Block Diagram (ibd)|
|Processes (Pr)||Activity Diagram (act)|
|States (St)||State Machine Diagram (stm)|
|Interaction Scenarios (Is)||Sequence Diagram (sd)|
|Information (If)||Block Definition Diagram (bdd)|
|Parameters (Pm)||Block Definition Diagram (bdd)|
|Constrains (Ct)||Block Definition Diagram (bdd) & Parametric Diagram (par)|
|Summary & Overview (Sm-Ov)||Block Definition Diagram (bdd)|
|Requirements (Req)||Requirement Diagram (req)|
The Taxonomy (Tx), Connectivity (Cn), and Parameters (Pm) model kinds can also be thought of as tables. The rest of the model kinds do not have analogous SysML diagrams- however, the Roadmap (Rm) model kind can be thought of as a Gantt chart, the Traceability (Tr) model kind can be thought of as a matrix, and the Dictionary (Dc) model kind can be thought of as a table.
This section will give a brief summary of each of the domains and model kinds shown in the UAF Grid.
UAF Guide describes a workflow for creating Enterprise Architecture (EA) views in accordance with the Unified Architecture Framework (UAF) Modeling Language (UAFML). This EA Guide for UAF is published as a non-normative component of the UAF specification. It is intended to be used in conjunction with the UAF Sample Problem that defines architecture views for a Search and Rescue Mission. The nine steps of the workflow are laid out in alignment with the stakeholder viewpoints in UAF for producing the requisite architecture views in each of those viewpoints. This underlying architecture description method is an implementation of the Architecture Elaboration process in ISO 42020 and can be used in conjunction with processes for the Conceptualization and Evaluation of an architecture specified in ISO 42020. It can also be used as the basis for an EA modeling methodology, architecture development planning, and modeling project organization and planning. The Guide covers architecting of the enterprise as well as architecting (at a high level) of major entities within the enterprise.
|Event Name||Event Date||Event Location|
|UAF Summit: ACTIONABLE ARCHITECTURE IN THE 21ST CENTURY - HYBRID event||Mar 23, 2022||Reston, VA USA|
|ACTIONABLE ARCHITECTURE IN THE 21ST CENTURY||Mar 26, 2020||Reston, VA USA|
|OMG Technical Meeting||Mar 23-27, 2020||Reston, VA USA|
|OMG Technical Meeting||Dec 9-13, 2019||Long Beach, CA USA|
|INCOSE International Workshop 2020||Jan 25-28, 2020||Torrance, CA USA|
|OMG Technical Meeting||Mar 23-27, 2020||Reston, VA USA|
|INCOSE International Symposium 2020||Jul 18-23, 2020||Cape Town, South Africa|
Numerous presentations were delivered promoting the use of UAF in multiple different events worldwide:
OMG organised Information days for UAF: