DoD Enterprise Architecture & Standards The Future of Architecture 16 September 2009

1. Walt Okon Senior Architect Engineer Senior Architect Engineer for Information Sharing Enterprise Architecture and Standards Directorate DoD Chief Information Officer (703) 607- 0502 . walt.okon@osd.mil DoD Enterprise Architecture & StandardsThe Future of Architecture16 September 2009

2. DoD Agenda for OMG 0900 - 0915 Future of Architecture; Vision, Mission, Deliver 0916 – 0945 DoD Organization, Governance, and Process 0945 – 1010 Refreshment Break 1010 – 1030 DoD IT Standards Program (DISR) 1030 – 1050 DoDAF Version 2.0 1050 – 1110 DoD Information Enterprise Architecture v1.1 1110 – 1120 EA Federation 1120 – 1130 Information Sharing Segment Architecture 1130 – 1140 Break 1140 – 1155 DoD Architecture Education & Training 1155 – 1210 DoD Architecture Exchange – UPDM V2.0

3. UPDM – Unified Profile for DoDAF/MODAF Unalienable Rights: Life, Liberty and pursuit of Happiness Defense Architecture Framework

5. DoD Architecture Federation Ref Models Tech Stds Arch Guidance Laws, Regs, and Policy Tools DoD EA RM DoDAF Laws Regs Policy DISR DARS DITPR Force Application Building Partnerships Command & Control Net-centric Joint Capability Areas Battlespace Awareness Protection Logistics Solution Architectures Force Support Corporate Management & Support Dept of Army Dept of Navy Air Force Army Architecture DON Architecture Air Force Architecture DoD Enterprise Architecture Information Enterprise Architecture Dept of Air Force SOCOM Other DIA NGA NRO NSA DLA DISA 5 5

6. DoDAF V2.0 Viewpoints That Fit-the-Purpose Capability Viewpoint Articulate the capability requirement, delivery timing, and deployed capability Operational Viewpoint Articulate operational scenarios, processes, activities & requirements Project Viewpoint Describes the relationships between operational and capability requirements and the various projects being implemented; Details dependencies between capability management and the Defense Acquisition System process. Standards Viewpoint Articulate applicable Operational, Business, Technical, and Industry policy, standards, guidance, constraints, and forecasts Data and Information Viewpoint Articulate the data relationships and alignment structures in the architecture content All Viewpoint Overarching aspects of architecture context that relate to all models Services Viewpoint Articulate the performers, activities, services, and their exchanges providing for, or supporting, DoD functions Systems Viewpoint Articulate the legacy systems or independent systems, their composition, interconnectivity, and context providing for, or supporting, DoD functions Renamed New New New New Architecture viewpoints are composed of data that has been organized to facilitate understanding. 6

7. “Fit for Purpose” DoDAF Architecture Descriptions

8. DoDAF V 2.0 Delivery • DoDAF V2.0 is available at: • https://www.us.army.mil/suite/page/454707 • http://www.defenselink.mil/ • http://www.defenselink.mil/cio-nii/docs/DoDAF%20V2%20-%20Volume%201.pdf

9. http://www.defenselink.mil/cio-nii/sites/diea/ 10

10. Motivation US DoD and UK MOD interested in leveraging commercial standards for their Military Architecture Framework Military Architecture Framework Tool Interoperability Key Goal for DoD, MOD, NATO Formal MetaModel basis for the Military Architecture Framework Critical to Interoperability Objectives Proliferation of Military Architectural frameworks DoDAF, MODAF, DNDAF, NAF, AGATE, ADOAF, MDAF, etc. Architecture Exchange - Why

11. UPDM – Unified Profile for DoDAF/MODAF UPDM RFC Group Walt OkonMatthew Hause Adaptive Artisan Software ASMG BAE Systems DoD DND embeddedPlus Generic IBM Thales Lockheed Martin Co Mitre L3 Comms MOD NoMagic Raytheon Rolls Royce Sparx Systems VisumPoint Selex

12. Defense-Industry Challenge: Synchronization of DoDAF-UPDM Lifecycles 2. Industry Produces Develops Generic Modeling & Engineering Standards • Governments • Produce Baselines • Develop, Evolve & • Harmonize • Defense Enterprise • Architecture • Frameworks • For Acquisition RFC 3. Vendors Produce Product Versions Defense Domain Tools “Just-In-Time” Leverages Vendors Standards- Based Tools & Government Frameworks

13. Architecture Models + Data = Architectural Description Operational ModelExample • Things • Individuals • Types or classes of individuals or things Architecture Data + Metadata Architecture Models Architectural Description Fit-for-Purpose (FFP) Fit-for-Purpose describes an architecture that is appropriately focused and directly support customer needs or improve the overall process undergoing change. The models provide choices, based upon the decision-maker needs. 14

14. DoDAF V2.0 Focus Results: Better ANALYSIS and Decisions. Focus: architecture DATA, not Products DoDAF V2.0 provides overarching architecture concepts, guidance, best practices, and methods to enable and facilitate architecture development. 15

15. Improving DoD’s Architecture • Guidance • DoDAF v2.0 • Federated Architecture Strategy • Tools • DoD Architecture Registry System (DARS) • DoD IT Standards Registry (DISR) • GIG Technical Guidance (GTG) Tool • Education and Training • DoD Architecture Training Effort All this is nothing without Certified Architects!

16. Architecture Training DKO Site • URL - https://www.us.army.mil/suite/page/530507

17. DoD Architecture Education & Training • DoD must identify Architect’s opportunities for Education & Training • Identifies core KSAs Architects must have to be able to design, develop, and deliver DoD architectures that enable senior leader decision making and engineering design • Analyze and define the types of architecture training at different levels of architecture • DoD – IT Architects Career Path–Architects Series • Define a certification requirement and process

18. White Paper: Outline • Preface • Introduction • Purpose, Scope, and Approach • Findings • Recommended Way Ahead • The DoD Architect Competency Framework • A culmination of input gathered through research, interviews, and workshops on the standard knowledge, skills, and abilities DoD Architects should obtain at varying levels of maturity. https://www.us.army.mil/suite/doc/10757012

19. DOD Architect Levels Level 1 Development Primary function is to develop architectures based on user requirements and input from subject matter experts Level 2 Analysis Primary function is to analyze architectures for the purposes of integration, interoperability, gap analysis, risk assessment, leveragability, compliance, and business decision making Level 3Management Primary function is to lead and manage an architecture effort through its entire lifecycle, from development to execution/implementation White paper identifies the functions and associated KSAs for each level. These KSAs are independent of educational degree, working domain (contractor, civilian, military), or career title (GS level, rank, or role).

20. Roadmap to the Future • Deliver an IT EA Education & Training Strategic Plan • Deliver an architect careers plan • Establish architecture specialties in Office of Personnel Management (OPM) • Formalize a Architect’s Competency Framework • Implement certification across architecture specialties • Work with academic and educational institutions to enhance their curricula

21. Strategic Plan 2009Draft 1.7a DOD IT ENTERPRISE ARCHITECTURETRAINING & EDUCATION

22. DKO Site • URL - https://www.us.army.mil/suite/page/530507

23. Save the date! May 10-14, 2010 DoD Enterprise Architecture Conference 2010, San Antonio, TX