Enterprise Architecture Using the Zachman Framework [With CDROM]

by Carol O'Rourke, Neal Fishman, Warren Selkow

Book Overview

Introduces the concept of Enterprise Architecture, using the Framework developed by John Zachman, to business and MIS students and professionals. This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 0619064463
• ISBN13: 9780619064464
• Release Date: April 2003
• Publisher: Course Technology
• Length: 716 Pages
• Weight: 2.85 lbs.
• Dimensions: 1.6" x 7.4" x 9.3"

Customer Reviews

Excellent book; approach Zachman Framework w/caution

This is more of a "What" than a "How" book, and it does clearly [if somewhat verbosely] describe the Zachman Framework. It also provides implementation advice (the "How"), but that information is not as clearly laid out as it is in "Enterprise Architecture Planning" (ISBN 0471599859). I like this book because it is business-focused, and painstakingly describes the Zachman Framework and how it clearly provides a multidimensional view of business-technology alignment. It also reflects the latest thinking with respect to the framework, including Zachman DNA (Depth iNtegrating Architecture), which is missing from "Enterprise Architecture Planning" I cited above. It also contains some unique perspectives that I haven't found in other books, such as how to use the framework outside of IT (Appendix C), and how to map careers to the framework (Appendix D). What is missing from this book, and others like it, is a disclosure of the dark side of the framework if an organization fully commits to it. One such problem is once you've mapped your enterprise architecture to the Zachman Framework's matrix, a change in any cell will cause a ripple effect throughout the matrix. As time goes on this effect becomes a barrier to changes or requires high maintenance to keep the architecture in synch with the business and technology components. This does not diminish the value of the Zachman Framework as a way to view the enterprise, but should forewarn you that implementing it as a principle methodology is a step that should be carefully considered before committing. That said, this book is one I would highly recommend to anyone who is considering the Zachman Framework, or who is seeking an approach to clearly viewing an enterprise from multiple dimensions in order to cut through complexity and see the big picture. I also recommend that you visit the Zachman Institute (see ASIN B00016NEXI) to see the latest work and additional information.

A good introduction

I have just finished reading this book, after starting it back in May, 2003. I found the book to be just what my team needed. The fast path was useful, but I think the overall length of the book is excessive. However, its content overrides the length.My role as systems analyst in a mid-sized metal fabrication plant requires me to make many decisions that a lot of people don't understand, let alone agree with, because most people in my organization are only looking at and focusing on their own individual area. I would imagine that is a common occurrence in many organizations. Case studies in this book have helped my team begin to understand the concepts of enterprise architecture and its importance. I highly recommend this book to teams that are trying to create an architecture for their organization that aligns IT with business requirements.What some of this book's previous reviewers seem to gloss over is the fact that the Zachman Framework is about communication. This book tells how to think about a problem using a classification schema. This book clearly explains ways to communicate with others who are viewing a problem in a different way-hence the framework's six rows labeled planner, owner designer, builder, subcontractor, and functioning enterprise. The different viewpoints are represented in succession in Chapters 2 - 7. The three people on my team have been able to use some of the examples in this book to helpour organization learn how to understand other department's ways of looking at a problem. The authors explain that rudimentary steps to thinking, encouraged by enterprise architecture, begins with a list.This book explains how questions like `what is the difference between employees and people' can be answered by viewing the question from the six perspectives and asking the six questions listed across the top of the columns. I have heard John Zachman explain the answer to that identical question at a seminar. The book addresses governance within an organization, a timely topic considering accountability in strained economic times, andincludes many case studies that show how to measure to see if standards and guidelines are being met. The book explains how current issues such as governance are addressed by asking the six questions in the framework-what, how, where, who, when and why--thus simplifying the communication process and enabling the organization to come up with a common focus or goal. Iwould also recommend this book to managers who need help in classifying things within their problem domain because it shows the reader how to view the organization more broadly.

Grateful to have a book, not just journal articles

I have been learning about the Zachman Framework for several years through seminars and journal articles. This book pulls all the important concepts together for management and serves as a good reference to introduce individuals who are new to the topic.Spewak's and Cooke's books address John Zachman's framework, but this book covers all cells. I would highly recommend this book to anyone who needs to create buy-in for their division because the book shows how walking through the framework one cell at a time creates value for the organization. Another added bonus is that a cd with an introduction to John Zachman's book is included.

Business Knowledge Manager

For four years I have been fighting an up hill battle to get my senior management to understand the need for a good knowledge management system. The Executives have all the standard answers about why we can't do it. The CEO could see no immediate payback.I read the book, was taken completely by surprise by its content and depth. I managed to get the CEO to commit to read just the first three chapters. He read the whole book, in four days.I have been given a fairly liberal budget to put the Framework in place. This is amazing in the health care industry.What the book accomplishes, in great depth and much proof, is why enterprise architecture has become a matter of corporate survival. The author uses the lessons of history to make the points and further emphasizes how we see major corporations present themselves through the eyes of the framework.An must read for you and your bosses to make the case for enterprise architecture.

Thoughts from a business analyst

Finally the topic of enterprise architecture is addressed in a way that is easy to understand. This book is easy to read. It's a lengthy book, maybe too lengthy, but a path in the table of contents gets you through the 'meat'of the book quicker. The questions at the end of the chapters help you think about what you just read. For those of you familiar with other enterprise architecture books like Melissa Cook and Steven Spewak, you will find that this book covers all 36 cells, not just parts of it. The framework presented is meticulously explained and described toward the end of the book. The commonplace case studies throughout the book show you how to reduce complexity by sharing information in a very methodical manner, piece by piece. The author clearly emphasizes how to document this communication by creating models for each cell of the framework. The last chapter in the book actually shows you examples of ways to implement.You'll recognize everyday occurrences of just trying to get the work done. Other books have sections containing information about the Zachman framework, but this is the only one I've seen that is totally based on it. It's a good read and well worth your time if you are interested in architecture and you want to get started somewhere. If only they'd taught this stuff when I was in school.