Customer Reviews

Guide to Enterprise IT Architecture

5 star:		(3)
4 star:		(1)
3 star:		(0)
2 star:		(1)
1 star:		(0)

 

 

This book describes the Open Group's Architecture Framework, which is a structured approach to developing an architecture based on a sequence of steps outlined in their architecture development method.

The book sets the context for architecture in general in the first three chapters, covering an introduction to technical architectures in general, addressing specific issues related to architecture with respect to business alignment, technologies, cost factors, etc.; and delving into the business foundation that [should] drive the architecture.

Subsequent chapters cover each step in the architecture development method in detail. Specific steps are:
Phase A: Architecture Vision: Define scope; create vision; obtain approvals
Phase B: Business Architecture: Develop a Business Architecture
Phase C: Information System Architectures: Develop Data and Applications Architectures
Phase D: Technology Architecture: Develop a Technology Architecture
Phase E: Opportunities and Solutions: Checkpoint suitability for implementation
Phase F: Migration Planning: Prioritize work; Select major work packages; Develop migration plan Phase G: Implementation Governance: Provide architectural oversight of the implementation
Phase H: Architecture Change Management: Establish procedures for managing change to new architecture

Although this book covers an approach to architecture that is not mainstream, it is viable and well developed. I especially like the clearly articulated description and detail, which are reinforced with illustrations that bring the text to life. Moreover, the authors pay attention to all life cycle factors, particularly maintenance and post implementation support. Additional information about the Open Group Architecture Framework can be found on the sponsoring web site (ASIN B00006G0R7).

This book is, in my opinion, a secondary text on architectures and more suited to seasoned system and technical architects who are seeking to expand their knowledge of architecture methods. The approach set forth can be applied to the development and implementation of any architecture, making this book an asset to the discipline's body of knowledge.

I'm an engineer, not a literature major, so I've learned to plow through dense text to find the important facts and features of subjects that are useful in my job. This book and the architecture methodology it describes is rich in detail and based on sound principles.

Every major best practice in architecture is included: structure, discreet layering, separation of concerns, technical accuracy, and business focus. The company I word for uses the 4+1 architecture methodology, which is not far off from the methodology given in this book. I've found a lot of ideas in this book that I can use on the job without violating our comoany standards, and I am sure that as time goes on I'll discover more because I refer to this book a lot.

If you want to complain about writing I recommend changing careers to something more suitable like writing novels. If you want to keep current in architecture and best practices read this book.

While this book is written around the TOGAF, its impact is wide ranging. I read this book together with HANDBOOK OF ENTERPRISE ARCHITECTURE by Bernus et. al. Both form great text books for Graduate Level courses aimed at practitioners rather than theoreticians. Go for it, its steep price is justified...

This tome (scholarly book) may have a great purport (purpose), but the message is hidden in the sempiternity (endless amount)of $5 words. In fact, after reading this book, I feel like I've mastered a study in Roget.

It seems obvious to me the authors had their thesauraus wide open while writing this book, and only for the purpose of impressing us with their vast command of the English language. The author also continually speaks in parantheses (meaning, he slices a sentence in two, therefore distracting the reader from the original intent). Sarcasm intended.

In summary, find a book that is readable. This one isn't.

This book contains a wealth of information on EA. However it is based on an older version of TOGAF. But one is able to relate the information to more recent version of TOGAF, so I can still recommend this book for anyone who wants to go more in depth on TOGAF.