Practical Model Driven Enterprise Architecture

Bridge the gap between theory and reality by implementing real-world examples using the Sparx EA tool and ArchiMate® 3.1 specification to develop sophisticated enterprise architecture models serving every unit in your organization Key Features • Discover the various artifacts that enterprise architects need to develop for stakeholders to make sound decisions • Build a functional enterprise architecture repository that is rich in information, references, and metamodels • Learn how to use Sparx Enterprise Architect from scratch Book Description Most organizations face challenges in defining and achieving evolved enterprise architecture practices, which can be a very lengthy process even if implemented correctly. Developers, for example, can build better solutions only if they receive the necessary design information from architects, and decision-makers can make appropriate changes within the organization only if they know the implications of doing so. The book starts by addressing the problems faced by enterprise architecture practitioners and provides solutions based on an agile approach to enterprise architecture, using ArchiMate® 3.1 as an industry standard and Sparx EA as the modeling tool. You'll learn with the help of a fictional organization that has three business units, each expecting something different from you as the enterprise architect. You'll build the practice, satisfy the different requirements of each business unit, and share the knowledge with others so they can follow your steps. Toward the end, you'll learn how to put the diagrams and the content that you have developed into documents, presentations, and web pages that can be published and shared with any stakeholder. By the end of this book, you'll be able to build a functional enterprise architecture practice that supports every part of your organization. You'll also have developed the necessary skills to populate your enterprise architecture repository with references and artifacts. What you will learn • Discover how enterprise architects can contribute to projects and departments within organizations • Use Sparx Enterprise Architect to build a rich architecture repository • Learn about the ArchiMate® 3.1 specification as you apply it in real-world projects • Use the focused metamodel technique to build the information necessary for maintaining your repository's consistency and accuracy • Understand the importance of keeping architectural artifacts simple yet eye-catching • Define an operational model that fits your initial needs and expands as required Who this book is for This book is for enterprise architects at all architectural layers and practices of any maturity level. Many of the artifacts suggested in this book are inspired by The Open Group Architecture Framework (TOGAF®); however, familiarity with TOGAF® is not required. Whether you work within the business, applications, data, or technology layers, this book covers examples that apply to your work. Although not mandatory, experience modeling in Sparx Systems Enterprise Architect using any modeling language will be helpful. No prior knowledge of ArchiMate® is required to get started with this book.

bull; Written by expert practitioners who have hands-on experience solving real-world problems for large corporations bull; Helps enterprise architects make sense of data, systems, software, services, product lines, methodologies, and much more bull; Provides explanation of theory and implementation with real-world business examples to support key points

Every enterprise architect faces similar problems when designing and governing the enterprise architecture of a medium to large enterprise. Design patterns are a well-established concept in software engineering, used to define universally applicable solution schemes. By applying this approach to enterprise architectures, recurring problems in the design and implementation of enterprise architectures can be solved over all layers, from the business layer to the application and data layer down to the technology layer. Inversini and Perroud describe patterns at the level of enterprise architecture, which they refer to as Enterprise Architecture Patterns. These patterns are motivated by recurring problems originating from both the business and the underlying application, or from data and technology architectures of an enterprise such as identity and access management or integration needs. The Enterprise Architecture Patterns help in planning the technological and organizational landscape of an enterprise and its information technology, and are easily embedded into frameworks such as TOGAF, Zachman or FEA. This book is aimed at enterprise architects, software architects, project leaders, business consultants and everyone concerned with questions of IT and enterprise architecture and provides them with a comprehensive catalogue of ready-to-use patterns as well as an extensive theoretical framework to define their own new patterns.

This book provides practical advice on how to develop an enterprise architecture practice. The authors developed different tools and models to support organizations in implementing and professionalizing an enterprise architecture function. Coverage applies these tools and models to a number of different organizations and, as a result, will help readers avoid potential pitfalls and achieve success with enterprise architecture.

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.

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.

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.