1. Object Management Group Unified Architecture Framework (OMG UAF)
Benefits and Costs
Drafted by Leonard Levine, DISA/EE
14 August 2014
8/14/2014
UNCLASSIFIED – FINAL DRAFT
- PRE-DECISIONAL

2. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
Outline
SUMMARY
BENEFITS
U.S. Policy
Practicalities
Unification Power of OMG’s MOF
Outreach and Evolution
Usage:
Acquisition
Tailoring & Influencing Development
Interoperability & Integration
Certifications
Professional Corps of Architects & Systems Engineers
COSTS
PROCESSES
END STATE
RECOMMENDATION
Backup / Background
Baseline of DoD Efforts
History and Evolution
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

3. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
Summary
The Government of the United States (USG) will receive the benefits of a Unified Architecture Framework (UAF) developed by the Object Management Group (OMG) without additional costs to the Department of Defense (DoD) above the current baseline of efforts.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

4. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
Policy
UAF
Complies with the U.S. Government policy promoting the use of “voluntary consensus” standards rather than developing or updating existing government standards;
Draws in participation by other standards development organizations (SDOs) and
Consistent with U.S. Government policy on Intellectual Property Rights (IPR) .
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

5. Practicalities: Beyond Policy
No sense for each organization to write its own Architecture Framework; rather it makes sense to tailor and use a standard.
The OMG UAF will address the Whole of DoDAF, Volume 1, 2 & 3:
DoDAF, Volume Two: Extend the existing work of the UPDM beyond the technical level of metamodeling and physical exchange through XMI, which in essence is the equivalent of Volume II of the three volume DoDAF documentation set.
DoDAF, Vol One: Address approaches/methods and a Conceptual Data Model, which are the essence of DoDAF Volume I; and
DoDAF, Volume Three: Unify and expand the physical exchange beyond the current separate specifications of UPDM/XMI and DoDAF physical exchange specification XML, covered in part by DoDAF Volume III .
The UAF will extend to include new vendors and specifications & standards beyond OMG.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

6. Unification Power of OMG’s Meta Object Facility (MOF)
MOF underlies many of OMG’s specifications including UPDM, SysML, UML, NIEM UML. Strength to accomplish added levels of interoperability:
Models can be exported from one application, imported into another
Models can be transported across a network, stored in a repository
Models can be retrieved, rendered into different formats
including XMI, OMG's XML-based standard format for model transmission and storage
Models can be transformed, and used to generate application code.
Not restricted to structural models, or even to models defined in UML - behavioral models and data models also participate in this environment, and non-UML modeling languages can partake
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

7. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
Outreach & Evolution
The OMG for the UAF Initiative will
Reach out to other bodies and
Include other specifications, documents, and frameworks
Ease and facilitate work of DoD Architects by providing more interoperability among tools in related areas not previously covered such as portfolio management.
Specifically include current versions of DoDAF as well as
MODAF, DNDAF, and NAF
Federal Enterprise Architecture Framework (FEA)
Follow-up & compatibility with current development of UPDM Version 3.0 (based on DoDAF 2.02 Change 1).
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

8. Outreach: Embracing Complementary & Competing Frameworks One Example
Take Open Group’s TOGAF as an example
Originated many years ago in DoD,
Potential for unification is in the similarity of its Architecture Development Method (ADM) with DoDAF Volume 1’s Capabilities, Activities, Resources, and Performers (C.A.R.P.) and DoDAF 6-Step Architecture Development Processes.
Previous proposals to unify via the OMG Meta Object Facility (MOF)
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

9. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
Usage: Acquisition
Requiring and/or Mandating use of UAF
Acquisition Process
Issuance of Government RFPs, contracts and the like requiring compliance with an OMG/ISO UAF are likely to lead to more standardized architecture & engineering deliverables than citing the current DoDAF.
DoDAF is not a citable standard.
Not a value judgment on DoDAF, just a fact.
Not mandate-able in DISR
Engineering integrity is likely to increase due to the standardization of architecture deliverables and their model base.
The same models used at high level enterprise architecture can be re-used & modified for lower level solution architectures including systems engineering.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

10. Use: Tailoring and Influencing Development
Ease burdens of maintaining individual, independent architecture frameworks.
USG or DoD could Issue tailoring instructions
Amplifying or tailoring the use of UAF in their context
Format: as a supplement, annex, or separate document
USG or DoD Influence Direction of UAF
Levy or raise Formal “Issues” through the OMG process
Participate in OMG through Task Forces such as C4I (parent of UPDM Group) and Analysis & Design as it does currently and other groups such as Liaison Subcommittee of OMG Architecture Board.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

11. Interoperability & Integration
Builds upon and extends UPDM
Already provided a measure of interoperability with allies.
UAF will provide closer integration between DoDAF (and potentially MODAF and NAF) with UPDM, definitely a good thing for all.
While a NATO STANAG is a theoretical possibility, there is no assurance that even the U.S. will endorse or endorse without disabling dissent or reservation.
UAF can incorporate progress made at NATO without waiting for a STANAG. Also not all commercial vendors will implement a STANAG. OMG can also incorporate or conform to a STANAG if one should emerge.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

12. Certifications: Professional Corps of Architects & Systems Engineers
OMG will be able to provide Certifications in Architecture using the UAF
similar to its current certification programs in
Business Processing
Systems Engineering
Consequently, it is likely that a Corps of Professionally Certified Architects will emerge
UAF will promote the discipline of engineering based on Model Driven Architecture (MDA)
MDA is taught at many universities and is supported by a large professional literature
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

13. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
Costs
No known additional costs to DoD above the baseline of efforts.
OMG through its members, particularly Vendors of Architecture and Systems Engineering Tools and Services, will bear the burden of this initiative.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

14. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
Processes - 1
The OMG will follow their own well-known and tested processes for the development of specifications and for the submission of such specifications to ISO .
This includes Requests for Information, Request for Proposals, Proposal Responses, Issue Management, and Issue Resolutions. New requirements will be handled through RFP or Issues
OMG assures practicality of its specifications by requiring commitment from three or more vendors to field implementations before it will finalize and publish a public specification.
The UAF will be vetted through a series of Task Forces that will include the Government Task Force and the Analysis & Design Task Force as well as the C4I Task Force that oversees the current UPDM development.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

15. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
Processes - 2
Continuing… The OMG will follow their own well-known and tested processes for the development of specifications and for the submission of such specifications to ISO .
Proposed specifications must be reviewed and approved by the overarching OMG Architecture Board (AB) that aims to enforce compatibility and interoperability as well as technical correctness.
OMG also provide other services such as Wiki development site and a Technical Editor.
OMG through its Liaison Subcommittee will submit the UAF specification to ISO or ISO-IEC for a speedy adoption with issues and updates reserved for OMG. Issues from ISO will be handled as Issues from members such as DoD through the formal Issue and the Revision Task Force procedures.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

16. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
End State
First, a Publicly Available Specification freely available from OMG (OMG PAS)
Second, a full International Standard (IS) available from ISO.
Conformant tools from commercial vendors should be available shortly after an OMG PAS.
Interoperable
Anticipate competitive tools & pricing.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

17. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
Recommendation
A Letter or Memorandum of Support from DoD-CIO/A&I to OMG for UAF is highly recommended.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

18. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
Background/Backup
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

19. Baseline of DoD Efforts - 1
DoDAF development continues at slower pace with the release of Change 1.
 OMG UPDM Group development continues with UPDM 3.0
unifies the metamodels of DoDAF, MODAF, DNDAF, and other frameworks. UPDM 3.0 I
working on DoDAF 2.02 Change 1 [DoDAF], particularly DoDAF Meta Model [DM2].
Resulting specification should be ready in about a year and
Compliant tools shortly thereafter.
We can expect at least four (4) major architecture tools to implement UPDM 3.
UPDM 3, like UPDM 2, will be submitted to the International Organization for Standardization (ISO) and a full International Specification can be expected a year later.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

20. Baseline of DoD Efforts - 2
 The Defense Information Systems Agency (DISA)
pays OMG annual fee of approximately $12,800 for DoD membership at Government rate,
provides one senior computer scientist at approx. 50% time, and
assumes meeting fees ($2000) and travel expenses for four meetings per year ($10,000).
DoD-CIO, Architecture & Interoperability devotes
a senior engineer at approx. 50% and a contract architecture specialist at 50% time to develop or customize or apply DoDAF (a small part of which is devoted to OMG UPDM)
assumes travel expenses for one person to two OMG meetings per year ($7,500).
DoD-CIO participates in the Federal Enterprise Architecture (FEA) and related Federal processes as well as the NATO CaT processes.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL

21. UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL
History and Evolution
UAF initiative is a direct descendant and evolution from a decade-long, successful history of collaboration between DoD and OMG.
Work started early in 2005, immediately after the issuance of DoD Architecture Framework (DoDAF 1.0), resulting in a OMG Request for Proposal (RFP) for a UML Profile for DoDAF and MODAF, issued in September 2005.
After a regrouping for DoDAF 1.5 (issued in 2007), OMG changed the name slightly to Unified Profile for DoDAF and MODAF and issued UPDM 1.0 in December 2009.
UPDM 2.0 responded to DoDAF 2.0 in January 2013.
UPDM 3.0 (well underway in August 2014) will respond to DoDAF 2.02 Change 1.
DoD, first under ATL , and then under DoD-CIO/A&I has been intensively involved from the beginning. The UK MOD has had an equally successful relationship with OMG in this area.
8/14/2014
UNCLASSIFIED – FINAL DRAFT - PRE-DECISIONAL