1. How the CDC Enterprise Architecture Development Methodology Can Help You Albert Decker, Northrop Grumman John Fitzpatrick, CDC

2. Agenda  What is the Enterprise Architecture Development Method (ADM)? –Description –History –Purpose –Overview – Examples  How can this help you? –General benefits of EA –ADM Specific Standard set of artifacts/models Jump start your EA program/process

3. Description of the ADM  Phased approach to create an architecture segment – a subset of the entire enterprise  Standard set of artifacts, each having a template  Project plan template to guide you through the process  Guidance document to explain how to do each task in the project plan

4. History of the ADM  The ADM is based on best practices from a variety of sources –Health and Human Services Architecture Framework –Department of the Interior’s Methodology for Business Transformation –Department of Defense Architecture Framework –Federal Enterprise Architecture Framework –The Open Group Architecture Framework  The ADM is currently in Version 1 –Treat it as a Beta version

5. Purpose of the ADM  Have a consistent approach –Consistent tools and templates –Consistent analysis  Produce a standard set of artifacts/models –Similar products for as-is and to-be –Cover all layers of the architecture You can produce models at the level of detail that makes sense for your project  Be flexible enough to adapt to particular projects –If you adapt it, PLEASE do not leave out the stakeholder modeling, which is critical  Produce “actionable” architectural models –After completing the architecture you will have a plan for implementation

6. The ADM Overview  Initiation –Set Scope and Purpose of effort –Determine Stakeholders –Form Team  Baseline Analysis –Capture/Gather data for each layer of the architecture (layers on next slide) –Analyze baseline (preliminary)  Target Analysis –Interview Stakeholders –Define Vision, Goals and Objectives and align to larger Enterprise –Identify and define target states for Business, Data, Services, etc.  Transition Planning –Perform gap analysis between baseline and target –Create a plan to move from baseline to target  Transformation –Monitor the execution of the plan (typically through project reviews)  Compliance –Continued monitoring (typically annual review) for any performance issues, changed needs, etc.

7. The ADM and HHS Architecture Layers

8. ADM By Example : NCPHI Architecture Project 2007  The NCPHI Architecture project was initiated by Dr. Leslie Lenert following last year’s PHIN Conference  The project completed Phase 1 in December of 2007  Naturally, our first task was to tailor our collection of data to fit the needs and schedule of the project…

9. Initiation  Set Scope and Purpose of effort –The Executive Sponsor does this –Typical vehicle is a Project Charter While architects usually write the charter, the sponsor must always sign off on it –Scope of the NCPHI Architecture Project was 55 NCPHI systems and the processes and programs they support –Purpose was to document all systems and create a strategy for moving to an open source, collaborative environment –Scope was split into 6 segments  Determine Stakeholders –NCPHI Stakeholders were separated into 4 categories  Form Team –Team consisted of Architects, Project Managers, and subject matter experts for both systems and programs

10. Initiation  The scope and purpose were used to create a list of deliverables for the project.  Working back from that, a questionnaire was created and templates were tailored for the data collection effort –This complex questionnaire was sent as an Excel spreadsheet –It required a lot of explanation, so we wrote an FAQ  Focus was initially on information exchange –Experience shows this is a fruitful avenue to pursue

11. Phase One Target Architecture

12. Baseline Analysis  Capture/Gather data for each layer of the architecture –Distributed the questionnaire and instructions –Held initial meetings with system stewards –Made preliminary models –Reviewed models with system stewards –Finalized models  Analyze baseline (preliminary) –Identified some potential issues for move to open source

13. Target Analysis  Interview Stakeholders –System stewards were used as proxy to stakeholders NOT RECOMMENDED  Define Vision, Goals and Objectives and align to larger Enterprise –Fortunately, the target vision was very clear and well aligned to the broader Enterprise of CDC and HHS  Identify and define target states for Business, Data, Services, etc. –A target concept of operations was created

14. Transition Planning  Perform gap analysis between baseline and target –This is relatively easy in this case, as the legacy is nowhere near the target  Create a plan to move from baseline to target –Created a high level strategy for moving to the target –Recommended next steps in creating a lower level transition plan  This was the end of Phase 1

15. How this can Help You: General Benefits of EA  Establish clear links between mission and IT spending  Reduce redundancy –Reduces costs  Identify barriers to information flows, process bottlenecks, etc.  Ease transition to new technologies

16. ADM: Standard set of artifacts  Artifacts serve a purpose within the method –Deliverable –Analysis input –“Best practice” is not a reason!  Moves many decisions about what to produce to a program level –Reduces project complexity –Different projects produce similar models  Become well understood after just a few projects

17. Jump Start Your EA Program  Start with an existing method based in best practices –Documentation and templates allow for quicker ramp up  Try it one time before making any changes  Then decide what works for you

18. Questions