Enterprise Architecture Planning: Developing a Blueprint for Data, Applications, and Technology

by Steven H. Spewak, Steven C. Hill, Hill Steve

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 Here the authors give you a common-sense approach to Enterprise Architecture Planning . You'll find dozens of examples of architectures, procedures, checklists, and useful guidelines to support these techniques. This is the best guide available to help you ensure a cost-effective, long-term solution.

Genres: Business, Nonfiction, Architecture, Technology

392 pages, Paperback

First published October 1, 1992

Reviews

[Kian.ting · Rating 5 out of 5]

I know this book is old, many critics will say it is too wordy and all, but if you did the Togaf certification, you know about the business, data, and technology architecture. You were told what they are but was never really shown an example of how it looks like. This book gives you that example of how the design artifacts of that architecture look like and from those examples, you could get the gist and a better understanding of how the architectural artifact would/could look like. This book is also good for the aspiring Architect to know that there is also a human/political element in architectural consulting work and you really have to deal with it. The book gives you ways in which you could possibly deal with it, and hey Zachman wrote the forward to the book so how bad could it be? Just give it a go.

[بندر · Rating 5 out of 5]

i want read this book please
help me

[Bradley Woods]

boring as all hell

[João Dobbin · Rating 4 out of 5]

Amazing how a book from the 90's can still be so valuable today in a such fast paced field such as technology. It provides tons of value in its business modeling and frameworks, even with outdated terms (which made me laugh a few times, like UPGRADE YOUR MAINFRAME). I don't think the current startup ecosystem thinks of architecture enough and this knowledge became more restricted to larger companies, but this could prevent so many operational bottlenecks that makes me wonder why every single technology conpany does not apply concepts of architecture in its business.

[Adi Wibowo · Rating 4 out of 5]

This book provide pratical step-by-step procedures to conduct enterprise architecture planning. The procedure it self is prety much straight forward. This is actually a good and bad thing. The good thing is we can follow the steps and this book will act like a guidance. But sometimes, as TOGAF pointed out, the planning procedures or progress needs to be circular. In the real world sometimes we need to make a decision about some plan, without knowing all the necessary information. Like when we design architectures for some divisions, and then to expand it to cover larger area of organization. In this kind of need circular procedures, where revisions of former plan or diagram are allowed to be administered in the later steps, will work best.

[Spe · Rating 5 out of 5]

The best book ever written about Enterprise Architecture. Despite being written almost two decades ago, it's still the most relevant and practical guide to EA for visionary business leaders and CIOs.

[Steen Sørensen]

The missing link between Zachman and Weill ;-)

[Secretmissionforgoodyahoo.Com · Rating 5 out of 5]

i want to read this