Presentation Unified Architecture Framework and Methodology Key Component to Interoperability 13 November 2014 Walt Okon Professor Information Technology Science Technology and Business Division ID: 1045528
Download Presentation The PPT/PDF document "Object Management Group" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1. Object Management GroupPresentationUnified Architecture Framework and MethodologyKey Component to Interoperability13 November 2014Walt OkonProfessor, Information TechnologyScience, Technology, and Business DivisionNorthern Virginia Community College-NOVAAlexandria Campus, Virginiawokon@nvcc.eduwalt.okon@verizon.netPhone: 703-644-6257Cell: 571-488-5173
2. Through Constructive Collaboration DoD Architecture Framework will Deliver Interoperability for Shared Systems and ServicesPremise
3. The US Government has not defined or mandated a Architecture Framework and Methodology to achieve Interoperability for Shared Systems and ServicesProblem Statement
4. Chief Engineers, Chief Architects, and systems designers and developers agree an Architecture Framework is essential to achieving integration and interoperability across systems and services for the US Government. A single Architecture Framework will enable designers and developers to build in integration and interoperability. DoD Architecture Framework (DoDAF) is the widely used engineering centric framework and it is being used through the world in centers of excellence. Four other architecture frameworks are on the market causing confusion, frustration, and increased cost expenditures. Today's Environment
5. DoD’s DoDAF Direction
6. Why and When: Historical Development of AF’s.C4ISRArchitecture Framework v1.0C4ISRArchitecture Framework v2.0DoDAFv1.0MODAFv1.01996199720032005DoDAFv1.52007MODAFv1.12007NAFv1.02005Scope of UPDM 1.0Approved Sept 2008MODAF Meta-Model (M3) expressed using UML NotationMODAFv1.22008NAFv3.12007DoDAFV2.020092008Scope of UPDM 2.0ETC June 2011DNDAFv1.8UAFv1.02015?DoDAFV2.022012
7. 7Overall architecture framework convergence visionDoDAFv1.51995C4ISR F/W v1.0DoDAFv2.0UAFv2.0520032007JCIDS & NR-KPPApplicability beyond C4ISRUse-basedIntegrated Architecture2009201020122014DoDAFv2.01v2.02DoDAFv2.03DoDAF/DNDAFv2.04199720162013Joint InteroperabilityDoDAF v1.0C4ISR F/W v2.0Net-centricity and SoASvcV views26 AV/OV/SV/TV viewsLinked to I&S policiesCADM 2.0Fit-for-purposeData-centric architectureImproved models of systems, services, capabilities, rules, measuresDoDAF Meta Model (DM2) based on IDEASUrgent CRs52 1 XSDIDEAS Foundation v1.0 fixesUrgent CRsTECHEDITSDM2 OWLFederal Common ApproachDNDAF Security ViewsMODEM – DM2 Harmonization (IDEAS Domain Level)NATO NAFUDAFStandardization, e.g., ISOOMGOASISUAFFramework Objective: Achieve a single integrated Architecture Framework for interoperability. Achieve a US, Canada, and United Kingdom single Framework with a common Data Meta Model Achieve alignment with the US Government Common Approach to Enterprise Architecture Unified Direction of USG and NATOAchieving Strategic Goals and Capability
8. US Government OMB DirectionFEAF-II
9. Dr Scott BernardFederal Chief Enterprise ArchitectOMB Lead for IT Shared Services Executive Office of the PresidentOffice of Management and BudgetU.S. Federal Enterprise ArchitectureCommodity IT ServicesHosting (Networks, Systems, Apps)Help Desks / Fusion CentersE-Mail Collaboration SolutionsMobile SolutionsWebsites & Content ManagementData WarehousesInventory ManagementAccount ManagementContracting and AcquisitionPrint ManagementCommon Approach to Federal Enterprise ArchitectureUsing EA to Design Future-Ready AgenciesFEA II and DoDAF 2.02 Merge
10. Office Of Management and BudgetDraft Laws–Executive OrdersControls Budget/FundingOffice of the Federal CIOFederal Chief ArchitectArchitecture required-money/budget
11. Changes in ApproachCommon Approach to Federal EAFEAF-IIBriefed by Dr. Bernard
12. OMB Desired DeliveryIT Reform AgendaShared Services StrategyCloud Computing StrategyCommon Approach to Federal EAIaaSPaaSSaaSLight AppsSecurityCloud Computing Reference Architecture (NIST)Shared Services / Cloud SolutionsFEAF-II / FEAv2DODAFv2.0Other EAPolicyApproachDeliveryData Center ConsolidationShared Service/Cloud Computing Implementation ArchitectureBriefed by Dr. Bernard
13. DesignArtifact Set8 Perspectives /52 Elective)Analysis(A-11 Exhibit 53 & 300)Reference Models(CRM - PRM, BRM, DRM, ARM, IRM, SRM)DesignArtifact Set6 Domains with 6 Required, and 42 Elective artifactsAnalysis(A-11/Exhibit 53 & 300)Reference Models(CRM - PRM, BRM, DRM, ARM, IRM, SRM)Annual Enterprise Roadmap(High Level Agency-Wide Current EA Project & Program Summary / 3-Yr Future Summary / Transition Plan) Annual EA Program Assessment(EA Program Maturity / EA Project Value)Common Approach to Federal Enterprise Architecture (FEA)Approach 1 - FEAF v2.0Approach 2 - DODAF v2.02Agency EA Repository / InventoryDOD EA Repository / InventorySolution Architecture ProjectsCollaborative Planning Method - CPM (5 Phases)Solutions Architecture Projects DODAF Method (6 Phases)Annual Agency IRM Strategic Plan (per A-130) EA ReportingFederal-Wide Reference Architectures / StandardsU.S. Federal Enterprise ArchitectureEA ActivitiesOther Governance AreasBriefed by Dr. Bernard
14. DoDAF will be foundational and enhanced DoDAF will contain DNDAF Security Views/ModelsDoDAF and MODAF will be HarmonizedUAF will be capability focusedDoDAF/UAF will become an international Standard (ISO/OMG)DoDAF DM2 and MODEM will be HarmonizedUnified Architecture Framework DoDAF Sunsets and Unified Architecture Framework Emerges
15. 15Common Approach To Federal Enterprise Architecture
16. Future First“Future First” aligns with the Common Approach to Federal Enterprise Architecture and brings together the areas of design, analysis, projects, standards, reporting and governance.This provides “Full SpectrumE-Governance”.1May 2, 2012
17. Current Engagements:OMGPM-ISEACT-IAC P&A SIGFederal Chief ArchitectConstructive Collaboration
18. Current Engagements:OMGConstructive Collaboration DoD CIO Representative –Len LevineOMG Representative –Richard Soley, Victor Harrison Sr. Vice PresidentModelDriven –Cory CasanaveOMG UPDM Design Team – Matthew Hause
19. Solutions5Standards Organizations32aServices and Support4Com-munity of Interest 1Com-munity of Interest 2Com-munity of Interest 3Com-munity of Interest 4Com-munity of Interest “n”Com-munity of Interest “n” + “m”Com-munity of Interest 5Information Sharing CommunityCom-munity of Interest 6Stakeholders1aU.S. Government AgenciesState, and Tribal AgenciesInternational AgenciesAcademic InstitutionsCommercial OMGOASISW3COthersRequirements Pluggable--Taxonomies, Vocabulary mappings, and context ontologiesProtocolsSecurity PoliciesData Connectors & Mappings Late binding, injection, loose coupled, ChoreographyLeadershipSteering CommitteeCoordination and PrioritizationTestbeds and outcomesFunding and MembershipReference ImplementationsSpecifications of usageTestbedsTrainingStandardsSuppliers1bCommercialGovernmentalIndividualDeliver Productized Approve on behalf of the ISC the publication ofBasis for definingCollaborative Delivery ofNeeds and opportunitiesCoordination of DirectionOpportunities and CapabilitiesFunding and membershipFundingProductization and DeliveryNeedsParticipationCapabilities2bProductizationPrinciplesSpecificationsCONOPS
20. Current Engagements:PM-ISEConstructive Collaboration PM-ISE – Kshemendra Paul, Program ManagerPamela Wise-Martinez Vijay MehraRalph E CorbittAshwini JarralMark E. Reichardt
21. August 12, 2014Using Information Sharing Environment Interoperability Framework (I2F)Making Interoperability Common with Enterprise ArchitectureThe Office of the Program Manager for Information Sharing Environment
22. Increase Information/ Intelligence Sharing Reduce Total Cost of Operations Shared ServicesDesiredOutcomesPriorityObjectivesNationalStrategy2012GovernmentAuthoritiesStakeholderInputs Interoperability Safeguarding Search & Discovery Access & Retrieval Dissemination Defense Law Enforcement Foreign Affairs Homeland Security Intelligence Interoperability Requirements Operational Capabilities Exchange Patterns Technical Capabilities Technical Standards Reference Models Exchange Specifications Technical SpecificationsFEAFDoDAFPAGEnablesConstraints/Environment Federal SLT Private Int’lStakeholdersCommunitiesTOGAFGRAArchitecture FrameworksCaptured In
23. Getting on the Same Page (Definitions)What is Information Interoperability? The ability to transfer and use information in a uniform and efficient manner across multiple organizations and information technology systems Australian Information Interoperability Framework (2006)In other wordsIt’s the ability of two or more systems or components to exchange information and to use the information that has been exchanged
24. PM-ISE mission established in EO1356, EO1388 details the strengthening for information sharing. PM-ISE initiatives are reinforce on standards, interoperability, and architecture etc… DODAF have been huge undertaking but or not directive within whole of government, the need for a unified architecture approach would go far in solving interoperability. Federal Enterprise Architecture Common Approach, lots of goodness, links some DODAF artifacts, but not Directive/Policy FEAF – Policy is in the Agency Requirements to Deliver Transition Roadmaps each April. Supportive, but does not achieve the goals of A119 Under the OMG process the UPDM is a normative specification for modeling DODAF - Supports A119 “use of consensus based standards” I2F provides definitions, and guidance for implementation, but is not PolicyCollaboration Agreements
25. I2F supports Architecture Framework Interoperability via the Architecture Grid Alignment tools, and builds common practices for Interoperable Architecture Design Need practical next steps to achieve Framework Interoperability? Architecture Frameworks alone do not achieve interoperability Federal Workgroup maybe the best approach to achieve Framework Interoperability Standards Coordination Council has ownership of the I2F to operationalize whitespace and other activities, but are not on hook to improve architecture efforts or other nascent thoughts hereCollaboration Agreements
26. Develop a Constructive Collaboration Team to deliver Unified Architecture Framework and Methodology mandated by US Government Policy will result in Interoperability for Shared Systems and ServicesSolution Direction
27. Current Engagements:ACT-IAC P&A SIGConstructive Collaboration
28. 1. A member of the Constructive Collaboration Team to deliver Unified Architecture Framework and Methodology.2. Develop a ACT-IAC position paper that would endorse a need for a US Government Policy using Unified Architecture Framework and Methodology to enable Interoperability for Shared Systems and Services.3. Support other organization (OMG, PM-ISE, OMB) promulgating Unified Architecture Framework and Methodology.P&A SIG Support Actions
29. Who are the Players? Government: Federal CIO and Federal Chief Architect Department CIOs and Chief Architects Industry: ACT- IAC - IAC Planning and Architecture SIG NDIA Academia: National Defense University Penn State University - FEPO George Mason University NOVA International Standards Organizations OMG – UPDM OASIS
30. Walt OkonAir Force OfficerCC, Eng, ATC, ComputersCiv –DISAStratPlans, Eng, System EngCiv - DoD CIODoDAF, DARS, StandardsRetiredAdjunct Professor Vision and Objective Deliver Interoperability for Shared Systems and Services Constructive Facilitation resulting in Collaboration Guide and enable Government, Industry, and Academia