DoDAF和MBSE

DoDAF is an architectural framework defined by the United States Department of Defense (DoD) for the defense and aerospace industries. The goal is to effectively combine operational objectives, combat capabilities, and various systems that support operations, and to effectively coordinate independent systems through the association of system architectures, so as to obtain capabilities and achieve goals.

Mission Protect. Connect. Perform. Vision To Deliver an Information Dominant Domain to Defeat our Nation's Adversaries Key Focus Areas Artificial Intelligence. Cloud. Communications. Cybersecurity. Data.

Mission Defend. Link. Execute. Vision: Deliver an information-led field to defend the nation Focus areas Artificial Intelligence, Cloud, Communications, Cybersecurity, Data

DoDAF can be used to organize and share large, complex distributed system architectures. DoDAF has 8 viewpoints, as shown in the figure below:

The 8 viewpoints of DoDAF are briefly described as follows:

DoDAF has multiple models for each viewpoint, the following is a list of models included in each viewpoint:

The models in DoDAF's 8 viewpoints are all interrelated, so that a holistic architecture can be comprehensively defined from multiple perspectives. This necessitates a transition from the traditional systems development process (document-based and code-centric) to MBSE (Model-Based Systems Engineering) when doing DoDAF engineering.

A guide to the process of setting up a DoDAF using iSpace

Due to the complexity of DoDAF, it is necessary to understand the relationship between these models and define what role and what model in the whole architecture establishment process, which requires a tool to guide the architecture process of DoDAF, and iSpace, an MBSE process support tool, can help users establish a DoDAF process guide and describe three process views:

The following is a guide to the DoDAF process established with iSpace

DoDAF's workflow

First, let's model the DoDAF workflow as follows:

Roles and responsibilities

Workpiece (deliverable)

What are the models for each viewpoint of DoDAF? The following is a model mapping of each viewpoint of the DoDAF created using the MBSE Process Guide tool iSpace.

DoDAF modeling using UPDM and UAF

Introduction to using UPDM and UAF

UPDM is a UML/SysML-based modeling guideline for DoDAF and MODAF. A UPDM group jointly formed by INCOSE and OMG to use UML /SysML creates a unified profile for DoDAF and MODAF (UPDM).

UAF (Unified Architecture Framework）。 Based on UPDM 3.0 and UML/SysML unified framework, we want to unify enterprise architecture standards for DoDAF, MODAF and NAF. The UAF objective is to develop a standardized and consistent IT top-level architecture in the military field based on DoDAF (United States Department of Defense Architecture Framework), MODAF (United Kingdom Ministry of Defense Architecture Framework) and NAF (North Atlantic Treaty Organization Architecture Framework). UAF defines an approach to representing the top-level architecture of IT that enables stakeholders to focus on specific areas of the organization while maintaining a holistic view.

The UAF view specification is organized using a two-dimensional grid, often referred to as the UAF Grid:

EA's support for UPDM

As a mainstream modeling tool that supports UML and SysML, EA naturally has support for UPDM. The modeling tools available in the EA for UPDM include three aspects:

Support for UAF in EA

In addition to supporting UPDM, the modeling tool EA further provides support for UAF, including three aspects:

An example of a DoDAF model built in an EA

The models of DoDAF from each viewpoint are strongly correlated, so that the overall architecture can be decomposed and tracked in an orderly manner. The modeling tool EA can build models of each viewpoint and associate each model to achieve overall modeling and understanding of the architecture.

Below are a few examples of the DoDAF models that have been built in the EA.

OV1: Concept diagram of high-level operations

OV-1 describes a task, task category, or scenario. It shows the main operational concepts and the operational areas of concern. Describes the interactions between the system of current interest and its environment, as well as with external systems. OV-1 provides a graphical description of the content of the architecture and ideas about the actors and operations. Its primary use is to aid human communication and is intended to be introduced to high-level decision-makers.

Intended uses of OV-1 include:

OV-6c - Event Tracing Description

OV-6c provides a chronological check of resource flows on a case-by-case basis. Each event trace diagram should have an accompanying description that defines a specific scenario or situation. The goal of an operational event/trajectory description is to track the action in a scene or sequence of key events, It can be described in a sequence diagram.

Uses for OV-6c include:

SvcV-1 - Service Context Description

SvcV-1 describes the structure of resources and how they interact so that operations in a logical architecture and services from service perspectives can be linked. It is important for architects to recognize that SvcV-1 is focused on resource flow and service delivery. Subservices can be identified in SvcV-1 as any level of decomposition (i.e., depth) that the architect deems appropriate. SvcV-1 can also identify the physical assets (such as platforms) where resources are deployed, and override the operational activities and locations that use those resources.

Uses of the SvcV-1 include:

SvcV-1 is used in two complementary ways: