Talk:UPDM

The government has a lot to learn about working in an open standards forum.

Proposal: replace the one-line "Transition to UAF" section with a sourced section

Disclosure: I contribute to the OMG UAF task force. I am proposing this text here rather than editing the article directly.

The "Transition to UAF" section is a single sentence and a bare link to a 2015 slide deck. UAF has been the successor to UPDM since 2017 and is now at version 1.3, and NATO names its metamodel in NAF v4.1. I propose two changes.

1. Replace the "Transition to UAF" section with the text below. It is sourced to the OMG specification, the NAF v4.1 document, the UK MOD withdrawal notice, and three published papers, two of them by authors outside the UAF effort (Eichmann et al. 2019, Torkjazi and Raz 2024).

2. Add one sentence to the lead, after the first sentence: "UPDM has been superseded by the OMG Unified Architecture Framework (UAF)." The lead is tagged for rewrite, and this is the fact a reader most needs.

I am not proposing a rename or a standalone UAF article at this stage. If the section stands, the red link to Unified Architecture Framework elsewhere on Wikipedia can point to it as a section link.

Proposed section wikitext:

== Transition to the Unified Architecture Framework ==
In October 2017 the OMG adopted the '''Unified Architecture Framework''' (UAF) as the successor to UPDM.<ref name="OMG-UAF">{{cite web |title=About the Unified Architecture Framework Specification Version 1.3 |url=https://www.omg.org/spec/UAF/ |publisher=Object Management Group |access-date=15 September 2026}}</ref><ref name="Hause2017">{{cite journal |last1=Hause |first1=Matthew |last2=Bleakley |first2=Graham |last3=Morkevicius |first3=Aurelijus |title=Technology Update on the Unified Architecture Framework (UAF) |journal=INSIGHT |volume=20 |issue=2 |year=2017 |pages=71–78 |doi=10.1002/inst.12153}}</ref> UAF evolved from UPDM version 2.1 and extends its scope from military to commercial architectures. Its stated intent is a standard representation for enterprise architectures using a [[model-based systems engineering]] approach.<ref name="UAF13-DMM">{{cite book |title=Unified Architecture Framework (UAF) Domain Metamodel, Version 1.3 |publisher=Object Management Group |date=September 2025 |id=formal/25-10-01 |url=https://www.omg.org/spec/UAF/1.3/DMM/PDF |at=Sections 1.2 and 7 |access-date=15 September 2026}}</ref>

UAF differs from UPDM in two ways. It is published in two parts, a Domain Metamodel (DMM) that is independent of any modeling language, and a UML/SysML profile (UAFML) that implements the metamodel in modeling tools. Its views are also organized as a grid. Each row is a viewpoint, such as Strategic, Operational, Services, Personnel, Resources, Security, Projects or Standards. Each column is an aspect, such as Taxonomy, Structure, Connectivity, Processes, States, Information, Constraints or Roadmap. Each cell is a view specification traced to the frameworks UAF was built from.<ref name="UAF13-DMM"/>

The core concepts of UAF come from the DoDAF 2.02 metamodel (DM2), the MODAF ontological data exchange mechanism (MODEM), the security views of Canada's DNDAF, and NAF version 4. The UAFML can be used to develop architectures compliant with DoDAF 2.02, MODAF, and NAF versions 3.1 and 4.<ref name="UAF13-DMM"/> The UK Ministry of Defence withdrew MODAF on 15 January 2021 and replaced it with NAF version 4.<ref name="MODAF-withdrawn">{{cite web |title=MOD Architecture Framework |url=https://www.gov.uk/guidance/mod-architecture-framework |publisher=UK Ministry of Defence |access-date=15 September 2026 |quote=MODAF has been replaced with the NATO Architecture Framework (NAF) V4.}}</ref> NAF version 4.1, issued in March 2026, accepts either the UAF Domain Metamodel or ArchiMate as the metamodel for compliant architectures.<ref name="NAFv41">{{cite book |title=NATO Architecture Framework Version 4.1 |publisher=NATO Digital Policy Committee, Architecture Capability Team |date=March 2026 |edition=Document Version 2026.03 |url=https://www.nato.int/content/dam/nato/webready/documents/publications-and-reports/NATO-Architecture-Framework-v4-1-en.pdf |at=Chapter 4, sections 1.1.4 to 1.3.3 |access-date=15 September 2026}}</ref>

UAF version 1.1 was adopted in April 2020, version 1.2 in July 2022, and version 1.3 in 2025.<ref name="OMG-UAF"/><ref name="UAF13-DMM"/>

Published applications of UAF include a system-of-systems development case study,<ref name="Eichmann2019">{{cite conference |last1=Eichmann |first1=Oliver C. |last2=Melzer |first2=Sylvia |last3=God |first3=Ralf |title=Model-based Development of a System of Systems Using Unified Architecture Framework (UAF): A Case Study |conference=2019 IEEE International Systems Conference (SysCon) |year=2019 |doi=10.1109/syscon.2019.8836749}}</ref> a method for integrating autonomy into a system of systems,<ref name="Torkjazi2024">{{cite journal |last1=Torkjazi |first1=Mohammadreza |last2=Raz |first2=Ali K. |title=Model-Based Systems Engineering (MBSE) Methodology for Integrating Autonomy into a System of Systems Using the Unified Architecture Framework |journal=INCOSE International Symposium |year=2024 |doi=10.1002/iis2.13195}}</ref> and work on aligning UAF enterprise models with SysML system models.<ref name="Martin2023">{{cite journal |last1=Martin |first1=James N. |last2=Brookshier |first2=Daniel |title=Linking UAF and SysML Models: Achieving Alignment between Enterprise and System Architectures |journal=INCOSE International Symposium |volume=33 |issue=1 |year=2023 |pages=1132–1155 |doi=10.1002/iis2.13074}}</ref>

Objections, corrections, or better independent sources welcome. Techwzrd (talk) 21:26, 15 September 2026 (UTC)