A 5-minute Introduction to the UAF (Unified Architecture Framework)

Hello, everyone!

We’re thrilled to share some big news: in the beginning of 2024, we’ll be releasing the software update for our MBSE tool – Astah System Safety – along with a complimentary plug-in for the Unified Architecture Framework (UAF).
If you’re new to UAF or seeking to broaden your understanding, you’re in the right place. 🙂

What is UAF?

The Unified Architecture Framework (UAF) is a standard representation published by Object Management Group (OMG) for describing the architecture of enterprise systems using a Model Based Systems Engineering (MBSE) approach. Here, “Enterprise Systems” refer to expansive organizational structures, including large corporations and government entities, and systems where multiple systems are integrated.

UAF was actually evolved from the Unified Profile for Department of Defense Architecture Framework (DoDAF)/British Ministry of Defence Architecture Framework (MODAF) (UPDM), version 2.1.
UAF extends the scope of UPDM and generalizes it to make it applicable to commercial.

What is UAF used for?

To optimize and transform such enterprise systems, it is necessary to resolve many issues from various perspectives in a coherent manner. When considering such optimizations and transformations, we think about enterprise architecture, and UAF provides a template-like cohesive framework for describing this. There are various challenges when constructing enterprise architecture, and UAF primarily aims to solve the following problems:

The difficulty of aligning disparate stakeholder perspectives
The challenge of coherently describing diverse concepts of varying abstraction levels

With the evolution of system development, these issues are not exclusive to enterprise systems; they are common to many types of systems development, where UAF can be applied effectively.

Exploring the “UAF Grid”

Now let’s dive into UAF’s offerings. UAF provides the following two main components:

Definition of Viewpoints
Definition of a Domain Metamodel

A “Viewpoint” in UAF refers to the perspective from which architecture is described, based on the concerns and issues of stakeholders. UAF defines 15 viewpoints, which generally encompass the concerns and issues of stakeholders in enterprise systems. The viewpoints provided by UAF are summarized in the following “UAF Grid”.

(Figure 7:1- UAF Grid from Unified Architecture Framework (UAF) Domain Metamodel Version 1.2)

In this grid, the rows represent Viewpoints, and the columns represent how those Viewpoints are modeled, which UAF refers to as “Aspects.”

The “Domain Metamodel” is where the concepts for describing enterprise architecture are defined. I believe that there are many instances where a system must be described coherently, from abstract strategies to concrete system solutions, and UAF provides best practices for this.

Now, let’s take a detailed look at a slice of this grid, specifically the initial part of “Resource View” definition as defined in the Unified Architecture Framework (UAF) Domain Metamodel Version 1.2 specification – page.66.

8.1.7 View Specification: Resource

Stakeholders:
System Engineers, Resource Owners, Implementers, Solution Providers, IT Architects.

Concerns:
Defining the solution architecture to implement operational requirements.

Definition:
The solution architecture captures organizational, software, artifacts, capability configurations, and natural resources to fulfill operational requirements. The more detailed design of resources is typically described using SysML or UML.

As mentioned before, viewpoints are defined based on stakeholders’ concerns, which are showcased first. Here, the Resource Viewpoint represents the interests of more technically-oriented stakeholders, like system engineers.
Also, note that the concern is a ‘definition of a solution architecture,’ which indicates that it focuses on revealing the solution architecture within the broader context of enterprise architecture. The definition lists potential resources and aims to fulfill operational requirements via the proposed solution architecture. The concluding remark clarifies that UAF does not extend to the granular design of individual resources.

Upcoming Articles

Thus, UAF provides definitions of various viewpoints to sufficiently describe the concerns and issues related to enterprise systems. Additionally, it offers a domain metamodel to manage the interests between different stakeholders and ensure consistency between concepts of varying abstraction.

In the next article, I will explain the domain metamodel in more detail, and thereafter, introduce each viewpoint along with the associated domain metamodel.
We also plan to write about tips and effective ways to use UAF that aren’t evident from the specification alone.

Stay tuned for more exciting content!

Introducing Astah System Safety

Circling back to our upcoming release, Astah System Safety is a modeling tool for safety-critical systems to support system architecture modeling, system safety assessment and analysis by incorporating the following modeling languages and techniques in one tool: SysML, STAMP/STPA, GSN/D-Case and ASAM SCDL. A free UAF plug-in we release in next month will be compatible with this Astah System Safety product. If you’re interested, a 40-day free trial is available! 🙂

Download a 40-day trial for Astah System Safety

Download UAF Plug-in

UAF Plug-in was released on March 12th, 2024. This complimentary plug-in works for both Astah SysML and Astah System Safety. Feel free to give it a try!