1 / 27

OMG UML Profile for the DoD and MoD Architecture Frameworks (UPDM)

OMG UML Profile for the DoD and MoD Architecture Frameworks (UPDM). Dwayne Hardy American Systems Dwayne.Hardy@AmericanSystems.com Jan 30, 2007. UML Profile for DoDAF/MODAF (UPDM) Overview.

iain
Download Presentation

OMG UML Profile for the DoD and MoD Architecture Frameworks (UPDM)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OMG UML Profile for theDoD and MoD Architecture Frameworks (UPDM) Dwayne Hardy American Systems Dwayne.Hardy@AmericanSystems.com 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. Summary of DoDAF Views NODES A B C TIME System Functionality Description (SV-4) T1 T2 T3 Systems Functionality Sequence and Timing Description (SV-10 a/b/c) Technical Architecture Profile (TV-1) Physical Schema SV-11 Standards Technology Forecast (TV-2) Systems Evolution Description (SV-8) System - System Matrix (SV-3) Systems Interface Description (SV-1) Activity to System Function (SV-5) Systems Technical • -------------------------------- Systems Communications Description (SV-2) • ..... Operational • ..... • ..... Systems Data Exchange Matrix (SV-6) Systems Performance Parameters Matrix (SV-7) X Y X Z Y Operational Concept Description (OV-1) Y X Systems Technology Forecast (SV-9) Operational Activity Model (OV-5) Node Connectivity Description (OV-2) NODES A B C TIME T1 T2 T3 Operational Activity Sequence and Timing Description (OV-6 a/b/c) Organizational Relationships Chart (OV-4) Information Exchange Matrix (OV-3) Logical Data Model (OV-7) c

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

  5. EPOCH 4 Overlap of systems System deployment between epochs EPOCH 3 by operational capability category EPOCH 2 EPOCH 1 Capability 1 Capability 2 Capability 3 Capability 4 PJHQ JTF LCC System deployment by echelon level Corp Div Bde BG Coy Plt System connectivity and systems involved StV-5 Capability to Systems Deployment Mapping MODAF

  6. MG 01/10/04 IOC 01/04/05 FOC 01/08/05 System A IOC 01/06/04 IG 01/05/04 MG 01/11/04 System B IOC 01/10/06 IG 01/06/04 MG 01/01/05 System C MG 01/10/04 IOC 01/05/05 FOC 01/01/06 System D OUT OF SERVICE 01/06/05 DISPOSAL 01/11/04 System E 2004 2005 2006 Doctrine LoD 'Hexagon' Project Phase Equipment Training Pre-IG No outstanding issues IG to MG Key to View Manageable issues LoDs MG to IOC Critical issues People Sustainment IOC to FOC Organisation In Service Disposal 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 Evolutions Explorations * DOD governance Department processes Transformation Lessons learned ASM ABM OMG International Vendor tools Academic Industry best practices Federal UPDM will define a UML/SysML implementation of DoDAF products and MOF based data exchanges DODAF 1.5 - 2.0 CCB & DODAF Working Group • DODAF Vol II structured diagrams • DODAF Vol III chapters on CADM coordination AP233-CADM mapping spec will define data exchange in XML UPDM may define an XMI implementation for this interface CADM 1.0x CCB & CADM TWG CCB & AIP CCB & DARS Users Group DARS Federation * NII briefing 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

  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. Adaptive Artisan Software BAE Systems CSCI General Dynamics IBM Lockheed Martin Mega International No Magic NorthropGrumman Raytheon SAIC Sparx Systems Thales Telelogic UPDM Team Members

  19. Need IssueRFP EvaluateSubmissions UPDM Timeline LOIFeb 06 EvaluateSubmission Vote Adoption of a Specification June 07 RFP Feb. 05 InitialSubmissions Sept. 05 Dec. 06 March07 June 07 RevisedSubmission(s) June 06 Tools Implementation ~ 2008

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

  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 • UPDM OMG meeting agendas • http://syseng.omg.org/SE_DSIG_Meetings/

  22. Questions?

  23. Backup

  24. 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 metamodel equipment hosts system platform Taxonomy weapon system business system warship aircraft A system A system which which has the manages the … capability to … accounts system HR system bomber fighter A system which A system which manages the … manages the … etc … Metamodel & Taxonomy-Relationship

  25. NATO DoD Core Sdfjhsdfjhsdf Sdfjhsdfjhsdf sdfjdsfk nweiewnmn sdfjdsfk nweiewnmn dfldsflmc dfldsflmc Taxonomy Taxonomy sdfkmsdm sdfkmsdm sdf sdf weo sdf sdf weo 0fhebhn fefwef 0fhebhn fefwef sdfmdfd sfgsdf sdfmdfd sfgsdf sdfsdfgksdfgnf sdfsdfgksdfgnf sdfsdofjnsdf sdfsdofjnsdf sdfhsd eidjjd sdfhsd eidjjd dsofhsdfoh eee dsofhsdfoh eee sdadsd wewqf fee sdadsd wewqf fee Sdfksdj fweewmew ewf Sdfksdj fweewmew ewf specialise specialise specialise AF DODAF Sdfjhsdfjhsdf Sdfjhsdfjhsdf sdfjdsfk nweiewnmn sdfjdsfk nweiewnmn dfldsflmc dfldsflmc Equipment Taxonomy sdfkmsdm sdfkmsdm sdf sdf weo sdf sdf weo 0fhebhn fefwef 0fhebhn fefwef sdfmdfd sfgsdf sdfmdfd sfgsdf synonym Taxonomy sdfsdfgksdfgnf sdfsdfgksdfgnf sdfsdofjnsdf sdfsdofjnsdf sdfhsd eidjjd sdfhsd eidjjd dsofhsdfoh eee dsofhsdfoh eee sdadsd wewqf fee sdadsd wewqf fee Sdfksdj fweewmew ewf Sdfksdj fweewmew ewf specialise Supplier sdfjdsfk nweiewnmn dfldsflmc Taxonomy sdfkmsdm sdf sdf weo 0fhebhn fefwef sdfmdfd sfgsdf sdfsdfgksdfgnf sdfsdofjnsdf sdfhsd eidjjd dsofhsdfoh eee sdadsd wewqf fee Sdfksdj fweewmew ewf 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. Tool A Tool B data exchange structure meaning XMI Taxonomy XMI Sdfjhsdfjhsdf Sdfjhsdfjhsdf sdfjdsfk sdfjdsfk nweiewnmn nweiewnmn dfldsflmc dfldsflmc sdfkmsdm sdfkmsdm sdf sdf sdf sdf weo weo 0fhebhn 0fhebhn fefwef fefwef sdfmdfd sdfmdfd sfgsdf sfgsdf sdfsdfgksdfgnf sdfsdfgksdfgnf META sdfsdofjnsdf sdfsdofjnsdf sdfhsd sdfhsd eidjjd eidjjd dsofhsdfoh dsofhsdfoh eee eee MODEL sdadsd sdadsd wewqf wewqf fee fee Sdfksdj Sdfksdj fweewmew fweewmew ewf ewf 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. Meta Object Facility (MOF) UML Meta Model UPDM Meta Model stereotype specifications XMI Spec XMI for UML Stereotypes 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

More Related