Hide Notes 

Slide 1: OMG UML Profile for the DoD and MoD Architecture Frameworks (UPDM) Dwayne Hardy American Systems Dwayne.Hardy@AmericanSystems.com Jan 30, 2007
Slide 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! 2
Slide 3: Summary of DoDAF Views NODES TIME A T1 T2 T3 B C System Functionality Description (SV-4) X Y Y X XY Z Systems Functionality Sequence and Timing Description (SV-10 a/b/c) Systems Interface Description (SV-1) Activity to System Function (SV-5) Physical Schema SV-11 CNE T N O NC I O T ND B O OE c System - System Matrix (SV-3) Technical Architecture Profile (TV-1) Standards Technology Forecast (TV-2) S se 3 yt m S se 4 yt m Lc l Ae Nt oa r a e S se 5 yt m E TR A XE N L C NET N O NC I O ( USD T E O TI E H N DS F N E E T O E O I T RS ) CNE T N O NC I O T ND B O OE Sys te m Systems Evolution Description (SV-8) NODE A n ch Te S se 1 yt m T oW w- a y Cm u i ai n o m ctos n Lk is n Ss e 2 yt m OeW n- a y Cm u i ai n o mnc to s Lk i n s ica Systems Communications Description (SV-2) Systems Data Exchange Matrix (SV-6) Systems Performance Parameters Matrix (SV-7) CNE T N O NC I O T ND C O OE Operational Operational Concept Description (OV-1) Systems Technology Forecast (SV-9) Operational Activity Model (OV-5) • ..... • ..... • ..... • ------------------------- l Node Connectivity Description (OV-2) NODES TIME A T1 T2 T3 B C Organizational Relationships Chart (OV-4) Logical Data Model (OV-7) Information Exchange Matrix (OV-3) Operational Activity Sequence and Timing Description (OV-6 a/b/c) 3
Slide 4: MOD Architecture Framework (MODAF) Inputs: Doctrine & SAGs Cap Audit Legacy Systems Standards Prog Plans Inform Outputs: Strategic View Enterprise Architecting Operational View System View Technical View Acquisition View DoDAF Optimise Capability Phasing Provides Operational Concepts Defines System Components & Key Interface Points Structures the Mandated Standards Provides the Route map Improved Policy Coherent Effects System of Systems Standards and Principles NEC Roadmap Context 4 Inform Inform Inform Inform
Slide 5: MODAF StV-5 Capability to Systems Deployment Mapping EPOCH 4 EPOCH 3 EPOCH 2 EPOCH 1 Capability 1 Capability 2 Capability 3 Capability 4 System deployment by operational capability category Overlap of systems between epochs PJHQ JTF LCC Corp Div Bde BG Coy Plt System connectivity and systems involved 5 System deployment by echelon level
Slide 6: AcV-2 SoS Acquisition MODAF Programmes MG 01/10/04 IOC 01/04/05 FOC 01/08/05 System A IG 01/05/04 MG 01/11/04 IOC 01/06/04 System B IG 01/06/04 MG 01/01/05 IOC 01/10/06 System C MG 01/10/04 IOC 01/05/05 FOC 01/01/06 System D DISPOSAL 01/11/04 OUT OF SERVICE 01/06/05 System E 2004 2005 2006 Doct Equi Key to View pment LoD 'Hexagon' Project Phase rine Trai LoDs ning No outstanding issues Manageable issues Critical issues Pre-IG IG to MG MG to IOC IOC to FOC In Service Disposal Peopl e Sust Organi sation ainment 6
Slide 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 Defined its metamodel (M3) as a profile of UML 2 But adds additional viewpoints (perspectives)  MODAF extends DoDAF    NATO and other architecture frameworks further extend DoDAF and MODAF 7
Slide 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 8 DoDAF/MODAF architecture views
Slide 9: Relationship of Standards to DoD’s Architecture Program Explorations * ASM ABM OMG International Vendor tools DODAF 1.5 - 2.0 Academic Industry best practices Federal coordination AP233-CADM mapping spec will define data exchange in XML CCB & AIP OP E RATION AL -NODE P HYS ICA L -N ODE DATA OP E RATION AL -NODE S YS TE M E VE NT-TRIG G E R O PE RA TION AL -AC TIVITY S YS TE M-F UNC TION INF OR MATION S YS TE M DATA P HYS ICA L -N ODE INF OR MATION Evolutions DOD governance a UPDM will define UML/SysML Department processes implementation of DoDAF Transformation products and MOF based Lessonsexchanges data learned CCB & DODAF Working Group • DODAF Vol II structured diagrams • DODAF Vol III chapters on CADM UPDM may define an XMI implementation for this CCB & CADM TWG interface OP E RATIONAL -NODE P HYS IC AL -NODE DATA CADM 1.0x S YS TE M E VE NT-TRIG G E R OP E RATIONAL -AC TIVITY S YS TE M-F UNC TION P E RF ORMANC E TE C HNOL OG Y S TANDARD INF ORMATION PE RF O RMAN CE TE C HN OL OG Y S TA NDARD DARS Federation OP E RATION AL -NODE P HYS ICA L -N ODE INF OR MATION DATA S YS TE M OP E RATION AL -NODE P HYS ICA L -N ODE E VE NT-TRIG G E R O PE RA TION AL -AC TIVITY S YS TE M-F UNC TION INF OR MATION S YS TE M PE RF O RMAN CE TE C HN OL OG Y S TA NDARD E VE NT-TRIG G E R O PE RA TION AL -AC TIVITY S YS TE M-F UNC TION DATA PE RF O RMAN CE TE C HN OL OG Y S TA NDARD E VE NT-TRIG G E R O PE RA TION AL -AC TIVITY S YS TE M-F UNC TION PE RF O RMAN CE TE C HN OL OG Y S TA NDARD CCB & DARS Users Group 9 * NII briefing slide
Slide 10: OMG UPDM RFP Scope      RFP was issued by OMG Sept. 2005 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: http://www.omg.org/cgi-bin/doc?dtc/2005-09-12 10
Slide 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 11
Slide 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 12
Slide 13: SV Metamodel 13
Slide 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 14
Slide 15: SV-1 Example 15
Slide 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  16
Slide 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 17
Slide 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 18
Slide 19: UPDM Timeline LOI Need Feb. 05 Feb 06 Evaluate Submission RFP Sept. 05 Initial Submissions June 06 Vote Adoption of a Specification June 07 Dec. 06 March07 June 07 Issue RFP Evaluate Submissions Revised Submission(s) Implementation ~ 2008 Tools 19
Slide 20: UML Profile for DODAF/MODAF (UPDM) Roadmap DODAF v 1.0 (2004) DODAF v 1.5 Inputs MODAF v 1.0 OMG Kickoff RFP issued 1st draft Submissions revised Submission OMG Adopts UPDM Feb 2005 Sept 2005 June. 2006 March 2007 20
Slide 21: For More Information  DoDAF   http://www.defenselink.mil/nii/doc https://dars1.army.mil/IER/index.jsp  MODAF  http://www.modaf.com  Background on UPDM  http://syseng.omg.org/UPDM.htm  UPDM Request for Proposals (RFP)   http://www.omg.org/techprocess/meetings/schedule/UPDM_RFP.html http://www.omg.org/cgi-bin/doc?dtc/2005-09-12 21  UPDM OMG meeting agendas  http://syseng.omg.org/SE_DSIG_Meetings/
Slide 22: Questions? 22
Slide 23: Backup
Slide 24: Metamodel & TaxonomyRelationship   The metamodel defines Enterprise Architecture concepts The taxonomy supports the metamodel, specializing the model elements into more specific items  metamodel system hosts equipment platform Taxonomy weapon system A system which has the capability to… business system A system which manages the… warship aircraft  Acts as a dictionary of terminology Allows the metamodel to be more generic HR system A system which manages the… accounts system A system which manages the… fighter bomber etc… 24
Slide 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 NATO Taxonomy Sdfjhsdfjhsdf sdfjdsfk nweiewnmn dfldsflmc sdfkmsdm sdfsdf weo 0fhebhn fefwef sdfmdfd sfgsdf sdfsdfgksdfgnf sdfsdofjnsdf sdfhsdeidjjd dsofhsdfoh eee sdadsdwewqffee Sdfksdjfweewmewewf DoD Core Taxonomy Sdfjhsdfjhsdf sdfjdsfknweiewnmn dfldsflmc sdfkmsdm sdfsdf weo 0fhebhn fefwef sdfmdfd sfgsdf sdfsdfgksdfgnf sdfsdofjnsdf sdfhsdeidjjd dsofhsdfoh eee sdadsdwewqffee Sdfksdjfweewmewewf sp ec sp ec sp ial is e AF Equipment Taxonomy Sdfjhsdfjhsdf sdfjdsfk nweiewnmn dfldsflmc sdfkmsdm sdfsdfweo 0fhebhnfefwef sdfmdfd sfgsdf sdfsdfgksdfgnf sdfsdofjnsdf sdfhsdeidjjd dsofhsdfoh eee sdadsdwewqffee Sdfksdjfweewmewewf e ci a li se DODAF Taxonomy synonym ial is e Sdfjhsdfjhsdf sdfjdsfk nweiewnmn dfldsflmc sdfkmsdm sdfsdfweo 0fhebhnfefwef sdfmdfd sfgsdf sdfsdfgksdfgnf sdfsdofjnsdf sdfhsdeidjjd dsofhsdfoh eee sdadsdwewqffee Sdfksdjfweewmewewf Supplier Taxonomy ec sp ial is e sdfjdsfknweiewnmn dfldsflmc sdfkmsdm sdfsdf weo 0fhebhn fefwef sdfmdfd sfgsdf sdfsdfgksdfgnf sdfsdofjnsdf sdfhsdeidjjd dsofhsdfoh eee sdadsdwewqffee Sdfksdjfweewmewewf 25
Slide 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 Tool A Tool B data exchange structure meaning XMI XMI Taxonomy Sdfjhsdfjhsdf sdfjdsfk nweiewnmn dfldsflmc sdfkmsdm sdf sdf weo 0fhebhn fefwef sdfmdfd sfgsdf sdfsdfgksdfgnf sdfsdofjnsdf sdfhsd eidjjd dsofhsdfoh eee sdadsd wewqf fee Sdfksdj fweewmew ewf META MODEL 26
Slide 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 27