• Bing® is a registered trademark of Microsoft Corporation.
• All other brands, company, and product names are used for
identification purposes only and may be trademarks that are the sole
property of their respective owners.
The Practice of Enterprise Architecture:
A Modern Approach to Business and IT Alignment (2nd Edition)
• ebooks.com, amazon.com
• ISBN (Kindle): 978-0-6450825-0-0
• ISBN (ePub): 978-0-6450825-1-7
• ISBN (Paperback): 978-0-6450825-2-4
• ISBN (Hardcover): 978-0-6450825-3-1
• Second Edition: 15-Jan-2021
• 570 pages
Svyatoslav Kotusev (Slava)
Source: Author Official Website
LinkedIn Profile: Enterprise Architecture Researcher
A book based on a thesis
What to expect if you are reading a book based on the thesis of PhD in enterprise architecture?
A book based on a PhD thesis in enterprise architecture is likely
to be a detailed and comprehensive study of a specific area of
enterprise architecture. The book will likely be written in a
formal style, with a clear focus on the research problem under
investigation, precise word choice, and a cohesive and logically
organized flow of ideas.
The book may also include an overview of the author’s
research methodology, as well as an analysis of their findings
Practical & Realistic
Based on empirical studies
Lots of references
The CSVLOD model of Enterprise Architecture
Rules Structures Changes
What Artifacts Describe?
Considerations Visions Outlines
Standards Landscapes Designs
What did I like in the 2nd Edition?(1/3)
• Clarity of being able to communicate a complex topic as Enterprise Architecture
in a simple way.
• Diagrams are monochrome art pieces (Simple notation, Informative,
• Lots of references (606). I found lots of them are very interesting, and have so
much information, and provide both quantitative & qualitative evidence about a
• Always updated (WIP): EA Artifacts increased from 24 (1.x) to 28 (2.0), you can
follow the author on LinkedIn to keep up to date with any other announcements.
• Author is like a fortune teller In several situations, I found examples mentioned
in the book as if the author is a fortune teller who knows what is happening in
your organization within specific projects and he is telling you how this can be
What did I like in the 2nd Edition?(2/3)
• Realistic, practical, & based on empirical studies rather than Theoretical. Full
details of the studies, and findings can be found in “Enterprise Architecture and
Enterprise Architecture Artifacts: Questioning the Old Concept in Light of New
Findings”. “Table 1. Description of the identified EA artifacts including their
contents, usage and purpose”. Pages 107 – 109.
• Chapter 5: Due to problems with business strategy as the basis for architectural
planning, the author promoted a middle ground between business & IT to use:
1. Operating Model.
2. Business capabilities.
3. Specific business needs.
4. Business Processes.
5. Business requirements.
What did I like in the 2nd Edition?(3/3)
• Promote the concept of “There is no-one-size-fits-all”. Examples from chapter 17
“Architecture Functions in Organizations”, you will find many alternatives for the
1. Figure 17.2: The dependence of the structure on the size of an organization.
2. Figure 17.3: The dependence of the structure on the degree of decentralization.
3. Figure 17.9: The structure of Governance committees in different organizations.
What I would like to see in next edition?
• Simpler English, the words are carefully picked but are hard and require a translator for a
non-native English speaker.
• 2nd edition preface to use fewer confrontational messages with criticism.
• If the book can have a simple business case from end to end, where various artifacts can
be represented in more detail, it will be great. Or, it can be provided as an accompanied
online resource (To keep the book-length reasonable).
• Chapter 13: The Interaction between EA processes with other processes/frameworks
(PMO, Portfolio, Demand, Procurement, SDLC, Audit, Data Governance, ...), I hope they
can be converted into a graphical representation.
• Chapter 14: I think the artifact "Key Design Decisions (KDDs)" needs to be added although
they are classified as less popular. As the term "ADR (Architecture Decision Register)” is
becoming very popular and promoted by different architects worldwide.
• Add an appendix having a comparison between CSVLOD and other well-known EA
frameworks similar to the BCS article “A comparison of the top four enterprise
• Target Audience: Enterprise Architect.
• Anyone establishing EA practice to start with the pieces of advice mentioned in
“Chapter 19: The Lifecycle of Enterprise Architecture Practice”.
• If you are already practicing EA, reading this book will give you multiple ideas to
resolve daily issues you are facing.
• IMHO, after reading chapter 3, read Appendix A, then proceed to chapter 4.
There are important conclusions that are worth reading at the end of this
Ch 1 Ch 2 Ch 3 Ch 4 Ch 5 Ch 19 Appendix
 Exploring the roles of different artefacts in enterprise architecture practice, Svyatoslav Kotusev,
 BCS EASG Webinar - A fresh look at Enterprise Architecture Artifacts (Old but comprehensive),
Svyatoslav Kotusev, 15-Dec-2017
 Syvatoslav Kotusev- BCS Enterprise Architecture Conference 2019 - Presentation (New, brief but
sound is not that clear), Svyatoslav Kotusev, 2-Aug-2019
 Enterprise Architecture Management (In German), Till Albert, 17-Feb-2022
 A comparison of the top four enterprise architecture frameworks, Svyatoslav Kotusev, 1-Jul-2021.