## Review This is an incredible book that fundamentally changed my perspective on what [[Enterprise Architecture]] is. It introduces a lot of valuable concepts and is very self-consistent. Moreover, the use of graphics and tables to summarize and distill its points is phenomenal. This book is **not** without some gripes I have, both stylistically and with regard to content. It is wordy. It says many unnecessary things, and repeats itself a **lot**. It spends **a lot** of time simply categorizing things and has not convinced me in many cases that having categorical distinctions is actually *useful*. It's also pretty clear that the outline and framework for this book was conceived of, then not changed all that much to fit any form of narrative structure. Paragraphs are frequently numbered (i.e. a list of bullets that got blown out into paragraphs). Actually *reading* the text became a bit of a chore, despite how good the message *content* is. Also [[The CSVLOD Model Disregards the Value of Business-to-Business Alignment]], which I think is an oversight (although a fairly ineffectual one). I'd go so far as to say you could extend the CSVLOD model to include 3 new types for business-only related [[Enterprise Architecture Artifacts]], things like how a business process relates to another one - or rules for changing them. Whether or not this could be considered "[[Enterprise Architecture]]" is a **definitional** argument. [[Svyatoslav Kotusev]] says Enterprise Architecture is all about communication to ensure [[IT-Business Alignment]]. I think there's room to include the benefits of Business-Business alignment. It just so happens that making business-to-IT communication artifacts *also* typically helps different parts a of the business understand and communicate with one-another as well. ## Notes (see backlinks 👇) ---