Book Image

Practical Model-Driven Enterprise Architecture

By : Mudar Bahri, Joe Williams
Book Image

Practical Model-Driven Enterprise Architecture

By: Mudar Bahri, Joe Williams

Overview of this book

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.
Table of Contents (16 chapters)
1
Section 1: Enterprise Architecture with Sparx Enterprise Architect
4
Section 2: Building the Enterprise Architecture Repository
12
Section 3: Managing the Repository

Summary

In this chapter, we've covered some of the most fundamental aspects of enterprise architecture modeling. We've looked at the differences between behavioral and structural models and the elements that make them up. We've also looked at some common diagram types, such as the context diagram and the catalog. We've learned more about how to manipulate our models in Sparx and how to connect them to each other to provide an easy navigation experience for readers.

You will see that many of these aspects will be reinforced in subsequent chapters as we cover aspects of the technology and business layers of ArchiMate®. This is because many of the element types across these layers share a common function but with a differing scope. There are services, functions, processes, events, components, and interfaces in the business, application, and technology layers. If you understand the thin lines that differentiate each element in each layer, you've mastered...