An Introduction to Enterprise Architecture

by Scott A. Bernard

An Introduction to Enterprise Architecture is the culmination of several decades of experience that I have gained through work initially as an information technology manager and then as a consultant to executives in the public and private sectors. I wrote this book for three major reasons: (1) to help move business and technology planning from a systems and process-level view to a more strategy-driven enterprise-level view, (2) to promote and explain the emerging profession of EA, and (3) to provide the first textbook on the subject of EA, which is suitable for graduate and undergraduate levels of study. To date, other books on EA have been practitioner books not specifically oriented toward a student who may be learning the subject with little to no previous exposure. Therefore, this book contains references to related academic research and industry best practices, as well as my own observations about potential future practices and the direction of this emerging profession.

Genres: Business, Technology, Technical, Architecture

340 pages, Paperback

First published September 1, 2005

Reviews

[Denis Romanovsky]

This is a standard for enterprise architecture, so the book is quite boring. For sure, it should be. At the same time it explains well what enterprise architecture is, shows structure and contents, some usable case studies are there, explains why this thing is needed in an enterprise and how much effort should be spent on it. So, not bad, but boring.

[Anjar Priandoyo]

"EA is one of the three most powerful governance processes that a CXO has to use in implementing change (the others are strategic planning and capital planning)"

This is one of the most important quotes in this book. EA is something strategic, and something strategic is always about a change. This book mention that EA basically just a continuation of QA in 1980s. EA is something that a information dependent company need to strugle now. This book mention that Enterprise Architecture is a complement of System Analyst concept, Strategic Planning and Service Oriented Architecture.

The weakness of this book is and old book (2005), is not based on TOGAF -although explain in the appendix. However in total this is a good book, especially the case study that the author describe in the beginning and used through the book.

Basically all frameworks and concept is the same, this include Enterprise Architecture. For example, it is the same with PMBOK which consist of process, domain (knowledge area, technique), deliverables (input output), tools, management (capability).

[David Carpinteiro]

This book provides an overview of what is Enterprise Architecture and also the future of it. It also presents in detail EA3 as a framework for Enterprise architecture with a step by step guide on how to use it.
This is the second book i read on EA and felt again the same, the book says an introduction, but again felt that without a proper knowledge of the topic, the book becomes in some parts dificult to read and understand.
But in sum, it is a good book on the subject, the framework itself appears to be quite usefull but it could have a little more examples.

[Mike]

Read for an EA course. From a strict academic stance, it covered EA frameworks well. However, there is a significant gap between digging into frameworks and artifacts vs connecting EA to the real world.

If you are an inspiring EA, this book will provide you with EA qualifications, but leave you scratching your head not really knowing what an EA does.

[Girish Pathria]

Deals with the process rather than real-world examples. Just when one thinks it will dive into the reality of visualizing a future architecture scenario with reasoning and example, it falls flat, moves on and starts listing artifacts.

[Conrad]

A solid introduction to Enterprise Architecture for any budding basket weaver. Bernard improves on the Zachman framework by adding another EA layer to different strategy from core business processes.

[Andrew]

Excellent book that gives foundational concepts of EA!

[Nishad Sanzagiri]

Overall, the book is a good reference guide to understanding Enterprise Architecture, but what made the reading experience a bit annoying was the fact that it was filled with numerous typos — a bad job from the copy editor.

[Rune Pedersen]

A rich book of enlightenment. A tough son of a bitch. An overall introduction to Enterprise Architecture and its many facets. Read it if you must. Read it if you want to gain a wide perspective on the architecture of enterprises.

[Dharwiyanti]

Read it for (surprisingly) Organization Management class. Normative and lack of best practices.

[Steen Sørensen]

A very good tool box for the process of engaging in enterprise architecture

[Sami Albanna]

Useful.

[Emil O. W. Kirkegaard]

Very abstract. Almost no examples, and the one running example is made up. Full of fluffy marketing/business language. No empirical evidence. Not recommended.

[Jumled Leon]

A must-read book

This is a first-step book for someone looking for EA plan. Concepts are easy to understand and you ended with a clear idea about how to design a EA plan.

[Raghav Mehta]

1234