How
to Survive in the Jungle of Enterprise Architecture
Framework: Creating or Choosing an Enterprise
Architecture Framework
Review
by
Mike
Tarrani "www.tarrani.com" (Deltona,
FL USA)
Amazon.com Readers Review ranking
Average Customer Rating:

Valuable
compendium
When
I received this book I quickly scanned it
and dismissed it as a niche book for architects
working in the US Government or contractors
working in that environment. After reading
it, though, I believe that this is an invaluable
book for enterprise architects in the commercial
sector as well.
For
those working in or with the US Government,
and especially the Department of Defense,
this books in-depth comparison of enterprise
architectures within that domain is an amazing
resource. Among the government- and DoD-specific
architectures covered are Federal Enterprise
Architecture Framework (FEAF) issued by the
CIO council, Command, Control, Communications,
Computer Intelligence, Surveillance, and Reconnaissance
(C4ISR) Architecture (a part of the Department
of Defense Architecture Framework (DODAF),
and Joint Technical Architecture. This book
also covers CCA architecture compliance. This
is an interesting part of the book because
lessons learned from CCA compliance requirements
may possibly translate into an approach for
aligning commercial architectures to Sarbanes-Oxley,
which is a hot topic in the commercial sector.
Enterprise
architectures in the commercial domain that
are covered include the Zachman Framework,
Enterprise Architecture Planning, The Open
Group Architecture Framework, and the Integrated
Architecture Framework. More importantly,
there are manufacturing-specific frameworks
covered, such as the Purdue Enterprise Reference
Architecture and the Computer Integrated Manufacturing
Open Systems Architecture, which round out
this books comprehensive survey of architectures.
The
manner in which the above architectures are
covered is what I most like about this book.
The author has performed the mind-numbing
task of collecting relevant factors of each
architecture, then presenting them in a set
format: history, purpose, scope, principles,
structure, guidance and compliance. This format
allows you to use this book as a catalog of
architectures, as well as the basis for comparing
the strengths and weaknesses of architectures
that are suitable for a specific environment.
I
also like the first eight chapters, and chapters
11 and 12, which provide general information
about enterprise architectures, definitions,
and advice on how to select the best architecture
based on requirements.
This
is an important book for enterprise architects
that will serve as an encyclopedia, idea book,
and general resource.
|