1 / 23

DoD Architecture Information Sharing Across The Gaps Prepared for AFEI Inter-agency and Cross-Domain Information Shar

amal
Download Presentation

DoD Architecture Information Sharing Across The Gaps Prepared for AFEI Inter-agency and Cross-Domain Information Shar

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. DoD Architecture Information Sharing Across The Gaps Prepared for AFEI “Inter-agency and Cross-Domain Information Sharing” 16 September 2010 Walt Okon Senior Architect Engineer Architecture & Infrastructure Directorate (703) 607-0502 Walt.Okon@osd.mil

    2. Defense is our Mission Architecture; Then and Now

    3. 3 DoD CIO Governance Environment Need to decide responsibility for each of these processes across the IC. Communicate and resource accordinglyNeed to decide responsibility for each of these processes across the IC. Communicate and resource accordingly

    4. 4 CIO Governance Framework

    5. 5 ASRG Organizational Structure

    8. DoD Architecture Federation

    9. DoDAF V2.0 Viewpoints Fit-the Purpose In 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. In 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.

    11. “Fit for Purpose” DoDAF Architecture Descriptions

    12. 12 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 It 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 architecture 2- Determine the scope of the architecture 3- Determine data required to support architecture development 4- Collect, organize, correlate and store data 5- Conduct analysis in support of architecture objectives 6- Document results Managers 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.It 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 architecture 2- Determine the scope of the architecture 3- Determine data required to support architecture development 4- Collect, organize, correlate and store data 5- Conduct analysis in support of architecture objectives 6- Document results Managers 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.

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

    14. Requirement US DoD and UK MOD leverage commercial standards for Military Architecture Framework Defense IT Architecture Framework Tool Interoperability Key Goal for DoD, MOD, NATO Formal MetaModel basis for the Defense Architecture Framework Critical to Interoperability Objectives Proliferation of Military Architectural Frameworks DoDAF, MODAF, DNDAF, NAF, AGATE, ADOAF, MDAF, etc.

    15. UPDM – Unified Profile for DoDAF/MODAF UPDM RFC Group

    16. Defense-Industry Challenge: Synchronization of DoDAF-UPDM Lifecycles

    17. DoDAF V2.0 Focus & Capability DoDAF 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 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.

    18. 18 Improving DoD’s Architecture Guidance GIGv2.0, DoDAF v2.0, DM2, DoD IEA, Federated Architecture Strategy Tools DoD Architecture Registry System (DARS) DoD IT Standards Registry (DISR) GIG Technical Guidance (GTG) Tool Meta Data Repository (MDR) Architecture Education and Training/Implementation DoD Architecture Training Effort

    19. Architecture Education & Training

    21. 21 Roadmap to the Future Common Architecture Framework (DoDAF with New FEA) Tool Vendor Partnership with Interexchange Alignment of academic and educational institutions Architecture specialty in Office of Personnel Management Implement certification across architecture specialties

    22. 22 UNCLASSIFIED

More Related