1 / 6

Brian Wilczynski Architecture & Interoperability Directorate Office of the DoD CIO

UML Profile for DoDAF/MODAF Information Session Co-Hosted by: DoD CIO/Architecture & Interoperability and SAF/Enterprise Architecting and Warfighting Integration Decision Support Division 16 May 2007. Brian Wilczynski Architecture & Interoperability Directorate Office of the DoD CIO.

pakuna
Download Presentation

Brian Wilczynski Architecture & Interoperability Directorate Office of the DoD CIO

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. UML Profile for DoDAF/MODAFInformation SessionCo-Hosted by: DoD CIO/Architecture & Interoperability and SAF/Enterprise Architecting and Warfighting Integration Decision Support Division16 May 2007 Brian Wilczynski Architecture & Interoperability Directorate Office of the DoD CIO

  2. Beyond DoDAF 1.5 https://dars1.army.mil

  3. Incorporated Net-Centric Content Changed Systems View to Systems/Services View Re-Packaged 3 Volume Set Integrated CADM Added Journal Major Changes in DoDAF 1.5:

  4. DoDAF v2.0 Potential Topics ABM/ASM Service Oriented Architecture Other Frameworks Net-Centric Examples Service Specification Template Capability related concepts Service Interfaces Service Description Framework UPDM Net-Centricity Measurement concepts Operational Node Program vs. Enterprise Architecture Content Strategic Goals Relationship to FEA Information Assurance/Security SA and OO Architecture Tiers Relationship to NCOW RM BPMN Authoritative Sources Alignment to JCIDS/JROC Scoping Workshop in June 2007

  5. DoDAF v2.0 Planned Approach DAS Process JCIDS Process PfM Process External Reporting PPBE Process IRB Processes MODAF TOGAF NAF DoDAF 1.5 Analysis of External Requirements Analysis Of Frameworks Baseline Concept Map Input For Derive Initial Input For DoDAF 2.0 Initial Requirements Set For Re-validate Through DoDAF 2.0 Finalized Requirements For 2.0 Concept Map 2.0 Model Analysis 2.0 Conceptual Data Model Derive Leads To Baseline For ASM BTA UPDM CADM Derive 2.0 Logical Data Model 2.0 Physical Data Model Derive

  6. Our approach to architecture must be as agile as the processes and technology we describe Use DoDAF 1.5 requirements as baseline for DoDAF 2.0 The Core Architecture Data Model (CADM) will be derived from DoDAF 2.0 requirements Structure and content may change The name is the same Establish standards so that architecture data is net-centric DoDAF v2.0 must address evolving information requirements of the Department using both top-down and bottom-up approaches Summary

More Related