The Department of War (DoW) is undergoing a significant transformation in how it acquires and develops software systems. Central to this evolution is the shift from traditional document-based processes to model-centric methodologies. In this context, researchers at Carnegie Mellon University Software Engineering Institute (SEI) recently analyzed the alignment of the DoW’s Software Acquisition Pathway (SWP) with the Unified Architecture Framework (UAF). The aim of the study, as detailed in this blog post, is to operationalize model-based systems engineering (MBSE) within the SWP using UAF, which would enhance traceability, decision-making, and compliance across the lifecycle.

The Need for a Model-Centric Acquisition Strategy

The federal government’s digital engineering strategy, initiated in 2018 and reinforced by subsequent directives across military branches, emphasizes the use of digital models as the primary means of communication in engineering activities. The 2023 release of DoDI 5000.97 formalized this shift, requiring programs initiated thereafter to incorporate digital engineering capabilities.

Despite this policy momentum, implementing MBSE across diverse acquisition programs remains challenging. These challenges present valuable opportunities within the SWP. While the policy is designed to streamline software acquisition, there is exciting potential to enhance it further by incorporating clearer guidance on model-based systems engineering (MBSE), especially for embedded software systems that require high levels of certification and assurance.

As part of ongoing work to address these challenges, SEI researchers contributed as panelists at the 22nd Annual Acquisition Research Symposium hosted by the Naval Postgraduate School. We also presented the paper Synergizing the Software Acquisition Pathway (SWP) With the Unified Architecture Framework (UAF) For Operationalization. In this post, we’ll introduce the concepts presented in the paper including an overview of the SWP, UAF, the SEI MBSynergy project, and walk through an example related to developing a Capability Needs Statement for the SWP program using UAF.

A Focus on the Software Acquisition Pathway

The SWP provides a tailored acquisition route for software-intensive systems. More specifically, the SWP provides software-intensive development programs with a streamlined path for developing and delivering software capability, emphasizing the use of modern software development methods and tools for delivering capability rapidly.

The SWP lifecycle is separated into two primary phases:

• The Planning Phase focuses on defining capability needs, developing strategies and roadmaps, establishing infrastructure, and designing system architecture.
• The Execution Phase involves software development, testing, delivery, and value assessment, with continuous user engagement.

The pathway supports various software types, including embedded software, which was the focus of our study. Embedded software, often integrated into weapon systems, requires heightened scrutiny for safety, cybersecurity, and operational effectiveness, making it an ideal candidate for MBSE application.

As of the time of this post, there are programs utilizing the Software Acquisition Pathway across all major departments of the DoW and associated services and the utilization of this pathway is increasing in importance. A March 6, 2025, memo, Directing Modern Software Acquisition to Maximize Lethality directs the DoW to adopt the Software Acquisition Pathway as the preferred pathway for all software development programs.

Benefits of an UAF-Based MBSE Approach

The UAF, developed by the Object Management Group (OMG), is a standardized modeling language that evolved from frameworks like DoDAF, MoDAF, and NATO’s NAF. It provides a comprehensive set of 89 model views organized by stakeholder viewpoints (e.g., operational, security) and modeling aspects (e.g., processes, parameters).

UAF’s structured semantics and extensibility make it well-suited for MBSE in complex defense environments. However, its breadth can be overwhelming for new users. To address this, the SEI study leverages the UAF Domain Meta Model (DMM) version 1.2 and the Enterprise Architecture Guide for UAF to create a targeted, scenario-based approach tailored to the SWP.

The integration of UAF into the SWP offers several strategic advantages:

• enhanced traceability and digital threading. By structuring information in models, programs can establish robust digital threads that link requirements, design decisions, and verification artifacts across the lifecycle.
• improved decision-making. Models enable early analysis of tradeoffs, risks, and quality attributes, supporting more informed and timely decisions.
• reduced documentation burden. Model-based artifacts can replace or augment traditional documents, streamlining compliance with statutory and regulatory requirements.
• greater consistency and reusability. A standardized modeling approach fosters consistency across programs and facilitates reuse of architectural patterns and services.
• alignment with policy and strategy. The approach directly supports DoDI 5000.97 and digital engineering strategies from all military departments, positioning programs for long-term success.

Using Scenarios to Inform Strategic Development

A cohesive, well-designed strategy is needed to inform a consistent digital engineering approach and enable information models to be value-added and more fully integrated into the software development process. The SEI has developed a technique for analyzing enterprise architecture for the organizational value of Digital Engineering and MBSE using a scenario-based approach.

The SEI’s MBSynergy project aims to equip DoW stakeholders with tools and methodologies to evaluate the value of MBSE. Drawing from the Architecture Tradeoff Analysis Method (ATAM), the project introduces a scenario-based modeling approach to define and analyze enterprise activities.

Each scenario is structured as an input/output process involving specific stakeholders, triggers, and measurable quality attributes. This structure enables a detailed analysis of how MBSE contributes to performance, modifiability, availability, and other architectural qualities.

For the SWP, the SEI identified 25 scenarios across the planning and execution phases. These scenarios are grouped under seven enduring tasks depicted in the figure below.

Figure 1: MBSynergy Scenarios of the Software Acquisition Pathwy The figure is based on views from SEI’s “MBSynergy for Software Acquisition Pathway” model that was developed using Cameo Enterprise Architecture.

The core contribution of the study is the mapping of SWP activities to UAF views, transforming document-based processes into structured, analyzable models. This mapping was facilitated by comparing the information requirements of SWP guidance documents with the specifications of UAF views.

Defining Software Pathway Scenarios

One illustrative scenario is the development of the Capability Needs Statement (CNS) document, a foundational document required as part of initiating the execution. Traditionally captured in a static Word template, the Capability Needs Statement includes sections on operational context, capability needs, system architecture, scope, methodologies, schedule, risks, and resource planning. We chose the CNS as the featured scenario because it marks the first artifact created under SWP processes, a foundational step that ensures continuous traceability when embedded early in a digital model throughout the product lifecycle.

In the model-based approach, each section is translated into operational activity actions, each producing specific UAF views. For instance, see Figure 2:

Figure 2: Operational Process Flow for Capability Needs Statement Definition. The figure is based on views from SEI’s “MBSynergy for Software Acquisition Pathway” model that was developed using Cameo Enterprise Architecture.

In this scenario, five key areas were translated into operational activity actions, each generating a set of UAF views. There is an additional summary and overview. These views were then compared to the information described in the template to check for alignment. The goal was to identify a minimal set of views that could meet the information needs without overwhelming model architects and developers with too many specifications.

Each operational activity action is meant to be further broken down by individual programs into detailed sub-activity process flows. These flows help clarify the specific roles and responsibilities of project personnel. The UAF view diagrams shown in the figure serve as examples to guide how elements should be modeled. Ensuring consistency and clarity is a top priority for making the models usable across all SWP users.

The model views that capture these foundational elements of the CNS will remain traceable throughout planning and execution, supporting design, development, and value assessments. This traceability strengthens the connection between early lifecycle information and what’s developed later, both within a scenario and across different scenarios.

To further illustrate what this might look in practice, the SEI is creating an example Capability Needs Statement (CNS) using UAF views to align its core components in a model-based format. This example will show how model data supports other scenarios, highlighting the benefits of improved traceability, reusability, and consistency compared to traditional document-based approaches.

Future Directions and Collaboration Opportunities

The SEI’s study represents a contributing step toward realizing the DoW’s vision for digital engineering. By mapping the Software Acquisition Pathway to the Unified Architecture Framework through a scenario-based approach, the study provides a practical, scalable method for integrating MBSE into software acquisition.

The SEI is actively seeking collaboration with DoW programs to pilot the UAF-based MBSE approach and address other areas of interest relating to the use of models as part of the software development lifecycle including

• continuous model development alongside software delivery
• integration of AI and large language models (LLMs) for model generation and analysis
• embedding UAF data into software factory pipelines for automated decision support

These initiatives aim to further operationalize digital engineering and demonstrate the tangible value of MBSE in real-world acquisition contexts.

This model-centric strategy not only enhances compliance and traceability but also empowers programs to make better decisions, reduce risk, and deliver higher-quality software capabilities. As the DoW continues to modernize its acquisition processes, the integration of UAF and MBSE into the SWP offers a compelling blueprint for success.

The research was an output of the MBSynergy line project sponsored by the Office of the Under Secretary of War for Research and Engineering (OUSW(R&E)).