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

Describing application structure

The application structure describes the parts of the application that will be built. This includes the components and subcomponents, the interfaces, and the collaborations. They are the tangible parts of the application that can be deployed, copied, moved, deleted, or accessed. In this section, we will see how you can describe different parts of the application structure using different element types and relationships.

We will start this section by revisiting the application component, introducing the application interfaces, and then we will explore the application collaborations and how they can be helpful elements when modeling large applications.

Revisiting the application component

The Tracking App application component was introduced in Chapter 3, Kick-Starting Your Enterprise Architecture Repository, and the focused metamodel was introduced in Chapter 4, Maintaining Quality and Consistency in the Repository. So, we will not repeat what...