To provide structure and transparency to the complex world of IT, Enterprise Architecture was created. However, we created complexities within Enterprise Architecture with Frameworks that are not easily understandable and purposefully implementable. In this book, Nagesh and Gerry help to turnaround Enterprise Architecture organizations. They introduce a simple IDEA Framework that is based on common practices and investments within IT organizations. The Ten deliverables presented in this book bring structure and clarity to IT organizations that are 10-people IT shops and 1000+ IT staff enterprises alike. This book is not an ivory tower work, it is actionable, applied Enterprise Architecture. It is also a healthy dose of EA tough love. If you want to know why EA fails, read the second chapter. It is introspective, it does not blame external forces: the not-my-fault syndrome. It also does not blame, in fact it hardly mentions, technology. To be fair, the Nagesh and Gerry do recognize external influences; however they are viewed as risks that must be managed. Most corporations focus on this years budget, investments, and rewards. The same focus rolls downhill to the Information Technology department. If the IT department has not successfully communicated the budget and managed to spend it within the limits (10% variance), everything else may seem irrelevant. Eventually, Nagesh and Gerry started looking through current IT systems and IT assets to understand: (a) where the current funds were being invested, (b) how these investments jelled or were mandated because of the previous investments that had been made by IT, and (c) how the companys business priorities aligned with future technology needs, including the need to meet compliance requirements. Considering and discovering the answers to these three questions led Nagesh and Gerry to develop a definition of Enterprise Architecture that was based on technology investments Investment Driven Enterprise Architecture (IDEA) Framework. The purpose of the IDEA Framework is to provide guidance on how the corporations future technology will be drafted and communicated. Its method is to utilize actual systems, hardware, people, and business functions in order to establish boundaries within which the IDEA Framework will work. The structure of the IDEA Framework differs from that of many others because it consists of key deliverables that fit into day-to-day activities and it accommodates an enterprise-wide strategic plan. It also provides for the much-needed interaction between these key deliverables and facilitates contributions from key stakeholders across Business Units and the various IT departments. In essence, the IDEA Framework takes the key deliverables, stakeholders, and organizations and demonstrates how they dynamically function together.

Pragmatic Enterprise Architecture is a practical hands-on instruction manual for enterprise architects. This book prepares you to better engage IT, management, and business users by equipping you with the tools and knowledge you need to address the most common enterprise architecture challenges. You will come away with a pragmatic understanding of and approach to enterprise architecture and actionable ideas to transform your enterprise. Experienced enterprise architect James V. Luisi generously shares life cycle architectures, transaction path analysis frameworks, and more so you can save time, energy, and resources on your next big project. As an enterprise architect, you must have relatable frameworks and excellent communication skills to do your job. You must actively engage and support a large enterprise involving a hundred architectural disciplines with a modest number of subject matter experts across business, information systems, control systems, and operations architecture. They must achieve their mission using the influence of ideas and business benefits expressed in simple terms so that any audience can understand what to do and why. Pragmatic Enterprise Architecture gives you the tools to accomplish your goals in less time with fewer resources. Expand your Enterprise Architecture skills so you can do more in less time with less money with the priceless tips presented Understand the cost of creating new Enterprise Architecture disciplines and contrast those costs to letting them go unmanaged Includes 10 life cycle architectures so that you can properly assess the ROI of performing activities such as outsourcing, insourcing, restructuring, mergers and acquisitions, and more Complete appendix of eight transaction path analysis frameworks provide DBA guidelines for proper physical database design

Learn how to institute and implement enterprise architecture in your organization. You can make a quick start and establish a baseline for your enterprise architecture within ten weeks, then grow and stabilize the architecture over time using the proven Ready, Set, Go Approach. Reading this book will: 1. Give you directions on how to institute and implement enterprise architecture in your organization. You will be able to build close relationships with stakeholders and delivery teams, but you will not need to micromanage the architecture’s operations. 2. Increase your awareness that enterprise architecture is about business, not information technology. 3. Enable you to initiate and facilitate dramatic business development. The architecture of an enterprise must be tolerant of currently unknown business initiatives. 4. Show you how to get a holistic view of the process of implementing enterprise architecture. 5. Make you aware that information is a key business asset and that information architecture is a key part of the enterprise architecture. 6. Allow you to learn from our experiences. This book is based on our 30 years of work in the enterprise architecture field, colleagues in Europe, customer cases, and students. We do not pretend to cover all you need to know about enterprise architecture within these pages. Rather, we give you the information that is most important for effective and successful guidance. Sometimes, less is more. If your company is about to make a major change and you are looking for a way to reduce the changes into manageable pieces—and still retain control of how they fit together—this is your handbook. Maybe you are already acting as an enterprise architect and using a formal method, but you need practical hints. Or maybe you are about to set up an enterprise architect network or group of specialists and need input on how to organize your work. The Ready-Set-Go method for introducing enterprise architecture provides you, the enterprise architect, with an immediate understanding of the basic steps for starting, organizing, and operating the entirety of your organization’s architecture. Chapter 1: Ready shows how to model and analyze your business operations, assess their current status, construct a future scenario, compare it to the current structure, analyze what you see, and show the result in a city plan. Chapter 2: Set deals with preparing for the implementation of the architecture with governance, enterprise architecture organization, staffing, etc. This is the organizing step before beginning the actual work. Chapter 3: Go establishes how to implement a city plan in practice. It deals with the practicalities of working as an enterprise architect and is called the “running” step. The common thread through all aspects of the enterprise architect’s work is the architect’s mastery of a number of tools, such as business models, process models, information models, and matrices. We address how to initiate the architecture process within the organization in such a way that the overarching enterprise architecture and architecture-driven approach can be applied methodically and gradually improved.

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.

This book provides a method to plan, develop, validate, or evolve the design of an enterprise architecture function so that it fully meets the organization’s needs. The reader will benefit from this book in two ways. First, it provides a structured overview and orientation to the subject of architecture from an architecture function perspective. Second, it guides through the process of planning, building, and operating your own architecture organization based on a generic architecture function blueprint presented in the form of a pattern language offering a structured means for navigating, contextualizing, combining, and composing the architecture function patterns. The book is structured in six chapters. Chapter 1 “Introduction” explains the starting position and objectives of the book and introduces key concepts that will be explained further in subsequent chapters. Chapter 2 “Architecture Function Pattern Language” introduces the concepts of pattern, pattern catalogue, pattern topology, and ontology and explains how these concepts are combined to form a pattern language for planning, designing, and operating an architecture function. Next, Chapter 3 “Architecture Function – Context“ introduces concepts that are crucial for understanding the challenges that an architecture function faces and presents a generic schema for the business organizations and value chain. Chapter 4 “Architecture Function – Challenge” looks at an architecture function from a black box perspective and outlines the expectations and requirements that companies place on architecture organizations. It discusses the building blocks of an architecture function, the services it provides along the enterprise value chain, and the quality attributes that enterprises expect from their functions. Chapter 5 “Architecture Function – Constitution” then shifts from a black-box perspective to a white-box perspective and outlines the generic design of an architecture function in order to realize functional and quality-related requirements. Chapter 6 “Pattern Catalogue“ eventually introduces the pattern catalogue with a total of 48 architecture function patterns. These patterns suggest designs for collaboration between the architecture function and enterprise organizations, for the elaboration and development of enterprise services along the enterprise value chain, or for aligning architecture governance with enterprise governance. The book is intended for a broad readership, including enterprise, domain, and solution architects, lecturers and students, and anyone else interested in understanding the value proposition, responsibilities, outcomes, methods, and practices of architecture functions. It introduces the basic concepts and theories needed to understand the pattern language presented and the patterns it summarizes.

The book attempts to answer a few of the common questions related to Enterprise Architecture (EA) and SOA. What are the issues? What is EA? Why should an organization consider EA? How to build the Enterprise Architecture and document it. What are the roadblocks, politics, governance, process and design method? How to measure the value deliverd by EA and its maturity and and how to select an Enterprise Architect? An innovative EA Framework, the associated metamodel and generic Enterprise Reference Maps (templates) for the business process, applications and infrastructure layers are proposed. The framework looks like a content page showing the chapters of a book or, in this case, the components of the Enterprise Architecture without actually describing them but showing how they fit into the whole. The book then identifies and summarises Best Practices in the Enterprise Architecture and SOA development, EA patterns, the integration to the mundane solution architecture, delivery checklistsÉ The book is intended to be a document summarising why and how to build an Enterprise Architecture.

Organizations today exist in an environment of unprecedented change. They do so against a backdrop of a global, competitive marketplace, the fast-paced enablement of technology, amplified regulation and accelerating organizational complexity. Many organizations are addressing change in a sub-optimal way and they are operating without a clear view of where their operational risks lie. It is these dynamics that are leading organizations to recognise and embrace Business Architecture. Despite this environment, Business Architecture can be a difficult ’sell’ - it is often perceived to be abstract and lacking in tangible delivery. To succeed, Business Architecture must be pragmatic and, to be sustainable, it must focus on achieving long-term value and, at the same time, recognise the shorter-term tactical needs of the organisation. With these challenges in mind, this book provides a practical guide on how to employ Business Architecture and how to build a balanced proposition that delivers value to a broad range of stakeholders. As the book states, Business Architecture should not be practised in isolation, nor should it be thought of as a one-off process; it needs to be woven into the fabric of the organization. And so the authors illustrate the opportunities for weaving the Business Architecture Practice into this fabric through the various stakeholders and life cycles that exist, both formally and informally, within an organization. Whilst recognizing best practice, this book explores a new, inspirational level of Business Architecture whilst acknowledging that the best way to realize the vision is one step at a time.