Presentation on theme: "Walt Okon Senior Architect Engineer"— Presentation transcript:
1DoD Enterprise Architecture & Standards The Future of Architecture 16 September 2009 Walt OkonSenior Architect EngineerSenior Architect Engineer for Information SharingEnterprise Architecture and Standards DirectorateDoD Chief Information Officer(703)
2DoD Agenda for OMGFuture of Architecture; Vision, Mission, Deliver0916 – 0945 DoD Organization, Governance, and Process0945 – 1010 Refreshment Break1010 – 1030 DoD IT Standards Program (DISR)1030 – 1050 DoDAF Version 2.01050 – 1110 DoD Information Enterprise Architecture v1.11110 – 1120 EA Federation1120 – 1130 Information Sharing Segment Architecture1130 – 1140 Break1140 – 1155 DoD Architecture Education & Training1155 – 1210 DoD Architecture Exchange – UPDM V2.0
3UPDM – Unified Profile for DoDAF/MODAF Unalienable Rights: Life, Liberty and pursuit of HappinessDefense Architecture Framework3
5DoD Architecture Federation Solution ArchitecturesDoD Enterprise ArchitectureTech StdsDISRArch GuidanceDoDAFRef ModelsDoD EA RMLaws, Regs, and PolicyLawsRegsPolicyToolsDITPRDARSForce ApplicationBuilding PartnershipsCommand & ControlProtectionLogisticsForce SupportCorporate Management & SupportNet-centricBattlespace AwarenessJoint Capability AreasInformation Enterprise ArchitectureDept of ArmyDept of NavyArmyArchitectureDONAir ForceSOCOMDISADLANSANRONGADIAOtherDept of Air Force55
6DoDAF V2.0 Viewpoints That Fit-the-Purpose RenamedNewNewNewOverarching aspects of architecture context that relate to all modelsAll ViewpointArticulate the data relationships and alignment structures in the architecture contentData and Information ViewpointArticulate applicable Operational, Business, Technical, and Industry policy, standards, guidance, constraints, and forecastsStandards ViewpointSystems ViewpointArticulate the legacy systems or independent systems, their composition, interconnectivity, and context providing for, or supporting, DoD functionsServices ViewpointArticulate the performers, activities, services, and their exchanges providing for, or supporting, DoD functionsOperational ViewpointArticulate operational scenarios, processes, activities & requirementsCapability ViewpointArticulate the capability requirement, delivery timing, and deployed capabilityDescribes the relationships between operational and capability requirements and the various projects being implemented; Details dependencies between capability management and the Defense Acquisition System process.Project ViewpointNewIn DODAF 2.0 we have described an expanded number of viewpoints (categories of models and views expressing differing aspects of a common architecture need) to include those shown on the slide. Some of the viewpoints were introduced in earlier versions of DoDAF, others, such as Project and Capability are new to DoDAF 2.0.An architecture viewpoint can be displayed in a number of formats, such as dashboards, fusion, textual, composite, or graphs, which represents data and the architecture description which represents an architecture. In DoDAF 2.0, the ability is provided to create an architectural description which can be expressed in many of the same formats normally used for briefing, analysis, and decision-making.The next few slides present a view of data from an architecture developed for the US Air Force at Arnold Engineering Development Center in Tennessee. This is the Air Force Center for R&D, testing and Analysis of aircraft, engines, and other components. Both Charles and I are using these views today with the permission of the Air Force.Architecture viewpoints are composed of data that has been organized to facilitate understanding.66
8“Fit for Purpose” DoDAF Architecture Descriptions
9DoDAF V 2.0 Delivery DoDAF V2.0 is available at: https://www.us.army.mil/suite/page/454707It is important to note at the outset that utilizing this methodology for your architecture effort is NOT mandatory. It has been provided in DoDAF 2.0 as a means for organizations to adopt a generic, easy-to-use method for creating an architectural description, and for new teams with little experience.If an organization prefers to use its own methods, then the generic methodology is there to compare to ensure that all the needed steps are contained in the methodology the organization prefers to use in its own efforts.There are six steps is the DoDAF methodology:1-Determine the intended use of the architecture2- Determine the scope of the architecture3- Determine data required to support architecture development4- Collect, organize, correlate and store data5- Conduct analysis in support of architecture objectives6- Document resultsManagers don’t do all of these steps. The first 2 (speak to) are the managers’ domain, as is Step 5. The rest are the domain of the architect and development team, with the manager acting as a subject-matter expert, where needed.
11Architecture Exchange - Why MotivationUS DoD and UK MOD interested in leveraging commercial standards for their Military Architecture FrameworkMilitary Architecture Framework Tool InteroperabilityKey Goal for DoD, MOD, NATOFormal MetaModel basis for the Military Architecture FrameworkCritical to Interoperability ObjectivesProliferation of Military Architectural frameworksDoDAF, MODAF, DNDAF, NAF, AGATE, ADOAF, MDAF, etc.
12UPDM – Unified Profile for DoDAF/MODAF Walt Okon Matthew HauseUPDM RFC GroupAdaptiveArtisan SoftwareASMGBAE SystemsDoDDNDembeddedPlusGenericIBMThalesLockheed Martin CoMitreL3 CommsMODNoMagicRaytheonRolls RoyceSparx SystemsVisumPointSelex12
14Architecture Models + Data = Architectural Description Operational Model ExampleThingsIndividualsTypes or classes of individuals or thingsThe framework enables architecture content to be built that is “Fit for Purpose”, defined and described in Volume 1 as architecture, which is consistent with specific project or mission objectives. Because architecture can be applied at myriad levels of an enterprise, the purpose or use of architecture at each level will be different in content, structure, and level of detail. Pulling everything together that we know about an architecture—the viewpoints, requirements, and expected outcomes, we have an architectural description.In order to ensure that architectural descriptions meet program and mission objectives, the approach to architecture development must be tailored to address a specific, well-articulated, and understood purpose. This will help to ensure that necessary data collection, to an appropriate level of detail, is undertaken, completed, and supportive of specific decisions or objectives.Architectural description: A collection of products to document an architecture. An architectural description generally contains one or more viewpoints to express the business, service, system and other elements of the overall project or program.Architecture: The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution.ArchitectureData + MetadataArchitectureModelsArchitectural DescriptionFit-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.1414
15DoDAF V2.0 FocusResults: Better ANALYSIS and Decisions.Focus: architecture DATA, not ProductsDoDAF 2.0 significantly refocuses the architectural concepts that have been in play for many years. First and foremost, the focus is on DATA, not architecture products. Data is needed for good analysis and better decisions. How these decisions are made within the culture of an organization should not artificially change just because we publish a Framework.Instead, this version discusses how to collect the data needed, validate that data, organize that data, and THEN form it into models, views, and viewpoints that graphically express the data. For those that have been happy with the older ‘DoDAF products’, please be assured that they are still being supported, along with many other views. The difference is that you can choose HOW to express your data in ways that better fit both your organizational preferences, and your specific project needs.DoDAF V2.0 provides overarching architecture concepts, guidance, best practices, and methods to enable and facilitate architecture development.1515
16Improving DoD’s Architecture GuidanceDoDAF v2.0Federated Architecture StrategyToolsDoD Architecture Registry System (DARS)DoD IT Standards Registry (DISR)GIG Technical Guidance (GTG) ToolEducation and TrainingDoD Architecture Training EffortAll this is nothing without Certified Architects!
17Architecture Training DKO Site URL - https://www.us.army.mil/suite/page/530507
18DoD Architecture Education & Training DoD must identify Architect’s opportunities for Education & TrainingIdentifies core KSAs Architects must have to be able to design, develop, and deliver DoD architectures that enable senior leader decision making and engineering designAnalyze and define the types of architecture training at different levels of architectureDoD – IT Architects Career Path–Architects SeriesDefine a certification requirement and process
19White Paper: Outline Preface Introduction Purpose, Scope, and Approach FindingsRecommended Way AheadThe DoD Architect Competency FrameworkA 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/
20DOD Architect Levels Level 1 Development Level 2 Analysis Primary function is to develop architectures based on user requirements and input from subject matter expertsLevel 2 AnalysisPrimary function is to analyze architectures for the purposes of integration, interoperability, gap analysis, risk assessment, leveragability, compliance, and business decision makingLevel 3 ManagementPrimary function is to lead and manage an architecture effort through its entire lifecycle, from development to execution/implementationWhite 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).
21Roadmap to the FutureDeliver an IT EA Education & Training Strategic PlanDeliver an architect careers planEstablish architecture specialties in Office of Personnel Management (OPM)Formalize a Architect’s Competency FrameworkImplement certification across architecture specialtiesWork with academic and educational institutions to enhance their curricula
22DOD IT ENTERPRISE ARCHITECTURE TRAINING & EDUCATION Strategic Plan 2009 Draft 1.7a