I purchased this book with it was first published and it greatly influenced my thinking and has continued to do so to this day. There is a large caveat I want to share before continuing - be careful of the Zachman Framework because if you do base your enterprise architecture on it you will soon discover that making changes is a tedious process that ripples across the matrix. That said, I continue to believe in the basic concepts and components of the framework, and I also think that it is an excellent way to gain a view of an enterprise when you are attempting to model it.
Caveat aside, the techniques and many of the elements of the framework provided in this book are invaluable to creating any enterprise framework or initiating and managing a process improvement program. While Chapter 1 describes enterprise architecture planning in the context of the Zachman Framework, all of the subsequent chapters can be applied to any framework, which what makes this book as valuable today as it was a decade ago. Specifically, Chapter 3 (Planning), 5 (Enterprise Survey), 8 (Application Architecture), and 10 (Implementation Plan) are among the best of the best practices for approaching any project that is enterprise-wide in scope. For that reason I continue to keep my worn copy of this book nearby as a reference.
Despite my views on the Zachman Framework and some of its limitations and challenges, you may not have a choice - if you are on a team that is refactoring your enterprise in accordance with the Zachman Framework I recommend that you visit the Zachman Institute (see ASIN B00016NEXI) and augment the decade old material in this book with the up-to-date content available on that site.
If you are still in the exploratory stage and are considering this book because you want to learn more about either the Zachman Framework or EAP I recommend that you not only purchase this book (for the reasons cited above), but that you also read "How to Survive in the Jungle of Enterprise Architecture Framework: Creating or Choosing an Enterprise Architecture Framework" (ASIN 141201607X).
on January 12, 2004
I initially read this book at the start of my career as a systems analyst. The Zachman framework presented a great way to think about the relationships between systems, data, processes and business. Later on, as a project manager, it provided a more useful tool for understanding the importance of architecture in developing systems. In addition, it applies to architects and senior IT managers who want to make the most of their investment.
The writing displays the academic rigor of the author's background, as well as the applicability that comes from his wealth of experience. Perhaps this blend is best typified in the only application I've seen of reapplying (rewriting?) Deming's 14 points of management for an application in IT.
Perhaps what separates this book from most is how well it's held up over time. At 10 years old, it hasn't aged. If anything, in today's age of complexity, the relevance of a coherent understanding of architecture is more important than ever. This book will help you understand it.
on January 21, 2001
Other reviews of this book are valid in that Enterprise Architecture Planning is an invaluable resource for developing an enterprise-wide architecture. However, this excellent book is also an invaluable resource for the service delivery practitioner.
While the Zachman Framework is a recognized approach to enterprise architectures, it is also a excellent tool to anchor processes and procedures for delivering service and support for applications. The notion of application profiles are an excellent paradigm from which to develop problem management processes in support of enterprise applications.
Ideas and concepts set forth in the book are aimed at the enterprise architect, but can also be refactored into building blocks for a service delivery plan that is tightly integrated into applications delivery.
The above statement is based on my definitions, which are: service delivery is the set of processes that IT provides support for reliability, availability and infrastructure support that is aligned to business imperatives and requirements. Applications delivery is the processes employed to manage business requirements and translate them into products (developed or purchased).
This book provides a sound framework for achieving the above objectives, which I am sure were not the authors' primary intent. So, while this book provides the enterprise architect with a proven approach based on a proven framework, it has additional value. Specifically, it also provides the production services and operations functions within IT with a valid approach to integrating service delivery with applications delivery, and aligning them to business requirements.
on June 22, 2000
This is an excellent book. It presents a complete plan of how to implement a business oriented strategy planning program that will align IT with the strategies being pursued by your organization. This book does not provide all of the answers. It points out, correctly and in an easy-to-read format, that you, as an IT executive, must adapt the program presented here to your own situation.
However, the program outline is more extensive and more valuable than any I've seen before. It is also better than the program outline that I've personally seen delivered by top name consulting firms.
Coupling this book with practicle experience, and readings on both total quality management, and marketing will provide the budding planner with a successful intellectual tool set for creating an improved IT/Business alignment.
Dan Ashley, PhD firstname.lastname@example.org
on August 21, 1998
This is an excellent book outlining the process, content and pit-falls associated with EAP (a classic for consultants and professionals). It is important to remember that it presents a management framework not an implementation framework. I look forward to the next release -I hope it includes something on object modelling and UML and the need to differentiate between functional and competency based modelling (Business Architecture) when designing enterprise information systems for the future. This book is a foundation and a "must read" for any budding Enterprise Architect.