Table Of ContentPractical
Model-Driven
Enterprise
Architecture
Design a mature enterprise architecture repository
using Sparx Systems Enterprise Architect and
ArchiMate® 3.1
Mudar Bahri
Joe Williams
BIRMINGHAM—MUMBAI
Practical Model-Driven Enterprise Architecture
Copyright © 2022 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or
transmitted in any form or by any means, without the prior written permission of the publisher,
except in the case of brief quotations embedded in critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the accuracy of the
information presented. However, the information contained in this book is sold without warranty,
either express or implied. Neither the author, nor Packt Publishing or its dealers and distributors,
will be held liable for any damages caused or alleged to have been caused directly or indirectly by
this book.
Packt Publishing has endeavored to provide trademark information about all of the companies
and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing
cannot guarantee the accuracy of this information.
Associate Group Product Manager: Richa Tripathi
Publishing Product Manager: Shweta Bairoliya
Senior Editor: Nisha Cleetus
Content Development Editor: Rosal Colaco
Technical Editor: Pradeep Sahu
Copy Editor: Safis Editing
Project Coordinator: Manisha Singh
Proofreader: Safis Editing
Indexer: Pratik Shirodkar
Production Designer: Prashant Ghare
Marketing Coordinator: Deepak Kumar
First published: April 2022
Production reference: 1250422
Published by Packt Publishing Ltd.
Livery Place
35 Livery Street
Birmingham
B3 2PB, UK.
ISBN 978-1-80107-616-6
www.packt.com
To my mother – thank you for your prayers. To my children, Samer, Lina,
and Lara – believe in yourselves!
– Mudar Bahri
To my wife, Robin – you are the love of my life. To my son, Ryan, and
daughter, Kayla, because I'm so proud of you both. To my grandson, Ethan,
because I adore you.
– Joe Williams
Contributors
About the authors
Mudar Bahri is an enterprise architect with long, progressive experience in implementing
TOGAF® in large and midsized organizations. He is an independent Enterprise
Architecture (EA) mentor and consultant and helps architects to build and develop
practical EA skills that can provide decision-makers with useful artifacts. He is a certified
TOGAF® 9.1 Enterprise Architect with experience in other EA frameworks and project
management methodologies. He has used TOGAF® to develop digital transformation
strategies, cloud migration plans, solution architectures, and proposals. He believes that
EA is meant to bridge gaps, not create new ones, so it has to be simple, practical, and serve
everyone.
I want to thank the people who have been close to me and supported me,
especially my brother, Tameem Bahri, who inspired me to start writing.
Joe Williams has over 40 years of experience in software engineering and architecture on
many platforms and spanning several business domains, including retail, banking, health
insurance, telecommunications, environment monitoring, and government systems. He
holds a BS degree in information systems from the University of San Francisco and is
a TOGAF® 9.1 certified practitioner. Joe preaches the practice of modeling every chance
he gets. He is an expert in the Unified Modeling Language (UML) and has helped
establish architecture practices at several organizations. He has been modeling solutions
using Sparx Systems Enterprise Architect since 2007 and other modeling tools since 1995.
He is currently retired and living in northern California.
I want to thank my co-author, Mudar, for asking me to help write this book,
and my wife, Robin, for encouraging me to do so.
About the reviewer
Kris Marshall is a results-driven chief enterprise architect with over 20 years of
accomplishments in information technology leadership, enterprise architecture,
learning technologies (artificial intelligence and machine learning), and organizational
transformation. Kris has extensive experience with business strategy development (for
over 35 public and private organizations) and defines business and solution architectures
in support of those strategies, aligning organizational goals and the IT infrastructure that
support them.
As a doctoral graduate of Pepperdine University, Kris' research focuses on enterprise
architecture theory and the intersectionality of learning technologies. Kris presently
supports numerous university research labs and participates in research groups at
Pepperdine University, MIT, and Singularity University.
Table of Contents
Preface
Section 1: Enterprise Architecture with
Sparx Enterprise Architect
1
Enterprise Architecture and Its Practicality
Understanding TOGAF® 4 Understanding ArchiMate® modeling
specification 23
TOGAF® implementation benefits 5
Metamodels 28
TOGAF® implementation drawbacks 9
Introducing our focused metamodels 30
Introducing agile EA 13
Introducing Sparx Systems
Understanding agile EA? 14
Enterprise Architect 31
Comparing agile EA with EA 15
Why Sparx? 31
Embedding agile EA into TOGAF® 16
The Sparx UI 33
Introducing ArchiMate® 20
Summary 39
ArchiMate®'s role in EA artifacts 21
2
Introducing the Practice Scenarios
Structuring the book around First scenario – application
the scenarios 42 architecture 45
A brief on ABC Trading 42 Scenario description 45
The structure of the book 43 Artifacts backlog 46
viii Table of Contents
Second scenario – technology Third scenario – business
architecture 49 architecture 54
Scenario description 50 Scenario description 54
Artifacts backlog 50 Artifacts backlog 55
Summary 57
Section 2: Building the Enterprise
Architecture Repository
3
Kick-Starting Your Enterprise Architecture Repository
Technical requirements 62 Adding elements to the diagram 72
Building the application Starting with the application
component context diagram 63 component 72
Establishing your first diagram 63 Introducing application services 78
Adding Actors 83
Creating the repository file 65
Identifying other dependent elements 88
Creating the diagram 66
Describing the diagram 69 Summary 94
Changing the diagram theme 71
4
Maintaining Quality and Consistency in the Repository
Technical requirements 96 Modeling best practices 115
Building the application Keeping your diagram focused 116
component focused metamodel 96 Fitting your diagram onto a single page 117
Establishing the metamodel diagram 97 Adding only the necessary information 118
Interpreting an ArchiMate® Paying attention to your diagram's
metamodel 100 appearance 118
Adding elements from other Knowing your audience 120
architecture layers 112
Summary 121
Table of Contents ix
5
Advanced Application Architecture Modeling
Technical requirements 124 Introducing application functions 153
Determining what diagrams Introducing application interactions 156
to produce 125 Introducing application events 156
Understanding the view 125 Describing application
Structural and behavioral views 126 structure 158
Getting to know the viewpoint 127
Revisiting the application component 159
Describing application Introducing application interfaces 160
behavior 127 Introducing application collaborations 164
Introducing data objects 166
Introducing application services 128
Introducing application processes 147 Summary 169
6
Modeling in the Technology Layer
Technical requirements 172 Understanding the distribution
network element 201
Modeling technology
environments 173 Understanding the material element 202
Understanding the location element 203
Examples of technology models 174
Putting the elements together for
Diagram filters and layers 180
ABC Trading 204
Technology stacks 182
Modeling dependencies in
Interpreting the standard 183
ArchiMate® 3.1 205
Using the node element 184
Using the device element 186 Modeling networks 207
Using the system software element 188 The communication network element 208
Using the technology interface Communication network-focused
element 191 metamodel 212
Using the technology collaboration The path element 213
element 194 Path element-focused metamodel 216
Using the technology artifact element 196
Summary 218
Modeling physical
environments 197
Understanding the equipment element 198
Understanding the facility element 199
