The book has three main objectives:? To put the focus on the specificity of enterprise architecture as adiscipline, whose purpose is to weave together data, information, andknowledge, with platforms, systems, and organization.? To provide actionable descriptions of architectures and engineeringprocesses.? To ensure a comprehensive and formal representation of all relevantaspects of business, organization, and systems.1 BISAC are subject codes from the Book Industry Study Group. Codes can be found here:http://bisg.org/page/BISACSubjectCodesTo achieve these objectives, enterprise architectures can take advantage ofArtificial intelligence and Machine-learning technologies to change and adaptto shifts in business and digital environments.

This textbook provides a comprehensive, holistic, scientifically precise, and practically relevant description of Enterprise Architecture Management (EAM). Based on state-of-the-art concepts, it also addresses current trends like disruptive digitization or agile methods. The book is structured in five chapters. The first chapter offers a comprehensive overview of EAM. It addresses questions like: what does EAM mean, what is the history of EAM, why do enterprises need EAM, what are its goals, and how is it related to digitalization? It also includes a short overview of essential EAM standards and literature. The second chapter provides an overview of Enterprise Architecture (EA). It starts with clarifying basic terminology and the difference between EA and EAM. It also gives a short summary of existing EA frameworks and methods for structuring the digital ecosystem into layers and views. The third chapter addresses the strategic and tactical context of the EAM capability in an enterprise. It defines essential terms and parameters in the context of enterprise strategy and tactics as well as the operative, organizational context of EAM. The fourth chapter specifies the detailed goals, processes, functions, artifacts, roles and tools of EAM, building the basis for an EAM process framework that provides a comprehensive overview of EAM processes and functions. Closing the circle, the last chapter describes how to evaluate EAM in an enterprise. It starts by laying out core terminology, like “metric” and “strategic performance measurement system” and ends with a framework that integrates the various measuring areas in the context of EA and EAM. This textbook focuses on two groups: First, EAM scholars, ie bachelor or master students of Business Information Systems, Business Administration or Computer Science. And second, EAM practitioners working in the field of IT strategy or EA who need a reliable, scientifically solid, and practically proven state-of-the-art description of essential EAM methods.

Does it seem you’ve formulated a rock-solid strategy, yet your firm still can’t get ahead? If so, construct a solid foundation for business execution—an IT infrastructure and digitized business processes to automate your company’s core capabilities. In Enterprise Architecture as Strategy: Creating a Foundation for Business Execution, authors Jeanne W. Ross, Peter Weill, and David C. Robertson show you how. The key? Make tough decisions about which processes you must execute well, then implement the IT systems needed to digitize those processes. Citing numerous companies worldwide, the authors show how constructing the right enterprise architecture enhances profitability and time to market, improves strategy execution, and even lowers IT costs. Though clear, engaging explanation, they demonstrate how to define your operating model—your vision of how your firm will survive and grow—and implement it through your enterprise architecture. Their counterintuitive but vital message: when it comes to executing your strategy, your enterprise architecture may matter far more than your strategy itself.

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 Enterprise Architecture Management (EAM) discipline deals with the alignment of business and information systems architectures. While EAM has long been regarded as a discipline for IT managers, this book takes a different stance: It explains how top executives can use EAM to leverage their strategic planning and controlling processes, as well as how it can contribute to their sustainable competitive advantage. Based on the analysis of best practices from eight leading European companies from various industries, the book presents the crucial elements of successful EAM. It outlines what executives need to do in terms of governance, processes, methodologies, and culture in order to bring their management to the next level. Beyond this, the book points out how EAM could develop in the next decade, thus allowing today’s managers to prepare for the future architecture management.

Salary surveys worldwide regularly place software architect in the top 10 best jobs, yet no real guide exists to help developers become architects. Until now. This book provides the first comprehensive overview of software architecture’s many aspects. Aspiring and existing architects alike will examine architectural characteristics, architectural patterns, component determination, diagramming and presenting architecture, evolutionary architecture, and many other topics. Mark Richards and Neal Ford—hands-on practitioners who have taught software architecture classes professionally for years—focus on architecture principles that apply across all technology stacks. You’ll explore software architecture in a modern light, taking into account all the innovations of the past decade. This book examines: Architecture patterns: The technical basis for many architectural decisions Components: Identification, coupling, cohesion, partitioning, and granularity Soft skills: Effective team management, meetings, negotiation, presentations, and more Modernity: Engineering practices and operational approaches that have changed radically in the past few years Architecture as an engineering discipline: Repeatable results, metrics, and concrete valuations that add rigor to software architecture

Organizational complexity is an unavoidable aspect of all businesses, even larger ones, which can hinder their ability to react to sudden or disruptive change. However, with the implementation of enterprise architecture (EA), businesses are able to provide their leaders with the resources needed to address any arising challenges. A Systemic Perspective to Managing Complexity with Enterprise Architecture highlights the current advances in utilizing enterprise architecture for managing organizational complexity. By demonstrating the value and usefulness of EA, this book serves as a reference for business leaders, managers, engineers, enterprise architects, and many others interested in new research and approaches to business complexity.