HYPERLINK \l “_Toc210268460” EA Presentation PAGEREF _Toc210268460 \h 9 HYPERLINK \l “_Toc210268461” Overview Document PAGEREF _Toc210268461 \h 9 HYPERLINK \l “_Toc210268462” Basics PAGEREF _Toc210268462 \h 10 HYPERLINK \l “_Toc210268463” Workshop Presentation PAGEREF _Toc210268463 \h 10 HYPERLINK \l “_Toc210268464” Simple EA Audit Matrix PAGEREF _Toc210268464 \h 10 HYPERLINK \l “_Toc210268465” Simple EA Policy Document PAGEREF _Toc210268465 \h 10 HYPERLINK \l “_Toc210268466” EA Planning Project Template PAGEREF _Toc210268466 \h 10 HYPERLINK \l “_Toc210268467” Defining Risks PAGEREF _Toc210268467 \h 10 HYPERLINK \l “_Toc210268468” Assessing Capabilities PAGEREF _Toc210268468 \h 10 HYPERLINK \l “_Toc210268469” EA Tutorial PAGEREF _Toc210268469 \h 11 HYPERLINK \l “_Toc210268470” ITIL Process Fact Sheets PAGEREF _Toc210268470 \h 11 HYPERLINK \L “_TOC210268471” 1.
H., Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology, John Wiley & Sons, 1992 PAGEREF _TOC210268471 \H 21 HYPERLINK \L “_TOC210268472” 2.
Zachman, J.A., A Framework for Information Systems Architecture, IBM Systems Journal, vol. 26, no. 3, pp. 276-292, 1987 PAGEREF _TOC210268472 \H 21 HYPERLINK \L “_TOC210268473” 3.
Sowa, J.F. & J.A.
Zachman, Extending and Formalizing the Framework for Information Systems Architecture, IBM Systems Journal, vol. 31, no. 3, pp. 590-616, 1992 PAGEREF _TOC210268473 \H 21 HYPERLINK \L “_TOC210268474” 4.
Burgess, B.H. & T.A.
Hokel, A Brief Introduction to the Zachman Framework, Framework Software Inc., 1994 PAGEREF _TOC210268474 \H 21 HYPERLINK \L “_TOC210268475” 5.
Building Enterprise Information Architectures: Reengineering Information Systems.
Prentice Hall, 1996 PAGEREF _TOC210268475 \H 21 HYPERLINK \L “_TOC210268476” 6.
Inmon, W.H, J.A.
Zachman, & J.G.
Geiger, Data Stores, Data Warehousing, and the Zachman Framework: Managing Enterprise Knowledge, McGraw-Hill, 1997 PAGEREF _TOC210268476 \H 21 HYPERLINK \L “_TOC210268477” 7.
Internet Reference: http://www.istis.unomaha.edu/isqa/vanvliet/arch/isa PAGEREF _TOC210268477 \H 21 HYPERLINK \L “_TOC210268478” Identify Enterprise Needs PAGEREF _TOC210268478 \H 27 HYPERLINK \L “_TOC210268479” Validate Needs and Measures PAGEREF _TOC210268479 \H 28 HYPERLINK \L “_TOC210268480” Resolve Data Conflicts PAGEREF _TOC210268480 \H 28 HYPERLINK \L “_TOC210268481” Build the Enterprise Architecture Model PAGEREF _TOC210268481 \H 29 HYPERLINK \L “_TOC210268482” 1.
Reverse Engineer Existing Environment PAGEREF _TOC210268482 \H 34 HYPERLINK \L “_TOC210268483” 2.
Map “As Is” Physical Model to “To Be” Logical Model PAGEREF _TOC210268483 \H 35 HYPERLINK \L “_TOC210268484” 3.
Analyze the Gap PAGEREF _TOC210268484 \H 35 HYPERLINK \L “_TOC210268485” 4.
Develop Transition Plan PAGEREF _TOC210268485 \H 35 — Be one step ahead by using this checklist.
People will be impressed that as well as knowing about EA you approach any initiative with a complete understanding of the risks involved. Assessing Capabilities One of the most important aspects in undertaking any major initiative is to understand who is involved and at what level. This is no different when looking at an EA initiative.
Use this spreadsheet to place you partners and suppliers at different levels of the EA framework.
This way you will get to see where the strengths and weaknesses are EA Tutorial A high quality Presentation that allows you to guide others through the details of Enterprise Architecture and the Zachman Framework. This clever presentation is a must see for those involved. ITIL Process Fact Sheets These are the most concise summary of each of the ITIL processes.
They enable you to understand the goal and basic activities of each of the processes. These documents should be the first thing you review to get a high level understanding of the ITIL processes. The Zachman Framework As a company tries to become better in the creation of information systems a regular discussion occurs about the need or value of an information architecture.
The success of an individual application is not dependent on having an information architecture, but the corporate goal of a seamless, integrated corporate information system requires corporate planning.
A major part of this planning may involve architecture.
This article reflects some of my initial thoughts on a long-term project that I have just started that deals with the Zachman Framework.
For information on the general issue of information architectures refer to references at the end of this article. The Zachman Framework basically deals with the common sense rules that we were given in middle school for writing a story.
We were told to provide information about Who, What, When, Where, Why, and How in every story.
This same common sense partitioning of knowledge occurs in the columns of the Zachman Framework.
I will not try to defend the Zachman Framework over other frameworks, but any framework that is adopted or developed should be easy to explain to management and the involved professionals. A standard presentation for the Zachman Framework is given in Figure 1.
The knowledge that defines an application can be partitioned within the Zachman Framework.
Each column has a need for a precise model that defines the knowledge associated with that aspect of the application.
A current effort exists to provide the meta-model for each column.
This effort would benefit from using the NLM/ORM/NIAM approach of examples and sentences to define these requirements.
The type of knowledge captured in individual cells will not be discussed in this article, but an overview of the columns and a discussion of the rows will be presented. PRIVATE DATA FUNCTION NETWORK
Read more about ITIL : HYPERLINK l _Toc210268460 EA Presentation PAGEREF _Toc210268460 h 9 HYPERLINK….: