Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Practical Model-Driven Enterprise Architecture

You're reading from   Practical Model-Driven Enterprise Architecture Design a mature enterprise architecture repository using Sparx Systems Enterprise Architect and ArchiMate® 3.1

Arrow left icon
Product type Paperback
Published in May 2022
Publisher Packt
ISBN-13 9781801076166
Length 412 pages
Edition 1st Edition
Tools
Arrow right icon
Authors (2):
Arrow left icon
Joe Williams Joe Williams
Author Profile Icon Joe Williams
Joe Williams
Mudar Bahri Mudar Bahri
Author Profile Icon Mudar Bahri
Mudar Bahri
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1: Enterprise Architecture with Sparx Enterprise Architect
2. Chapter 1: Enterprise Architecture and Its Practicality FREE CHAPTER 3. Chapter 2: Introducing the Practice Scenarios 4. Section 2: Building the Enterprise Architecture Repository
5. Chapter 3: Kick-Starting Your Enterprise Architecture Repository 6. Chapter 4: Maintaining Quality and Consistency in the Repository 7. Chapter 5: Advanced Application Architecture Modeling 8. Chapter 6: Modeling in the Technology Layer 9. Chapter 7: Enterprise-Level Technology Architecture Models 10. Chapter 8: Business Architecture Models 11. Chapter 9: Modeling Strategy and Implementation 12. Section 3: Managing the Repository
13. Chapter 10: Operating the EA Repository 14. Chapter 11: Publishing Model Content 15. Other Books You May Enjoy

ABC Trading's technology background

In our scenario, the CTO is new to the organization. They are under pressure to control technology costs. Like many organizations, ABC Trading has dozens of applications that have been developed or purchased at various points in its history. Along with each application, new technology components have been implemented to support those applications and various other projects.

The CTO suspects that, along the way, some applications and technology components that are no longer needed have been left in place. It's also possible that the use of some applications or components can be eliminated by making relatively small changes. Unlike the previous user stories, this one requires us to analyze information across a broad spectrum of the enterprise rather than looking at the details of a single application or technology. The problem is that the CTO does not have this information.

But why not? It's not as if systems are implemented haphazardly...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime