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

Building the application component context diagram

A context diagram, as the name implies, is a diagram that shows the surroundings of a specific component. The main purpose of context diagrams is to provide a high-level introduction to an element such as an application component by answering the following questions:

  • What is the element and why does it (or will it) exist?
  • What does it provide to the enterprise?
  • Who will be using it?
  • Are there any other applications that interact or exchange data with it?
  • What data is being (or will be) exchanged?

Context diagrams can be useful for describing existing elements (as is) and for describing targeted elements (to be). The same concept applies, and the same types of elements can be used in both cases. Before you roll your sleeves up, let's see how to establish your first diagram.

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