Principles of Quality Architecture and Moving Forward Towards a Unified Common Approach 5 January 2012 Walt Okon Senior Architect Engineer Architecture & Infrastructure Directorate (571) UNCLASSIFIED 1

Defense is our Mission Architecture; Then and Now Common Architecture Framework Unalienable Rights: Life, Liberty and pursuit of Happiness

Elements of Quality Architecture Common Architecture Framework Approach Single Architecture Framework Policy, Direction, Guidance Architecture Exchange Architecture Tools Certified Architects Enabling efficient and effective acquisition of hardware, software and services used by DoD in missions deliverables.

Single Architecture Framework Architecture viewpoints are composed of data that has been organized to facilitate understanding. 4 All Viewpoint Overarching aspects of architecture context that relate to all models Data and Information Viewpoint Articulate the data relationships and alignment structures in the architecture content Standards Viewpoint Articulate applicable Operational, Business, Technical, and Industry policy, standards, guidance, constraints, and forecasts Systems Viewpoint Articulate the legacy systems or independent systems, their composition, interconnectivity, and context providing for, or supporting, DoD functions Services Viewpoint Articulate the performers, activities, services, and their exchanges providing for, or supporting, DoD functions Operational Viewpoint Articulate operational scenarios, processes, activities & requirements Capability Viewpoint Articulate the capability requirement, delivery timing, and deployed capability 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.

DoDAF Version 2.0 Metamodel

Policy, Direction, Guidance 6

UPDM – Unified Profile for DoDAF/MODAF Architecture Exchange UPDM – Unified Profile for DoDAF/MODAF Adaptive Artisan Software ASMG BAE Systems DoDDNDembeddedPlusGenericIBMThales Lockheed Martin Co Mitre L3 Comms MODNoMagicRaytheon Rolls Royce Sparx Systems VisumPointSelex UPDM RFC Group Walt Okon DoD Support

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

Architecture Tools Guidance –DoDAF v2.0 –Federated Architecture Strategy DoD Tools –DoD Architecture Registry System (DARS) –DoD IT Standards Registry (DISR) –GIG Technical Guidance (GTG) Tool –Meta Data Repository (MDR) Vendor Tools are Necessary

DoDAF V 2.0 Delivery  DoDAF V2.0 is available at: 

Architecture Education & Training Defense Architecture Framework DoD Certified Architects delivering quality Architectures Certified Enterprise Architects design the information technology architecture structure enabling the efficient and effective acquisition of hardware, software and services utilized by the DoD in missions supporting the warfighters. Architect Career Plan Architect’s Competency Framework

Elements of Quality Architecture Common Architecture Framework Approach Single Architecture Framework Policy, Direction, Guidance Architecture Exchange Architecture Tools Certified Architects Enabling efficient and effective acquisition of hardware, software and services used by DoD in missions deliverables.

Office of Management and Budget Common Approach Federal Enterprise Architecture (CA-FEA) 05 January 2012 “Build to Share” Walt Okon Senior Architect Engineer Architecture & Infrastructure (703)

UNCLASSIFIED 14 Mr. Scott Bernard, Chief Architect at OMB Reorganization of the Architecture Infrastructure Committee (AIC) Unified Architecture Framework (DoDAF Version 2.0) with New FEA alignment is his focus Organizations both Federal and Industrial (IAC) will be able to contribute to the EA community. Architecture at Federal Level

Strategic Direction from Federal Chief Architect “The Federal Enterprise Architecture (EA) community is at a crossroad regarding the way that architects individually and collectively contribute to Administration and Agency initiatives”  Mission Statement. Federal enterprise architects provide leading-edge analysis and design services that align strategic priorities with mission capabilities and technology solutions.  Vision Statement. To be a trusted, knowledgeable resource that helps to accomplish mission goals, drive change, and optimize resources through proven enterprise architecture methods. 2

Objectives of CA-FEA  To Describe: “…the need for changes in purpose, direction, and goals [of the EA practice in government].”  To Identify: areas that need improvement with respect to deriving more value from the practice of EA by senior decision makers responsible for agency strategy  To Change: how Architects at all levels (Enterprise, Segment, Solution) provide a support to the “business” of government  To Improve the Practice of EA: through development of a “common approach” To support decision makers To improve interoperability across organizations To improve the quality of architectural solutions

New - Common Approach  Move EA from academic exercise to an applied management discipline  Focused on business performance  Integrates strategic, business, technology domains  Agile, scalable, and repeatable  Emphasizes the future, not the past  Part of TechStat reviews  Produces tangible, measurable results  Cloud-based shared service orientation

Common Approach  EA Program needs to be “in-place” before agility can be reached  Enhance awareness on expanding the use of EA to serve as a strategy and business tool  Recommend reference architecture, profiles, and standards to align the elements EA in a common way to insure cross-domain interoperability.  Describe the mature practice of EA profession through identifying requirements for education/training.  Identify the relevance of stakeholders, their requirements, and means to provide traceability to the EA.  Provide education and training to develop foundational architecture skills as well as those specific to support U.S. Government EA process requirements.

Common Approach  Common Approach” -- being more prescriptive will: –Reduce the variety and standardize a Federal EA framework and methodology: 1.Reduces the number of EA variations to be supported by Tool manufactures 2.Supports repeatable practice by architects and provide common education to grow new Federal Enterprise Architects 3.“Common Approach” will address EA development, methodology, and maintenance

Updated FEA Approach  More agile approach  Primary outcome objectives  Levels of scope  Agency EA program elements  Repeatable process for solution architecture  Core / elective models  Analysis guide

Context and Status 21

Common Approach and FEA Primary Outcome Levels of Scope Basic Elements Repeatable process Sub-Architecture Areas Core Artifacts

Methodology 23

Reference Model Updates 24 Business Reference Model (BRM) Intra- and inter-agency shared services Agencies, customers, partners, providers Infrastructure Reference Model (IRM) Hardware providing functionality Hosting, data centers, cloud, virtualization Application Reference Model (ARM) Business-focused data standardization Cross-agency information exchanges Performance Reference Model (PRM) Inputs, outputs, and outcomes Uniquely tailored performance indicators Security Reference Model (SRM) Data Reference Model (DRM) Software providing functionality Enterprise service bus

Questions UNCLASSIFIED 25