Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology (Computer Science) Paperback – 29 Oct 1993
|New from||Used from|
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Frequently Bought Together
Customers Who Bought This Item Also Bought
Enter your mobile number below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
From the Back Cover
About This Book Praise for Enterprise Architecture Planning " the book has given me a wealth of good, fresh ideas about every facet of the architecture process makes a substantive contribution to the body of IS planning knowledge." John A. Zachman Zachman Information Systems Enterprise Architecture Planning is more advanced than traditional system planning approaches because you:
- define a stable business model independent of organizational boundaries, systems, and procedures,
- define data before application, and
- let data determine the sequence for implementing applications systems.
About the Author
Steven H. Spewak, Ph.D., and Steven C. Hill Industry veteran Steven H. Spewak, Ph.D., is Chief Architect for DHL Systems Inc. Steve Hill is a Product Manager for Logic Works in Princeton, NJ. They can be reached on CompuServe at 71521,1052 and 70262,1135, respectively.
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
Most Helpful Customer Reviews on Amazon.com (beta)
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).
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
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.
The book addresses the most difficult aspects of EAP--how to handle the political hurdles and human issues that can stop an EAP project dead in its tracks. In doing so, the author demonstrates keen insight and experience with technology projects in business. It's not just about those aspects, but they are included for the benefit of anyone going through an EAP process.
The book takes the logical approach of starting with the definition of the business according to its functions (business value chain), moving next to the high-level, conceptual definition of the data that is required by the business. It then uses that data model to define (not design) the conceptual application architecture and then, in turn, the conceptual technology architecture. There is a clear distinction between the conceptual architectures and the more concrete designs that occur at the lower levels of the Zachman Framework. The author makes a convincing argument that this high-level definition needs to be created before the lower-level designs or the efforts will fail to produce the desired results. Samples of reports, such as a Business Model and a Data Architecture report, are provided in the appendix. I highly recommend this book.
Look for similar items by category
- Books > Business, Finance & Law > Management > Management Skills > Communication & Presentation
- Books > Business, Finance & Law > Management > Management Skills > Decision Making
- Books > Computing & Internet > Databases > Data Storage & Management > Database Management Systems
- Books > Computing & Internet > Digital Lifestyle > Online Shopping > Amazon
- Books > Computing & Internet > Hardware