Getting Started with Enterprise Architecture A Practical and Pragmatic Approach to Learning the Basics of Enterprise… (Eric Jager) (z-library.sk, 1lib.sk, z-lib.sk)

Getting Started with Enterprise Architecture A Practical and Pragmatic Approach to Learning the Basics of Enterprise Architecture Eric Jager Foreword by Whynde Kuehn

Getting Started with Enterprise Architecture: A Practical and Pragmatic Approach to Learning the Basics of Enterprise Architecture ISBN-13 (pbk): 978-1-4842-9857-2 ISBN-13 (electronic): 978-1-4842-9858-9 https://doi.org/10.1007/978-1-4842-9858-9 Copyright © 2023 by Eric Jager This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made. The publisher makes no warranty, express or implied, with respect to the material contained herein. Managing Director, Apress Media LLC: Welmoed Spahr Acquisitions Editor: Aditee Mirashi Development Editor: James Markham Editorial Assistant: Jessica Vakili Cover designed by eStudioCalamar Cover image designed by Eric Jager Distributed to the book trade worldwide by Springer Science+Business Media New York, 1 New York Plaza, Suite 4600, New York, NY 10004-1562, USA. Phone 1-800-SPRINGER, fax (201) 348-4505, e-mail orders-ny@springer-sbm.com, or visit www.springeronline.com. Apress Media, LLC is a California LLC and the sole member (owner) is Springer Science + Business Media Finance Inc (SSBM Finance Inc). SSBM Finance Inc is a Delaware corporation. For information on translations, please e-mail booktranslations@springernature.com; for reprint, paperback, or audio rights, please e-mail bookpermissions@springernature.com. Apress titles may be purchased in bulk for academic, corporate, or promotional use. eBook versions and licenses are also available for most titles. For more information, reference our Print and eBook Bulk Sales web page at http://www.apress.com/bulk-sales. Any source code or other supplementary material referenced by the author in this book is available to readers on GitHub. For more detailed information, please visit https://www.apress. com/gp/services/source-code. Paper in this product is recyclable Eric Jager Almere, Flevoland, The Netherlands

iii Table of Contents About the Author ��������������������������������������������������������������������������������vii About the Reviewer �����������������������������������������������������������������������������ix Acknowledgments �������������������������������������������������������������������������������xi Foreword �������������������������������������������������������������������������������������������xiii Chapter 1: Introduction�������������������������������������������������������������������������1 Chapter 2: Architecture Origin ��������������������������������������������������������������5 2.1. Timeline..........................................................................................................5 2.2. Zachman Framework .....................................................................................9 2.3. The Open Group Architecture Framework (TOGAF) ......................................11 2.3.1. Fundamental Content ..........................................................................13 2.3.2. Series Guides.......................................................................................19 2.4. Similarities and Differences .........................................................................20 2.5. Summary......................................................................................................21 Chapter 3: Architecture Definition ������������������������������������������������������23 3.1. Defining Enterprise Architecture ..................................................................23 3.2. Summary......................................................................................................26 Chapter 4: Architecture Domains �������������������������������������������������������27 4.1. Domains and Layers ....................................................................................27 4.2. The Information Domain ...............................................................................30 4.3. Multi-domain Model .....................................................................................31 4.4. Summary......................................................................................................33

iv Chapter 5: Architecture Roles�������������������������������������������������������������35 5.1. Defining Roles and Functions ......................................................................35 5.2. Generic Roles ...............................................................................................36 5.3. Variety in Functions ......................................................................................38 5.4. The Enterprise Architect ...............................................................................42 5.5. Summary......................................................................................................45 Chapter 6: Architecture Visualization �������������������������������������������������47 6.1. Language to Visualize ..................................................................................47 6.2. Modeling Language ......................................................................................48 6.2.1. Architecture Elements .........................................................................52 6.3. Catalogs, Matrices, and Diagrams ...............................................................63 6.4. The Right Toolset ..........................................................................................66 6.4.1. Architecture Repository .......................................................................71 6.5. Summary......................................................................................................75 Chapter 7: Architecture Positioning ���������������������������������������������������77 7.1. Earning Stripes ............................................................................................77 7.2. Architecture Purpose....................................................................................78 7.3. Summary......................................................................................................82 Chapter 8: Architecture Implementation ��������������������������������������������83 8.1. Implementation Wheel .................................................................................83 8.2. Document .....................................................................................................89 8.2.1. Information ..........................................................................................90 8.2.2. Stakeholders .....................................................................................132 8.3. Define .........................................................................................................144 8.3.1. Maturity .............................................................................................145 8.3.2. Framework ........................................................................................160 8.3.3. Strategy .............................................................................................178 Table of ConTenTs

v 8.4. Execute ......................................................................................................201 8.4.1. Strategy .............................................................................................202 8.4.2. Roadmap ...........................................................................................210 8.5. Control........................................................................................................218 8.5.1. Measure Progress .............................................................................219 8.6. Summary....................................................................................................228 Chapter 9: Next Steps �����������������������������������������������������������������������229 9.1. The Next Level ............................................................................................229 9.2. Summary....................................................................................................232 Chapter 10: Architecture Application �����������������������������������������������233 10.1. Lemon-A-de .............................................................................................233 10.2. Developing Lemon-A-de’s Architecture ...................................................240 10.3. A Few Years Later ....................................................................................246 10.4. Summary..................................................................................................246 Chapter 11: Closing Remarks �����������������������������������������������������������247 Appendix A: Example Information Map ��������������������������������������������249 Appendix B: Example Maturity Model ����������������������������������������������255 Appendix C: Example Work Package View ���������������������������������������261 References ����������������������������������������������������������������������������������������263 Index �������������������������������������������������������������������������������������������������267 Table of ConTenTs

vii About the Author Eric Jager is a Certified Master Architect in the field of Enterprise Architecture. He is also a certified TOGAF Enterprise Architecture Practitioner, Certified Business Architect, and ArchiMate Practitioner. He is familiar with various architecture methodologies including, for example, the TOGAF Standard and the Zachman Framework. The inspiration for this book came from Eric’s work experience in organizations with regulatory functions in both the financial and healthcare industries, commercial service providers, and several hospitals. There, he noticed that organizations continued to struggle with properly implementing architectural thinking and working with architecture. Eric set out to create an easy-to-understand and easy-to-implement architecture methodology. Using a self-created Enterprise Architecture Implementation Wheel, he developed an approach to implementing Enterprise Architecture that can be used by both novice and experienced architects. Eric has been practicing Enterprise Architecture for over 15 years and has extensive knowledge and experience in the development and application of Enterprise Architecture. He easily leverages architecture to translate business strategy into implementation. Eric likes to focus on the practical and pragmatic application of Enterprise Architecture and lectures on Enterprise Architecture at the Eindhoven University of Technology. He also writes about his daily experiences in his blog: eawheel.com/blog.

ix About the Reviewer Rob Malschaert is an experienced Enterprise Architect, primarily working in the healthcare sector as an independent Enterprise Architect. Rob is certified in TOGAF and ArchiMate and is also a Certified Information Systems Security Professional (CISSP). Rob has extensive experience in the practical application of Enterprise Architecture in complex organizations, especially in integrating working under architecture in organizations that are inexperienced in using architecture as a tool to achieve organizational objectives. Additionally, Rob actively contributes to the development of the Dutch Hospital Reference Architecture (ZiRA) and provides postgraduate-level education on Enterprise Architecture at the Eindhoven University of Technology.

xi Acknowledgments First and foremost, I would like to thank my current and former employers for providing me with invaluable work environments and lecture opportunities that inspired me to write this book. The variety of situations there allowed me to envision and create an adapted architecture methodology that is illustrated in this book. Special thanks go to Rob Malschaert, a former colleague of mine and my current partner in lecturing in the field of architecture at the Eindhoven University of Technology, for agreeing to be the reviewer for this book. His keen insight and attention to detail were essential in ensuring that the material is presented clearly. I am also grateful for the support and advice of Whynde Kuehn, author of Strategy to Reality. Whynde also took the trouble to write the foreword for this book. My thanks also go to the staff at Apress Media, who guided a first- time author through the writing and editing process with good-natured professionalism. I would also like to thank Aditee Mirashi (Acquisitions Editor) for accepting my manuscript submission and going out of her way to answer all of my numerous questions prior to the publishing process. Finally, I would like to thank my wife, Nienke, whose trust and support made this book possible.

xiii Foreword Is there anything more powerful than an idea? An idea is the kernel of all possibilities, with unlimited potential to change the world. Indeed, ideas have shaped all of our human history. We are all familiar with the philosophical thought experiment: If a tree falls in a forest and no one is around to hear it, does it make a sound? Here’s another one: If an organization formulates the most brilliant strategy for competitive advantage but it never gets implemented, does it matter? Or even: If we develop the most brilliant framework to help organizations work more effectively but if they don’t know how to apply it in practice, does it make an impact? What is more powerful than an idea then is an idea that is executed. That is what this book is all about. To survive and thrive, organizations must do change well in a world of increasing disruption and uncertainty. This applies to organizations of every size, industry, and sector – from Fortune Global 500 companies and governments to startups and non-profit organizations. Surprisingly though, organizations around the world continually struggle to execute strategies and business change in an effective, coordinated way at pace, and the statistics and stories abound that reflect this. This is where Enterprise Architecture comes in. After giving a pertinent and insightful history of Enterprise Architecture, Eric brings us to where the discipline has evolved today. As he states, “Enterprise Architecture has evolved from a primarily IT-focused discipline to a strategic and business-centric practice.” We’ve come a long way, and the holistic view of Enterprise Architecture has never been more important than it is today.

xiv Enterprise Architecture is a framework for understanding and managing the overall structure and strategy of an organization. This framework helps us design our organizations with intent for effectiveness, agility, and value as well as navigate complexity and inform business decision-making. Enterprise Architecture is also the often-missing bridge between strategy and execution. It plays a critical role in translating strategy into a coordinated set of actions that enables an organization to achieve its goals and objectives – and ensures the continual alignment of initiatives and investments back to business direction. Enterprise Architecture guides us to do the right things, at the right time, for the right reasons. The intentional, agile design of an organization and its ability to execute strategy together create the ability to respond to change. Enterprise Architecture is critical to both. This means that organizations must do Enterprise Architecture well. This book is a reference and a guide for your journey of implementing Enterprise Architecture. While Enterprise Architecture frameworks define what to do, they do not necessarily tell you how to do it. This book helps to bridge that gap. Through his depth of experience, Eric translates the theory of Enterprise Architecture frameworks into a practical set of steps and guidance, codified through his Implementation Wheel and demonstrated through an example company. This book accelerates you so that you can focus on doing what matters most: applying Enterprise Architecture within your organization to achieve the value for which it was intended. Eric walks you through the process of implementing Enterprise Architecture with such specificity, care, and passion that it is like having your own personal guide. He unpacks the practical details you need to know to build out different aspects of Enterprise Architecture, including how to collaborate with others and facilitate effective conversations. He helps you adapt the sequence and approaches to your realities, gives expert tips, steers you around potential challenges, and shows you the foreword

xv way with an extensive set of examples and blueprints. He even tells stories along the way to entertain and educate. Implementing Enterprise Architecture is a continual journey for every organization. The architecture itself is ever evolving and expanding with the business, but as the discipline is leveraged, it also shifts mindsets. Enterprise Architecture facilitates new ways of thinking and working around how organizations provide value, deliver strategic change, make decisions for the enterprise, and design for today and a future-ready tomorrow. Architecture and architectural thinking are beneficial for everyone, not just architects. With some courage, patience, skill, and an expert guide to keep you on solid footing, a rewarding journey lies ahead. Whether you are experienced in Enterprise Architecture or new to the discipline, your next step to greater meaning and impact for your organization or career is contained here in these pages. Open your mind to all that Enterprise Architecture has become and can be as a strategic discipline critical to helping our organizations and societies meet their challenges and opportunities ahead with success. All the best to you on the journey! Whynde Kuehn Author of Strategy to Reality Founder and Managing Director S2E Transformation Inc. foreword

1 CHAPTER 1 Introduction I have been practicing Enterprise Architecture for over 15 years. During these years I have worked for several organizations. All of these organizations presented unique situations, each requiring a slightly different way of working. The organizations did have one thing in common: architecture maturity was either non-existent or at a low level. One of the main reasons for this is probably (because we never really know for sure) the difficulty an organization has in translating the available theoretical architecture frameworks into a practical application. Despite the good intentions of frameworks such as the TOGAF Standard [1], there still are a lot of organizations that have not yet been able to translate a framework into something that is usable. If an organization could easily use the tools provided by a framework, working with architecture would be more likely to get the attention it needs. An organization would be able to greatly benefit from the structure and coherence that a framework has to offer. In spite of the fact that the theory described in the frameworks has evolved and matured over the years, organizations have not yet found a way to put it to good use. I believe this is because theoretical frameworks do not pay enough attention to the pragmatic translation of their content into a practical application. In this book, I want to take the reader on a journey I call Getting Started with Enterprise Architecture. I have tried to take the theory from existing frameworks and translate it into a practical and pragmatic approach. © Eric Jager 2023 E. Jager, Getting Started with Enterprise Architecture, https://doi.org/10.1007/978-1-4842-9858-9_1

2 With this approach, a basic implementation of Enterprise Architecture can be achieved. The method described in this book is based on the theory and methodology outlined in the TOGAF Standard. The book is written from the idea of the methodology, but does not apply it to the letter of the theory. When you start implementing Enterprise Architecture, it’s good to use one of the frameworks available. But such a framework can quickly feel a bit overwhelming. A framework describes in reasonable detail all the steps that can or should be taken to achieve a complete implementation of Enterprise Architecture. However, it is not always necessary to follow all of these steps from start to finish. This is especially true for the detailed approach that the frameworks prescribe. If an organization has not yet integrated working with architecture into its day-to-day operations, there is certainly no need to follow the frameworks’ approach to the letter. But how do you start, and what do you start with? What do you do and what don’t you do? What do you do first, and what do you do next? In this book, I provide both novice and experienced architects with a brief overview of Enterprise Architecture, explaining the origins of architecture, the most popular frameworks, and the architecture domains. The book then moves on to provide insight into the visualization of architecture by educating the reader on topics such as the architecture modeling language, essential architecture elements and concepts, and a place to store it all: the Architecture Repository. After laying out the basics, the book continues with a deep dive into the self-developed Enterprise Architecture Implementation Wheel. The Implementation Wheel is based on the methodology described in the TOGAF Standard and provides architects with a method that is easy to use because of its practical and pragmatic approach to implementing Enterprise Architecture. Using the Enterprise Architecture Implementation Wheel, I will show you how to tailor an architecture framework to the Chapter 1 IntroduCtIon

3 implementation needs of the existing organization. I will also show you how to produce artifacts (architecture deliverables) that are useful and usable, and get you started with Enterprise Architecture. The book concludes with a description of an actual architecture implementation that uses the Enterprise Architecture Implementation Wheel in practice. Using the challenges faced by the fictional company Lemon-A-de, I will demonstrate how a basic Enterprise Architecture can be used to help an organization implement its intended strategy. Although Lemon-A- de is a relatively small organization, the power of applying Enterprise Architecture in translating strategy into execution becomes clear. Enterprise Architecture can be implemented in many different ways. The way described in this book is just one of them. Following the steps outlined in this book, using the Enterprise Architecture Implementation Wheel, results in a usable whole and lays the foundation for further development of Enterprise Architecture within the organization. Getting Started with Enterprise Architecture is the ideal handbook for the architect who is tasked with implementing Enterprise Architecture in an existing organization. Chapter 1 IntroduCtIon

5 CHAPTER 2 Architecture Origin This chapter describes the origins of Enterprise Architecture. What created the need for structure to which Enterprise Architecture proved to be the answer? A timeline is used to provide insight into the key events that led to the emergence, evolution, and maturation of architecture. Additionally, a brief explanation of the structure of the two best-known architecture frameworks (the Zachman Framework and the TOGAF Standard) is provided. As part of the TOGAF Standard, this chapter also introduces the Architecture Development Method. The chapter concludes with the similarities and differences between the two frameworks. 2.1. Timeline The origins of Enterprise Architecture can be traced back to the 1960s and 1970s, when large organizations began to recognize the need for formal methods to manage and align their complex IT systems with business goals. During this time, there were various efforts to develop system architectures and information models. In the 1980s, the term Enterprise Architecture began to gain traction. The focus was primarily on defining and documenting the structure and components of an organization’s information systems. This decade saw the emergence of methodologies such as John Zachman’s Framework for Enterprise Architecture [2]. Enterprise Architecture emerged as a response to the increasing complexity of IT environments and business processes. © Eric Jager 2023 E. Jager, Getting Started with Enterprise Architecture, https://doi.org/10.1007/978-1-4842-9858-9_2

6 The 1990s marked a period of increased interest and growth in the field of Enterprise Architecture. More and more organizations recognized the importance of aligning IT with business goals. The Open Group introduced the TOGAF Standard in 1995, providing a comprehensive approach to Enterprise Architecture. The early 2000s saw a greater focus on integrating IT and business strategies, leading to the adoption of Enterprise Architecture as a strategic management discipline. Enterprise Architecture frameworks and methodologies, such as the Zachman Framework and the TOGAF Standard, gained wider acceptance and use. In the mid to late 2000s, Enterprise Architecture evolved to address the complexities of globalized and networked enterprises. The focus shifted to a more holistic approach to Enterprise Architecture, encompassing not only IT systems but also business processes, people, and organizational structures. This broader perspective was necessary to adapt to rapidly changing market dynamics and technological innovations. The evolution of Enterprise Architecture brought a new focus to the strategic importance of IT within organizations. It provided a way to align IT infrastructure and business processes with business goals, thereby increasing the value of IT. Enterprise Architecture also offered a way to manage and reduce the complexity of IT environments, thereby reducing the cost and risk of IT projects. In the 2010s, Enterprise Architecture became increasingly integrated with other strategic management disciplines, such as business process management, data management, and cybersecurity. Enterprise Architecture became an essential tool for guiding digital transformation initiatives, cloud adoption, and agile development practices. In recent years, Enterprise Architecture has continued to evolve in response to the growing importance of digitization, data-driven decision- making, and emerging technologies such as artificial intelligence, the Internet of Things (IoT), and blockchain. Enterprise Architecture is becoming more adaptive and agile to address the dynamic and rapidly changing business landscape. Chapter 2 arChiteCture Origin

7 Today, organizations use Enterprise Architecture to optimize their business processes and IT infrastructure, accelerate their digital transformation, and strengthen their competitive position. Enterprise Architecture continues to evolve and adapt to the ever-changing technology environment and business needs. Throughout its history, Enterprise Architecture has evolved from a primarily IT-focused discipline to a strategic and business-centric practice. It plays a critical role in helping organizations optimize their operations, align their IT investments with business goals, and navigate the complexities of the modern digital age. As technology and business needs continue to evolve, Enterprise Architecture will undoubtedly remain a critical discipline for organizations seeking competitive advantage and long-term success. Architectural frameworks have been developed to provide structure to the ever-evolving environment. These frameworks provide the guidance needed to manage the complexity of IT environments and business processes. Over the years, several architecture frameworks have been developed. The most popular architecture frameworks are the Zachman Framework, the TOGAF Standard, and the BIZBOK Guide [8]. In addition to the development of frameworks, the architecture modeling language ArchiMate was also created (see Chapter 6, Section 6.2). The modeling language provided a solution for visualizing the complex environments of organizations. Over the past decades, the frameworks and the modeling language have continued to evolve and mature. The evolution of the best-known architectural frameworks and the modeling language, starting with the introduction of the Zachman Framework [3], is shown in Table 2-1. Key milestones over the past 35 years are included in the overview. The overview is limited to milestones related to the Zachman Framework, the TOGAF Standard, the BIZBOK Guide, and ArchiMate. Chapter 2 arChiteCture Origin

8 Table 2-1. Major events in the field of architecture Year Event 1987 John Zachman publishes the Zachman Framework (with three columns) 1995 tOgaF (the Open group architecture Framework) is released 2001 archiMate, a modeling language for enterprise architectures, is released First publication of the Zachman Framework with all six columns 2007 tOgaF 8.1 is released, with enhanced support for SOa and it management 2009 archiMate 1.0 is released 2011 tOgaF 9 is released, with enhanced support for business and it alignment a 3.0 version of the Zachman Framework is published, labeled enterprise Ontology instead of framework First release of the BiZBOK guide 2012 archiMate 2.0 is released 2016 archiMate 3.0 is released 2018 tOgaF 9.2 is released, with enhanced support for digital transformation 2022 the Open group releases the tOgaF Standard, 10th edition, with support for agile architectures and new technologies such as ai and blockchain the BiZBOK guide 11.0 is released archiMate 3.2 is released 2023 the BiZBOK guide 12.0 is released Chapter 2 arChiteCture Origin

9 The BIZBOK Guide is a more limited framework than, for example, the Zachman Framework or the TOGAF Standard. The BIZBOK Guide focuses solely on Business Architecture. For this reason, the BIZBOK framework is not discussed further in this chapter. 2.2. Zachman Framework The first architecture frameworks appeared in the 1980s and 1990s. The Zachman Framework, published by John Zachman in 1987, was the first framework (actually an ontology) that focused on structuring business processes and IT infrastructure. Throughout the 1990s, the Zachman Framework became increasingly popular as an Enterprise Architecture methodology. The framework was used by many organizations, including large corporations and government agencies. During this time, the framework underwent several modifications to better meet the needs of organizations. Shortly after the year 2000, the Zachman Framework was further developed, extended, and adapted to the changing needs of organizations. More attention was paid to the relationship between Enterprise Architecture and digital transformation, and new tools and techniques were developed to support Enterprise Architecture modeling. There have also been several discussions held about the applicability and practical value of the Zachman Framework and its role in an ever-changing IT environment [4]. The Zachman Framework provides a structured approach to understanding and managing organizational complexity through a matrix model. The framework defines a set of perspectives or viewpoints from different stakeholders and focuses on six fundamental questions: what, how, where, who, when, and why. Since 2001, these questions have been presented in a six-by-six matrix, with each column representing one of the perspectives and each row representing one of the questions (see Figure 2-1). Chapter 2 arChiteCture Origin