

Desertcart purchases this item on your behalf and handles shipping, customs, and support to South Africa.
Enterprise architecture (EA) is a set of descriptions relevant to both business and IT intended to bridge the communication gap between business and IT stakeholders in organizations, facilitate information systems planning and improve business and IT alignment. Due to complex historical reasons, the notion of enterprise architecture was always surrounded by endless speculations, dangerous myths, non-existing best practices, unfulfilled promises, expensive failures and grave disappointments. Traditionally the entire discourse around enterprise architecture was dominated by shallow advice and faddish approaches (e.g. well-known EA frameworks) infinitely distant from the practical realities, but nonetheless aggressively promoted by commercially motivated consultancies and gurus. At the same time, realistic and trustworthy information on enterprise architecture is still incredibly hard to find in any available sources. Based on an extensive study of the actual industry best practices and existing EA literature, this book provides a unique, systematic, end-to-end description of various aspects of an EA practice integrated into a consistent logical picture. In particular, this book offers clear, research-based, conceptually sound and practically actionable answers to the key questions related to enterprise architecture: What is the meaning of enterprise architecture and an EA practice? What processes constitute established EA practices and how do they work? What EA artifacts are used in successful EA practices and how? What is the best way to structure architecture roles and functions? What software tools and modeling languages are necessary for enterprise architecture? How to initiate an EA practice in organizations from scratch and evolve it? Where do current EA best practices originate from? This book is organized in a highly structured, sequential manner and does not require any prior knowledge of enterprise architecture. The book is intended for a broad audience of people interested in enterprise architecture including practicing and aspiring architects, architecture managers, academic EA researchers, EA lecturers and students in universities. Review: It is a good read about the reality of EA - It's a thorough examination of EA Review: Forget TOGAF, read this instead - I work for a reasonably large listed company (3000 people) and even for an organisation that size, TOGAF is a totally impractical behemoth to implement. This book is the who, what, when, where, why and how of enterprise architecture. Every word is about the most direct way to deliver value as a practicing enterprise or senior solutions architect. Amazing stuff.
| Best Sellers Rank | #167,861 in Books ( See Top 100 in Books ) #151 in Computer Hardware & DIY #946 in Computer Science #5,307 in Business Management & Leadership |
| Customer Reviews | 4.5 out of 5 stars 89 Reviews |
A**R
It is a good read about the reality of EA
It's a thorough examination of EA
M**E
Forget TOGAF, read this instead
I work for a reasonably large listed company (3000 people) and even for an organisation that size, TOGAF is a totally impractical behemoth to implement. This book is the who, what, when, where, why and how of enterprise architecture. Every word is about the most direct way to deliver value as a practicing enterprise or senior solutions architect. Amazing stuff.
A**L
Great book for EA
Good book!
S**C
Good book for both Enterprise Architecure rookies and experts
This book is an overlooked gem. As first, while still being a software developer, from at least 2014 I have more and more projects that are increasingly being developed as integrated solutions connected with preexisting software and hardware infrastructure (as opposed from building everything from the scratch as a closed monolith). So, more and more I have to consider information systems development from the broader perspective of Enterprise Architecture (EA), and more and more I'm shifting from programmer to information systems designer, and from information systems designer to enterprise architect. That being said, I've found concepts in this book: 1. Much more being real-life alike (for those concepts I use in my proto-EA practice), and 2. Much more applicable to real-life EA practice (for those concepts I don't use yet, but considering to use in future practice). Book is nicely written, in plain English, with somewhat generalized, but mostly quite adequate examples of described concepts. It is actually interesting to read and enlightening, unlike some, say, learning materials for some, say, EA frameworks. (And yes, I did surmount those materials, and acquired the appropriate official certification, so I'm not talking out of some kind of envy :-) Author does not reinvent the wheel, and does not imagine himself as the Origin of all Truths, but talks about using existing tools, concepts and standards in EA practice, from plain old office apps to BPMN and such, properly placing all those tools, concepts, and standards into his CSVLOD taxonomy of EA artifacts development. (So not like, say, authors of certain software design methods who are probably still thinking that nothing has ever existed for software design before them, and that all software design is object-oriented and, preferably, in some C++ alike language such as Java or C#.) The biggest complaint about the book are a little bit too generalized examples of quite important and frequent EA artifact: Business Capability Model. "Capability 1", "Capability 2", etc. That part of book really needs extension focusing on more "down to Earth" examples. Mr. Kotusev is somewhat controversial for his stance regarding popular EA frameworks, also expressed in this book. While much of his stance has a strong rationale, also explained in this book, I still think that *some* structured approach to EA is still better that *no* approach at all. That being said, this book does not describe some overarching methodology, such as TOGAF's ADM. Indeed, author argues that all such methodologies can only be ineffective. Instead, he concentrates on: 1. Development of useful EA artifacts (categorized according to before mentioned CSVLOD taxonomy) and 2. Then using those artifacts in proper ways. So, good book for EA rookies and experts.
J**S
Very useful book
A comprehensive approach to EA. Very useful.
Trustpilot
1 month ago
1 month ago