1 / 25

Principles of Quality Architecture and Moving Forward Towards a Unified Common Approach 5 January 2012 Walt Okon Seni

crete
Download Presentation

Principles of Quality Architecture and Moving Forward Towards a Unified Common Approach 5 January 2012 Walt Okon Seni

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. Principles of Quality Architecture and Moving Forward Towards a Unified Common Approach 5 January 2012 Walt Okon Senior Architect Engineer Architecture & Infrastructure Directorate (571) 372-4685 Walt.Okon@osd.mil UNCLASSIFIED 1

    2. Defense is our Mission Architecture; Then and Now

    3. Elements of Quality Architecture

    4. Single Architecture Framework 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.

    6. Policy, Direction, Guidance http://www.dodcio.defense.gov/sites/diea/

    7. Architecture Exchange UPDM – Unified Profile for DoDAF/MODAF UPDM RFC Group

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

    9. 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)

    10. DoDAF V 2.0 Delivery DoDAF V2.0 is available at: http://dodcio.defense.gov/sites/dodaf20/ 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.

    11. Architecture Education & Training

    12. Elements of Quality Architecture

    13. Office of Management and Budget Common Approach Federal Enterprise Architecture (CA-FEA) 05 January 2012

    14. UNCLASSIFIED 14

    15. 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

    16. 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

    17. 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

    18. 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.

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

    20. 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

    21. Context and Status 21

    22. Common Approach and FEA

    23. Methodology 23

    24. Reference Model Updates 24

    25. UNCLASSIFIED 25

More Related