Enterprise Architecture Planning (EAP) is a high-level blueprint for data, applications, and technology that is a cost-effective long-term solution. The authors give you a common-sense approach to EAP, supported by examples of architectures, procedures, checklists, and useful guidelines.
This book investigates solutions incorporated by architecture boards in global enterprises to resolve issues and mitigate related architecture risks, while also proposing and implementing an adaptive integrated digital architecture framework (AIDAF) and related models and approaches/platforms, which can be applied in companies to promote IT strategies using cloud/mobile IT/digital IT. The book is divided into three main parts, the first of which (Chapters 1–2) addresses the background and motivation for AIDAF aligned with digital IT strategies. The second part (Chapter 3) provides an overview of strategic enterprise architecture (EA) frameworks for digital IT, elaborates on the essential elements of EA frameworks in the digital IT era, and advocates using AIDAF, models for architecture assessment/risk management, knowledge management on digital platforms. In turn, the third part (Chapters 4–7) demonstrates the application and benefits of AIDAF and related models, as shown in three case studies. “I found this book to be a very nice contribution to the EA community of practice. I can recommend this book as a textbook for digital IT strategists/practitioners, EA practitioners, students in universities and graduate schools.” (From the Foreword by Scott A. Bernard) “In this new age of the digital information society, it is necessary to advocate a new EA framework. This book provides state-of-the art knowledge and practices about EA frameworks beneficial for IT practitioners, IT strategists, CIO, IT architects, and even students. It serves as an introductory textbook for all who drive the information society in this era.”(From the Foreword by Jun Murai)
Enterprise architecture defines a firm's needs for standardized tasks, job roles, systems, infrastructure, and data in core business processes. This book explains enterprise architecture's vital role in enabling - or constraining - the execution of business strategy. It provides frameworks, case examples, and more.
Cloud Enterprise Architecture examines enterprise architecture (EA) in the context of the surging popularity of Cloud computing. It explains the different kinds of desired transformations the architectural blocks of EA undergo in light of this strategically significant convergence. Chapters cover each of the contributing architectures of EA—business, information, application, integration, security, and technology—illustrating the current and impending implications of the Cloud on each. Discussing the implications of the Cloud paradigm on EA, the book details the perceptible and positive changes that will affect EA design, governance, strategy, management, and sustenance. The author ties these topics together with chapters on Cloud integration and composition architecture. He also examines the Enterprise Cloud, Federated Clouds, and the vision to establish the InterCloud. Laying out a comprehensive strategy for planning and executing Cloud-inspired transformations, the book: Explains how the Cloud changes and affects enterprise architecture design, governance, strategy, management, and sustenance Presents helpful information on next-generation Cloud computing Describes additional architectural types such as enterprise-scale integration, security, management, and governance architectures This book is an ideal resource for enterprise architects, Cloud evangelists and enthusiasts, and Cloud application and service architects. Cloud center administrators, Cloud business executives, managers, and analysts will also find the book helpful and inspirational while formulating appropriate mechanisms and schemes for sound modernization and migration of traditional applications to Cloud infrastructures and platforms.
An Introduction to Enterprise Architecture is the culmination of several decades of experience that I have gained through work initially as an information technology manager and then as a consultant to executives in the public and private sectors. I wrote this book for three major reasons: (1) to help move business and technology planning from a systems and process-level view to a more strategy-driven enterprise-level view, (2) to promote and explain the emerging profession of EA, and (3) to provide the first textbook on the subject of EA, which is suitable for graduate and undergraduate levels of study. To date, other books on EA have been practitioner books not specifically oriented toward a student who may be learning the subject with little to no previous exposure. Therefore, this book contains references to related academic research and industry best practices, as well as my own observations about potential future practices and the direction of this emerging profession.
The Principle Based Enterprise Architecture (PBEA) Method is a proven approach for implementing an enterprise-wide architecture practice in large- and medium-sized technology organizations. The method begins with a set of architecture objectives linked to concepts that matter to the business. It then lays out how to build technology platforms from components we call assets and how to manage those assets over time, through the calculation and management of technical debt. The PBEA method is a pragmatic approach to enterprise technology architecture which is based on the fundamental tenet that technology is never perfect, compromises must be made, and one of the most valuable functions an enterprise architecture group can provide for a company is a method for managing those compromises. We call the cost of these compromises "technical debt". It is essentially the difference between what we should have spent on technology and what we did spend. The PBEA method grew from the experience of watching how large technology organizations function (or do not function as the case may be). You will learn about such essential topics as: Best practices for building, managing, and ultimately evolving an enterprise architecture. Defining principles and golden rules to guide the high-quality creation of the building blocks of products and platforms (assets). Calculating technical debt and assessing the business risk associated with carrying that debt. Identifying and managing the actions required to pay off technical debt and mitigate any associated business risk. If you have witnessed products and platforms 'collapsing under the burden of technical debt', then this book is for you. If you have seen technology organizations fail to learn from their mistakes, then this book is also for you. If you have been involved in the development of products where Version 2 required almost a rewrite of Version 1 or worked in technology organizations that spend an excessive portion of their budget on maintenance, then the PBEA method may provide both insight and benefit. Or if you are an enterprise architect and have witnessed one or more Enterprise Architecture functions get eliminated because they were seen as 'too ivory tower' and too distant from the customer, then this book will provide you with a concrete, fact-based approach for building an enterprise architecture function that is fully aligned with business objectives and that delivers real measurable benefit to the corporation.
Implement successful and cost-effective enterprise architecture projects. This book provides a new approach to developing enterprise architecture based on the idea of emergent behaviors—where instead of micromanaging system implementation, the enterprise architecture effort establishes clear goals and leaves the details to the implementation teams. System development efforts are measured based on their contribution to achieving business goals instead of implementing specific (possibly outdated) requirements. Most enterprise architecture initiatives employ one of the existing system architecture frameworks such as Zachman or The Open Group Architecture Framework, but these are not well-suited for enterprise architecture in a modern, agile organization. The new approach presented in this book is based on the author’s experience with large enterprise architecture efforts. The approach leverages research into complex adaptive systems and emergent behaviors, where a few simple rules result in complex and efficient enterprise behaviors. Simplifying the task of establishing and maintaining the enterprise architecture cuts the costs of building and maintaining the architecture and frees up those resources for more productive pursuits. System implementers are given the freedom to rapidly adapt to changing user needs without the blessing of the enterprise modeling priesthood, and the architecture is transformed from a static pile of obscure models and documents into an operational framework that can be actively used to manage an enterprise’s resources to better achieve business goals. The enterprise architect is free to stop focusing on building and maintaining models and start focusing on achieving business goals. What You’ll Learn Refocus enterprise architecture on business needs by eliminating most of the enterprise-level models Delegate tasks to the development teams who do system implementation Document business goals, establish strategies for achieving those goals, and measure progress toward those goals Measure the results and gauge whether the enterprise architecture is achieving its goals Utilize appropriate modeling techniques that can be effectively used in an enterprise architecture Who This Book Is For Architecture practitioners and architecture managers: Practitioners are experienced architects who have used existing frameworks such as Zachman, and have experience with formal architecture modeling and/or model-based system engineering; managers are responsible for managing an enterprise architecture project and either have experience with enterprise architecture projects that were ineffective or are looking for a different approach that will be more cost-effective and allow for more organizational agility. Government program managers looking for a different approach to make enterprise architecture more relevant and easier to implement will also find this book of value.
As a software architect you work in a wide-ranging and dynamic environment. You have to understand the needs of your customer, design architectures that satisfy both functional and non-functional requirements, and lead development teams in implementing the architecture. And it is an environment that is constantly changing: trends such as cloud computing, service orientation, and model-driven procedures open up new architectural possibilities. This book will help you to develop a holistic architectural awareness and knowledge base that extends beyond concrete methods, techniques, and technologies. It will also help you to acquire or expand the technical, methodological, and social competences that you need. The authors place the spotlight on you, the architect, and offer you long-term architectural orientation. They give you numerous guidelines, checklists, and best practices to support you in your practical work. "Software Architecture" offers IT students, software developers, and software architects a holistic and consistent orientation across relevant topics. The book also provides valuable information and suggestions for system architects and enterprise architects, since many of the topics presented are also relevant for their work. Furthermore, IT project leads and other IT managers can use the book to acquire an enhanced understanding of architecture. Further information is available at www.software-architecture-book.org.
This textbook provides a hands-on introduction to enterprise architecture management. It guides the reader through the applications of methods and tools to typical business problems by presenting enterprise architecture frameworks and by sharing experiences from industry. The structure of the book represents the typical stages of the journey of an enterprise architect. Chapter 1 addresses the central question of what to achieve with the introduction of an enterprise architecture. Chapter 2 then introduces concepts and visualizations for business architecture that help with understanding the business. In chapter 3 the development of an application architecture is outlined, which provides transparency on information systems and their business context. Next, chapter 4 presents visual tools to analyze, improve and eventually optimize the application landscape. Chapter 5 discusses both traditional organizational as well as collaborative approaches to enterprise architecture management. Eventually, several established enterprise architecture frameworks like TOGAF, Zachmann, ArchiMate, and IAF are described in chapter 6. The book concludes with a summary and an outlook on future research potential in chapter 7. Based on their experiences through several years of teaching, the authors introduce students step-by-step to enterprise architecture development and management. Their book is intended as a guide for master classes at universities and includes lots of exercises and references for further reading.
Based on an extensive study of the actual industry best practices, this book provides a systematic conceptual description of an EA practice and offers practically actionable answers to the key questions related to enterprise architecture.