Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Practical Model-Driven Enterprise Architecture
  • Toc
  • feedback
Practical Model-Driven Enterprise Architecture

Practical Model-Driven Enterprise Architecture

By : Bahri, Joe Williams
4.3 (7)
close
Practical Model-Driven Enterprise Architecture

Practical Model-Driven Enterprise Architecture

4.3 (7)
By: 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)
close
1
Section 1: Enterprise Architecture with Sparx Enterprise Architect
4
Section 2: Building the Enterprise Architecture Repository
12
Section 3: Managing the Repository

Reporting our findings

Once again, how we present our findings depends on the audience. There are many options available. We need to try to anticipate whether our audience would be more receptive to diagrams or lists. How much information is necessary? We also need to take into consideration what will be done with this information. What are the next steps?

In our case, the CTO is rather new to the company. They are quite experienced, but they came from a somewhat different industry. Perhaps we need to add more descriptions of the technologies in question. We need to ask ourselves the following questions:

  • How formal do we need to be in presenting the information?
  • Do we need to introduce this subject?
  • Do we need to include a cover sheet?
  • How much access do we have to this person?
  • Are they so busy that we wouldn't be able to meet again for weeks?

These questions may have been answered by having worked with the CTO in the past, but we haven&apos...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete