Draft:Unified Architecture Framework


The Unified Architecture Framework (UAF) is a architecture framework for creating architectural descriptions for commercial, government and defense agencies.[1] UAF is compatible with the Department of Defense Architecture Framework (DoDAF) and Ministry of Defence Architecture Framework (MODAF), and adds elements from the Canadian Department of National Defence Architecture Framework (DNDAF) and NATO Architecture Framework (NAF) to provide a unified standard.[2][3]

The UAF Standard

The UAF standard is maintained by the Object Management Group (OMG), and includes contributions by 29 OMG member organizations. The UAF standard can be downloaded from the OMG website.[1]

OMG also organizes an annual UAF Summit with speakers from defense and industry.[4] Past presentations from 2022 onwards can be downloaded from the OMG events site, or viewed on BrightTALK or YouTube:

UAF Summit agendas and download links for years prior to 2022 are listed on the OMG UAF Wiki start page, in the Resources section.[3]

UAF Standard Components

UAF defines a set of View Specifications for describing an architecture, organized in a two-dimensional grid of Viewpoints (stakeholder concerns) and Aspects (ways to view architecture elements). The UAF Standard is divided into 2 parts:[1][3][5]

  • The UAF Domain Metamodel (DMM) that formally defines the View Specifications
  • The UAF Profile (UAFP) for SysML, also known as the UAF Modeling Language (UAFML)

The DMM is also released as ISO standard ISO/IEC 19540-1:2022, and the UAFP is released as ISO/IEC 19540-2:2022.

UAF Standard History

There have been 4 releases of the UAF specification:

UAF Usage

United States Department of Defense

Retirement of DoDAF

The National Defense Authorization Act for FY2024 section 811, Modernizing the Department of Defense Acquisition Process, mandated that the Department of Defense "retire and replace the Department of Defense Architecture Framework with a new structure focused on enabling interoperability through application program interfaces, enterprise architectures and platforms, and government and commercial standards".[6] The subsequent final report in July 2025 from the Joint Requirements Oversight Council to Congress regarding Section 811 included Reform Element B.7 Retire & Replace DoDAF, though it did not specifically state that UAF would be its successor.[7]

US Army PEO Aviation

In 2024, the US Army Program Executive Office - Aviation (PEO AVN) completed the definition of its Enterprise Architecture Framework (EAF) which included a transition from UPDM to UAF.[8] The EAF and its use of UAF was cited as a key element of the PEO AVN Open Systems Architecture (OSA) strategy.[9]

US Army ACIDS

In 2025, the Army Futures Command released the Army Capabilities Integration & Development System (ACIDS) Process Guide, mandating the use of UAF, although still allowing similar DoDAF views in some cases.[10]

Model-Based Acquisition

In 2022, OMG started the Model-Based Acquisition User Group Community (MBAcq), with the goal of promoting and standardizing the use of MBSE during the systems acquisition process. MBAcq defines a UAF-based process for creating and responding to a Request for Proposal (RFP), in which the acquirer's RFP and vendor's resulting proposals are all expressed as UAF models.[11][12][13]

References

  1. ^ a b c "About the Unified Architecture Framework Specification Version 1.3". www.omg.org. Retrieved 2026-04-26.
  2. ^ MORKEVIČIUS, Aurelijus (25 June 2022). "Past, Present, and Future of the Unified Architecture Framework (UAF)" (PDF). INCOSE.{{cite web}}: CS1 maint: url-status (link)
  3. ^ a b c "start [UAF Wiki]". www.omgwiki.org. Retrieved 2026-04-26.
  4. ^ "Calendar of Events | Object Management Group". www.omg.org. Retrieved 2026-05-17.
  5. ^ "Unified Architecture Framework (UAF) | The Aerospace Corporation". aerospace.org. 2026-03-31. Retrieved 2026-05-17.
  6. ^ "National Defense Authorization Act for Fiscal Year 2024" (PDF). Congress.gov | The Library of Congress. 2023-12-22. Retrieved 2026-05-18.{{cite web}}: CS1 maint: url-status (link)
  7. ^ "FY24 NDAA Section 811 Report to Congress" (PDF). Official Website of the Joint Chiefs of Staff. 2025-07-23. Retrieved 2026-05-18.{{cite web}}: CS1 maint: url-status (link)
  8. ^ DuBois, Thomas A.; Stough, John; Zook, Keith B.; Steiger, Matthew J.; Scott, Ethan; Cleary, Aaron; Hay, Jonathan; R. Alan Hammond, Jr (2024-05-07). "Introduction to the US Army PEO Aviation (PEO AVN) Enterprise Architecture Framework (EAF)". SAE Mobilus. The Vertical Flight Society. doi:10.4050/F-0080-2024-1169.
  9. ^ Sipe, Matt (2022-11-01). "PEO Aviation Modular Open Systems Approach (MOSA)" (PDF). U.S. Army. Retrieved 2026-05-17.{{cite web}}: CS1 maint: url-status (link)
  10. ^ "Army Capabilities Integration & Development System (ACIDS) Process Guide" (PDF). Warfighting Acquisition University. 2025-05-30. Retrieved 2026-05-17.{{cite web}}: CS1 maint: url-status (link)
  11. ^ "Model-Based Acquisition User Group Community | Object Management Group". www.omg.org. Retrieved 2026-05-19.
  12. ^ Hart, Laura E; Hause, Matthew C (2023). "1. Model-Based Acquisition (MBAcq): Uniting Government and Industry around a Common Standard". INCOSE International Symposium. 33 (1): 1203–1223. doi:10.1002/iis2.13078. ISSN 2334-5837.
  13. ^ Hart, Laura (2023-01-28). "OMG Model-based Acquisition (MBAcq) User Group A Government & Industry Collaboration Update". Object Management Group. Retrieved 2026-05-18.{{cite web}}: CS1 maint: url-status (link)

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.