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. Elements of a straight-foward approach to Enterprise Architecture 2/15/2011 Christopher Geraghty Sr. Consultant, PSC Group, LLC cgeraghty@psclistens.com OR… Why do we need an EA perspective?

3. What EA Addresses

4. Role for Technology Change

6. Part I – Overview of EA Methods TOGAF Capability Framework TOGAF Business Capabilities Business vision and drivers TOGAF Enterprise Continuum and Tools

7. Part I – Overview of EA Methods TOGAF

8. Enterprise Architecture approach - TOGAF v9 There 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 TOGAF PART 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 architecture PART III (ADM Guidelines and Techniques) This part contains a collection of guidelines and techniques available for use in applying TOGAF and the TOGAF ADM PART 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 deliverables PART V (Enterprise Continuum & Tools) This part discusses appropriate taxonomies and tools to categorize and store the outputs of architecture activity within an enterprise PART 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 enterprise The 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 Methods Zachman

10. Part I – Overview of EA Methods Zachman

11. Part I – Overview of EA Methods There are six domains to the Zachman Framework: Data - What Function - How Network - Where People - Who Time - When Motivation - Why Zachman There are five roles mapped to the six domains in the Zachman Framework: Planner - Scope - Contextual Owner - Business Model - Conceptual Designer - System Model - Logical Builder - Technology Model - Physical Sub-Contractor - Detailed Representations – Out-of-context

12. Part I – Overview of EA Methods Zachman

13. Part I – Overview of EA Methods tmforum frameworks

14. Part I – Overview of EA Methods tmforum eTOM

15. Part I – Overview of EA Methods tmforum SID

17. Roadmap alignment

18. Standardization

20. Least COST

21. Grow Revenue

22. Contain costs

23. Outsource

24. Buy vs. Lease

26. guiding principles

27. technology usage and guidance

28. idea generation by usage and enablement

30. Who we are

31. What we do

32. Metric Scorecard and Breakout

33. Communication Plan

34. Appendix

35. Glossary

37. Define Guiding Principles

38. Pick most important area of Technology

39. Pick most important Business Requirements

41. Collaboration

42. Discussion

43. Vendor mtgs

44. Industry mtgs

45. Trends

46. Emerging Technology

47. Use Case application

48. Positions

49. Viewpoints

50. Strategy Development

51. Roadmap Development

53. Coordination

54. Project Initiation

55. Approvals

56. Socialization

57. Education

59. Monitoring

60. Metric Review

62. # Visits with industry

63. # Stakeholder mtgs

64. # conferences attended

65. # exec briefings

66. # exec teleconferences

67. # trainings attended

68. # strategies developed

69. # roadmaps developed

70. # solution designs

71. # reference architectures

72. # transition architectures

73. # future architectures

74. # standards monitored

75. # processes identified

76. # kpi’s monitored

77. Performance increase

78. Performance decrease

79. # days request turnaround

80. # standards approved

81. # mtgs facilitated

82. # PIPs

83. # education sessions

84. # architecture reviews

86. # trends identified

88. # position papers

89. # viewpoint papers

90. # emerging technologies identified Metrics

91. Enterprise Architecture - References TOGAF: http://www.opengroup.org/togaf/ http://www.opengroup.org/architecture/togaf8-doc/arch/chap39.html http://www.opengroup.org/architecture/togaf9-doc/arch/ ZACHMAN: http://www.businessrulesgroup.org/BRWG_RFI/ZachmanBookRFIextract.pdf TMFORUM: http://www.tmforum.org/ EAEC – Enterprise Architecture Executive Council: https://www.eaec.executiveboard.com/Public/Default.aspx

93. Data Mining and Business Intelligence

94. Compliance and Security