This document outlines an approach to enterprise architecture using TOGAF. It discusses the key parts of TOGAF including the Architecture Development Method, guidelines and techniques, architecture content framework, and enterprise continuum. It also briefly covers the Zachman framework and TMForum frameworks. Practical tips provided include picking an approach, defining guiding principles, prioritizing the most important technology areas and business requirements, and common processes for architecture work. The document concludes with references to resources on TOGAF, Zachman, and TMForum.

1. Elementsof a straight-foward approachtoEnterprise Architecture2/15/2011Christopher GeraghtySr. Consultant, PSC Group, LLCcgeraghty@psclistens.comOR… Why do we need an EA perspective?

2. AgendaPART IOverview of EA Methods

3. What EA Addresses

4. Role for Technology Change

5. Role for Business ChangePART IIPractical Tips and TechniquesPART IIIInteractive Group DiscussionPart I – Overview of EA MethodsZachmanTOGAFeTOMSIDTMForum Frameworks/eTOM/SID/NGOSS

6. Part I – Overview of EA MethodsTOGAF Capability FrameworkTOGAFBusiness CapabilitiesBusiness vision and driversTOGAF Enterprise Continuum and Tools

7. Part I – Overview of EA MethodsTOGAF

8. Enterprise Architecture approach - TOGAF v9There are seven main parts to the TOGAF document:PART I (Introduction) This part provides a high-level introduction to the key concepts of enterprise architecture and in particular the TOGAF approach. It contains the definitions of terms used throughout TOGAF and release notes detailing the changes between this version and the previous version of TOGAFPART II (Architecture Development Method) This part is the core of TOGAF. It describes the TOGAF Architecture Development Method (ADM) - a step-by-step approach to developing an enterprise architecturePART III (ADM Guidelines and Techniques) This part contains a collection of guidelines and techniques available for use in applying TOGAF and the TOGAF ADMPART IV (Architecture Content Framework) This part describes the TOGAF content framework, including a structured metamodel for architectural artifacts, the use of re-usable architecture building blocks, and an overview of typical architecture deliverablesPART V (Enterprise Continuum & Tools) This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprisePART VI (TOGAF Reference Models) This part provides a selection of architectural reference models, which includes the TOGAF Foundation Architecture, and the Integrated Information Infrastructure Reference Model (III-RM)PART VII (Architecture Capability Framework) This part discusses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture function within an enterpriseThe intention of dividing the TOGAF specification into these independent parts is to allow for different areas of specialization to be considered in detail and potentially addressed in isolation. Although all parts work together as a whole, it is also feasible to select particular parts for adoption whilst excluding others. For example, an organization may wish to adopt the ADM process, but elect not to use any of the materials relating to architecture capability.

9. Part I – Overview of EA MethodsZachman

10. Part I – Overview of EA MethodsZachman

11. Part I – Overview of EA MethodsThere are six domains to the Zachman Framework:Data - WhatFunction - HowNetwork - WherePeople - WhoTime - WhenMotivation - WhyZachmanThere are five roles mapped to the six domains in the Zachman Framework:Planner - Scope - ContextualOwner - Business Model - ConceptualDesigner - System Model - LogicalBuilder - Technology Model - PhysicalSub-Contractor - Detailed Representations – Out-of-context

12. Part I – Overview of EA MethodsZachman

13. Part I – Overview of EA Methodstmforumframeworks

14. Part I – Overview of EA MethodstmforumeTOM

15. Part I – Overview of EA MethodstmforumSID

16. Part I – What EA AddressesTechnology and Business Strategy

17. Roadmap alignment

18. Standardization

19. Future-proofingPart I – Role for Technology ChangeIT analyzes and recommends best solutions based on business needsROI

20. Least COST

21. Grow Revenue

22. Contain costs