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

Chapter 3: Kick-Starting Your Enterprise Architecture Repository

When stakeholders introduce an idea of developing a new application to solve some business problems, your job as an enterprise architect is to help them and everyone involved to have a better understanding of what the application is for. Long before starting any designs, you need to identify what service the application is intending to provide, who will be using it, and with which existing applications it will exchange data. Whether you are planning to build this application in-house, hire a contractor to build it, or buy it off the shelf, you still need to develop these conceptual models to help the stakeholders make the right decision – including the decision of approving or rejecting the application altogether. Your role as an enterprise architect is to clarify and formalize the ideas and turn them into requirements for the solutions architect to build and/or deploy the application.

We have a backlog from...