OMG UML Profile for the DoD and MoD Architecture Frameworks (UPDM) Dwayne Hardy American Systems Jan 30, 2007

2 UML Profile for DoDAF/MODAF (UPDM) Overview OMG initiative underway to develop tool specification for representing & exchange of DODAF and MODAF products Requirements (RFP) issued Sept 05 Initial submissions received June 06 Final submissions expected Mar ‘07 Goal is to provide robust architecture modeling capability, improve communications and tool interoperability, and reduce re-training Multiple tool vendors and users participating Should leverage SysML, UML and BPMN and experience gained from existing tools DoD & UK MOD are supporting and hope to adopt!

3 Operational Systems Technical Operational Concept Description (OV-1) Node Connectivity Description (OV-2) X Y X Z X Y Y Systems Interface Description (SV-1) Operational Activity Model (OV-5) Information Exchange Matrix (OV-3) Activity to System Function (SV-5) System Functionality Description (SV-4) Organizational Relationships Chart (OV-4) Systems Data Exchange Matrix (SV-6) Operational Activity Sequence and Timing Description (OV-6 a/b/c) Systems Communications Description (SV-2) System - System Matrix (SV-3) Systems Technology Forecast (SV-9) Standards Technology Forecast (TV-2) Technical Architecture Profile (TV-1) Systems Performance Parameters Matrix (SV-7) Logical Data Model (OV-7) Systems Functionality Sequence and Timing Description (SV-10 a/b/c) Systems Evolution Description (SV-8) Physical Schema SV-11 ABC T1 T2 T3 NODES TIME ABC T1 T2 T3 NODES TIME c Summary of DoDAF Views

4 Coherent Effects System of Systems Standards and Principles Provides Operational Concepts Defines System Components & Key Interface Points Structures the Mandated Standards Improved Policy Optimise Capability Phasing NEC Roadmap Context Provides the Route mapOutputs: Legacy Systems Standards Prog Plans Cap Audit Inform Inputs: Doctrine & SAGs DoDAF Enterprise Architecting Acquisition View Strategic View Operational View System View Technical View MOD Architecture Framework (MODAF)

5 StV-5 Capability to Systems Deployment Mapping MODAF

6 AcV-2 SoS Acquisition Programmes MODAF

7 Motivation for UPDM UML is used extensively to represent architecture products (e.g., artifacts) across industry DoDAF v1.0 Volume II provides guidance on using UML But based on UML 1.x which has been superseded by UML 2 MODAF extends DoDAF Defined its metamodel (M3) as a profile of UML 2 But adds additional viewpoints (perspectives) NATO and other architecture frameworks further extend DoDAF and MODAF

8 Goals for UPDM Significantly enhance the quality, productivity, and effectiveness associated with architecture and system of systems modeling Enable architecture model reuse and maintainability Improve tool interoperability and communications between stakeholders Reduce training impacts due to different tool implementations and semantics Develop UML Profile for DoDAF/MODAF that provides industry standard UML/SysML representation of DoDAF/MODAF architecture views

9 Relationship of Standards to DoD’s Architecture Program Explorations * ASM ABM OMG International Vendor tools Academic Industry best practices Federal DOD governance Department processes Transformation Lessons learned Evolutions CCB & DODAF Working Group CCB & CADM TWG CCB & DARS Users Group coordination CCB & AIP CADM 1.0x DODAF DARS Federation DODAF Vol II structured diagrams DODAF Vol III chapters on CADM DODAF Vol II structured diagrams DODAF Vol III chapters on CADM UPDM will define a UML/SysML implementation of DoDAF products and MOF based data exchanges UPDM may define an XMI implementation for this interface AP233-CADM mapping spec will define data exchange in XML * NII briefing slide

10 OMG UPDM RFP Scope RFP was issued by OMG Sept Uses DoDAF v1.0 as a baseline Incorporates MODAF’s additional views (Acquisition and Strategic views) Incorporates additional requirements from DoDAF 1.5 Supports modeling system-of-systems architectures Systems that include hardware, software, data, personnel, procedures, and facilities (DOTMLPF & MOD Lines of Development ) Service oriented architectures and net-centricity RFP page:

11 UPDM RFP Requirements - Mandatory Develop profile that specifies Metamodel (abstract syntax and constraints) UML2 Profile Notation (concrete syntax) DoDAF and MODAF artifacts Additional views and viewpoints Element taxonomy reference Data interchange

12 Metamodel Defines: Key terms and definitions used in the proposed profile Concepts that are required for the description of architectures and consistent with those defined in IEEE 1471 and specific architecture frameworks (e.g., DoDAF, MODAF) Constraints on elements that ensure connectivity and integrity of the model

13 SV Metamodel

14 Profile & Notation Defines: The selected UML modeling elements using a standard notation Their stereotypes Additional constraints using the profiling mechanism provided by UML The relationship of notation to model elements defined by the metamodel shall be represented in tabular form

15 SV-1 Example

16 Views & Viewpoints DODAF/MODAF artifacts using UML/SysML New model elements using MOF QVT, when no direct diagrammatic representation is provided for individual DODAF and MODAF artifacts in UML/SysML

17 Creating the SV-5: An Illustration of Exported Information The SystemThreads and SystemEventTraces placed in the OperationalActivityRealization collaboration provides the information needed for the SV-5

18 UPDM Team Members Adaptive Artisan Software BAE Systems CSCI General Dynamics IBM Lockheed Martin Mega International No Magic NorthropGrumman Raytheon SAIC Sparx Systems Thales Telelogic

19 Issue RFP Vote Adoption of a Specification June 07 RFP Feb. 05 Initial Submissions June 06 Revised Submission(s) Dec. 06 Evaluate Submissions Evaluate Submission Tools Need Implementation ~ 2008 LOI Feb 06 UPDM Timeline Sept. 05 June 07March07

20 UML Profile for DODAF/MODAF (UPDM) Roadmap June Sept 2005 Feb 2005 DODAF v 1.0 (2004) OMG Kickoff RFP issued OMG Adopts UPDM MODAF v 1.0 March st draft Submissions DODAF v 1.5 Inputs revised Submission

21 For More Information DoDAF MODAF Background on UPDM UPDM Request for Proposals (RFP) UPDM OMG meeting agendas

22 Questions?

Backup

24 Metamodel & Taxonomy- Relationship The metamodel defines Enterprise Architecture concepts The taxonomy supports the metamodel, specializing the model elements into more specific items Acts as a dictionary of terminology Allows the metamodel to be more generic system equipment platform hosts metamodel Taxonomy A system which has the capability to… weapon system A system which manages the… business system A system which manages the… HR system A system which manages the… accounts system warshipaircraft fighter bomber etc…

25 Distributed Taxonomies OWL is designed for the web: Allowing references between OWL files at different locations (e.g. synonyms) Allowing one OWL file to specialise definitions in other files

26 Data Exchange UML profile and meta-model enable XMI for architecture tool interoperability. Elements in the XMI exchange file may refer to relevant taxonomy definitions

27 XMI for Data Exchange XML is an industry standard XMI is XML for model interchange UPDM requires XML that conforms to a model Make use of “vanilla” XMI with heavy use of stereotypes Specified by extending the UML meta model Meta Object Facility (MOF) UML Meta Model UPDM Meta Model stereotype specifications XMI for UML Stereotypes