Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Practical Model-Driven Enterprise Architecture
Practical Model-Driven Enterprise Architecture

Practical Model-Driven Enterprise Architecture: Design a mature enterprise architecture repository using Sparx Systems Enterprise Architect and ArchiMate® 3.1

eBook
$33.99 $37.99
Paperback
$41.99
Subscription
Free Trial
Renews at $19.99p/m

What do you get with eBook?

Product feature icon Instant access to your Digital eBook purchase
Product feature icon Download this book in EPUB and PDF formats
Product feature icon Access this title in our online reader with advanced features
Product feature icon DRM FREE - Read whenever, wherever and however you want
Product feature icon AI Assistant (beta) to help accelerate your learning
OR
Modal Close icon
Payment Processing...
tick Completed

Billing Address

Table of content icon View table of contents Preview book icon Preview Book

Practical Model-Driven Enterprise Architecture

Chapter 1: Enterprise Architecture and Its Practicality

Enterprise Architecture (EA) is a discipline that many organizations have adopted or have been motivated to adopt over the last two decades or so due to its promises to bridge the gaps between business and technology. EA is the art of defining and categorizing the elements that compose an enterprise and defining the relationships among these elements to get useful information that supports making strategic and tactical decisions. There are several frameworks that guide EA implementation, but the most popular one is TOGAF®.

This chapter starts by highlighting what made TOGAF® the de facto standard for implementing EA and puts the spotlight on the problems that most TOGAF® practitioners face – some (if not all) of which I am quite sure you will have faced. As I have learned, talking about problems is never helpful without providing solutions, so we will introduce a hands-on approach that has been extracted from years of practical experience in the EA domain to help you in aligning the theory with the practice smoothly and more productively.

Please remember that this book is not about teaching TOGAF®; I expect that you already have some knowledge of and experience with the framework and are looking for solutions to the problems that you may have already faced. It is also not about making comparisons between TOGAF® and other frameworks to show the advantages versus disadvantages of each. This book is based on TOGAF® and ArchiMate® only and will explain how to use them in a way that can help your organization to get quick, tangible outcomes from adopting them.

The following is a list of topics that will be covered in this chapter:

  • Understanding TOGAF®
  • Introducing agile EA
  • Introducing ArchiMate®
  • Introducing Sparx Systems Enterprise Architect

Let's start by talking about the benefits and drawbacks of TOGAF®.

Understanding TOGAF®

Even though TOGAF® came nearly two decades after the Zachman Framework (https://www.zachman.com/about-the-zachman-framework) was introduced, it dominated the market very quickly and became one of the most important standards in the EA domain. John Zachman was the first to introduce the concept of EA in the mid-eighties and defined an EA framework carrying his name. For many reasons, the Zachman Framework was not adopted by many architects, but the idea remained in many people's minds.

TOGAF® started to gain popularity in late 2002 when The Open Group® introduced version 8.0. From there onward, it continued to gain popularity and started to become the de facto standard in the EA domain especially when The Open Group® released version 9.0 in early 2009, followed by 9.1, and finally 9.2 in 2018. TOGAF® became popular because it provided enterprise architects with rich content that guides their development journeys and makes implementing EA achievable.

Architects chose to follow TOGAF® for many reasons, which we will talk about later in this section. However, implementing TOGAF® was not a straightforward journey for many, and it brought new challenges and difficulties to the architects. As a result, many EA projects ended up with massive scope creep, unneeded outcomes, and useless acronyms. Therefore, many EA projects got terminated due to low return on investment and more people lost faith in EA as a practical approach even with TOGAF®. In this section, we will talk about the following:

  • The benefits of using TOGAF® as a framework for implementing EA projects
  • The drawbacks that make implementing TOGAF® challenging

While you read this section, I am sure that you will recall similar situations that you or your team have faced in your EA implementation journey.

TOGAF® implementation benefits

The following features are some advantages that made TOGAF® the preferred choice over other frameworks for many architects:

  • Complete online documentation that is freely available.
  • An easy-to-follow process.
  • It fits architects with different experience.
  • A rich content metamodel.
  • It's loaded with guidelines and techniques.
  • It encourages learning.

We will look at each benefit individually in the following subsections and see why more than 111,000 individuals from over 144 countries have chosen to use TOGAF® and be certified in it (according to https://togaf9-cert.opengroup.org/certified-individuals on the date of writing this paragraph).

Complete online documentation that is freely available

The Open Group® has provided all the TOGAF® versions online and for free with anonymous access. This makes it possible for people at all levels of experience to explore, read, and learn the framework at their own pace without feeling constrained by costly subscriptions or time-limited trials. You do not even need to register on the website to be granted access to the content, which is something that not all frameworks provide. Some frameworks require paid memberships, and some require at least creating a profile, but this is not the case with TOGAF®. EA practitioners also find it very convenient to have the material online and accessible anytime, anywhere, and on any device.

Note

Even after being TOGAF® certified for years and practicing it continuously for about 15 years, I always have the website bookmarked in my browser.

An easy-to-follow process

One of the core TOGAF® components is the Architecture Development Method (ADM), which is a series of phases, each with a defined set of inputs, steps, and outputs. Architects find it easy to follow the ADM, especially architects coming from an IT background. They all know that if you want to build a solution, you need to first envision it, define its requirements, plan it, design it, build it, deploy it, and then operate it, which is very well known as the System Development Life Cycle (SDLC). The ADM has a similar concept to the SDLC, but the objective is to architect the entire enterprise and not a single IT solution.

The following diagram represents the ADM cycle as defined by TOGAF® here: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap04.html, using ArchiMate® 3.1 notation:

Figure 1.1 – An ArchiMate® representation of the ADM cycle (The Open Group®)

Figure 1.1 – An ArchiMate® representation of the ADM cycle (The Open Group®)

As you can see, the ADM cycle starts with the Preliminary Phase, which establishes the EA practice and formalizes the choice of tools and methodology. It is then followed by eight iterative phases that cover one part of the enterprise at a time.

It fits architects with different experience

Architects coming from different backgrounds and with different experience can all find something useful in TOGAF® that they can use in their area of expertise. Solution architects who have TOGAF® experience will have a better understanding of a business and be able to provide it with the right solutions that address its requirements and strategic directions. A second example would be project managers with TOGAF® experience, who will find it easy to upgrade their project management skills to program and portfolio management because understanding TOGAF® helps them understand how the enterprise works and how to have a holistic view of the different moving parts. IT operations managers with TOGAF® experience can use its Technical Reference Model (TRM) to categorize and classify the technology stack in their organizations using an industry-standard method, which helps them make the right decisions.

The list of examples can include every single member within the enterprise, so TOGAF® is an extremely useful and flexible framework that offers something for every practitioner, and each person will benefit from it differently.

A rich content metamodel

The metamodel provides architects with a foundation that tells them what the components of the enterprise are and how they are related to each other.

The TOGAF® metamodel, along with the taxonomy, provides architects with a better understanding so that they can describe the enterprise with consistency even if they look from different perspectives. Classifying and categorizing the elements and relationships of the enterprise is the heart and soul of EA. Here is the full TOGAF® 9.2 content metamodel: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap30.html#tag_30_03.

Additionally, TOGAF® provides a taxonomy and definition for all the keywords that architects use, which helps in unifying the language among different architects and makes their communications and documentation easier. People from different backgrounds can still argue the meanings of these definitions based on their interpretations but having a taxonomy can dramatically reduce these arguments. The Open Group® has even extended the TOGAF® taxonomy through ArchiMate®, which makes the combination of the two a complete and detailed set.

Important Note

This book will use the taxonomy defined by The Open Group® in both the TOGAF® 9.2 and ArchiMate® 3.1 materials as they are and will elaborate more for greater clarity.

It's loaded with guidelines and techniques

TOGAF® has tried to address all the issues that enterprise architects may encounter during their implementation engagements. It provides a set of useful tools, materials, and techniques, such as the following:

  • A set of principles that enterprise architects can start with and modify as needed.
  • Stakeholder management techniques and a proposed set of artifacts that can be of interest to different stakeholders.
  • Patterns and techniques to segment and control the scope and size of the EA practice.
  • A high-level governance model that can fit any size organization and team.
  • A general structure of the EA content repository that can be scaled up or down as needed.

The complete list of guidelines and techniques is too long to be covered in this book and you may have already experienced some or all of them. Please refer to https://pubs.opengroup.org/architecture/togaf92-doc/arch/chap17.html if you want to learn more about them.

It encourages learning

With more people showing an interest in TOGAF®, The Open Group® wanted to encourage practitioners to be distinguished by becoming certified in the framework. With the increasing demand for experienced enterprise architects, becoming TOGAF® certified is a desire and sometimes a requirement by employers when hiring or contracting.

Just like anything good in life, the benefits of the framework come with a cost, which can outweigh the benefits if not handled with care. After having a quick look at the benefits of using TOGAF®, let's review some of the drawbacks that can be associated with TOGAF® implementations.

TOGAF® implementation drawbacks

Even with all the materials that TOGAF® offers, not every implementation project ends as planned, if it ends at all. Some EA implementations end up delivering something different than what was originally planned, some end up in a massive scope creep that overwhelms the project with infinite tasks and activities, and some remain within the drawers of the EA team until the sponsors decide to pull the plug.

In this section, we will highlight the things that may contribute to these results, and will provide you with some example traps that some architects may have fallen into; you may have witnessed or experienced some of them during your EA journey:

  • The ADM is a giant waterfall process.
  • The lack of practicality.
  • High cost-to-value ratio.
  • TOGAF® is mostly adopted by IT people.

Let's look at each of these in more detail in the following subsections.

The ADM is a giant waterfall process

As mentioned earlier, the ADM is a major factor in the success of TOGAF®. However, ADM is a sequence of phases, which turns out to be a waterfall method by nature. Therefore, TOGAF® provided a chapter explaining how to use the ADM iteratively (https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap18.html), and another chapter on Architecture Partitioning to help keep the scope of work under control by dividing it into smaller partitions (https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap36.html). Even with these techniques, there is still huge room for making scope mistakes because following a phased approach can end up with one phase requiring completion before starting the next. Attempting to finish a phase with all the details, inputs, steps, and outputs that are defined in the ADM can leave you and your team with an infinite set of tasks to do.

Note

Please keep in mind that I am talking from practical experience and how I have seen things ending up in most cases. The problem is not in TOGAF® itself, but with the wrong interpretation by the practitioners of how many details need to be defined for each ADM phase.

For example, in the ADM, architects start with the Preliminary Phase, which has an objective to define and establish the detailed processes and resources for Architecture Governance (https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap05.html). Having this objective is understandable because, without governance, no project will be completed.

Establishing the Architecture Governance Board (AGB), which is the governance body that approves or rejects changes to the architecture, and defining their roles and responsibilities, their job descriptions, the governance processes, and the key performance indicators can take anywhere between a single day and 6 months, which is what I like to call the Effort Blackhole. This refers to a situation in which all the effort that you and your team put into finishing the phase will never end and there will always be the need for more.

Additionally, having this objective in the Preliminary Phase before the project is officially started makes it difficult for stakeholders and governance board members to understand how to govern something that does not yet exist. They can outline some processes and assign responsibilities, but that must start at a high level, then they'd need to get details as the organization's architecture maturity level increases. They may easily end up spending their time defining and refining these processes because it is not clear yet what to govern. The Effort Blackhole starts to form when the EA lead insists that all tasks in the Preliminary Phase must be completed before moving on to the next phase.

Another example is also in the Preliminary Phase of the ADM, which defines a tailored architecture framework as one of its outputs. A tailored architecture framework includes the following:

  • A tailored architecture method
  • Tailored architecture content (deliverables and artifacts)
  • Architecture principles, including business principles
  • Configured and deployed tools

That is according to section 5.4 in Chapter 5 in the TOGAF® online documentation (https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap05.html). If this statement is not handled properly by the lead enterprise architect, it can result in a massive scope creep that can keep the entire team of architects busy for months in tailoring the architecture framework they plan to use. The EA team can easily end up building a new EA framework instead of following TOGAF® to deliver EA artifacts, that is, being trapped in another Effort Blackhole.

The last example I will mention in this context is in phase B (Business Architecture), which takes Business Principles, Business Goals, and Business Drivers as inputs (https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap07.html). These elements can usually be found in the organization strategy, and if they are not, the architecture team will find themselves busy redefining (or just refining in the best case) the organization strategy, which is a project by itself and can lead to another massive scope creep and distraction to the team from their main EA objectives.

The lack of practicality

Another big problem that enterprise architects deal with when they plan to follow and implement TOGAF® is the lack of practical examples and document templates to use. Most frameworks impart theoretical information only to remain as generic and as neutral as possible. This leaves architects with huge gaps between the theory and the practice and in some cases, they deliver documents and presentations that are very theoretical and disconnected from the real world. This situation makes stakeholders perceive the EA office as the ivory tower office, indicating its disconnect from reality.

TOGAF® is full of terminologies that are either all new to many stakeholders or are defined slightly differently from other standards. For example, the definitions of object and service according to TOGAF® – and ArchiMate® – are a bit different from how Object Management Group (OMG) defines these two keywords. This usually confuses the stakeholders and results in the enterprise architects communicating using a language that no one else understands and delivering presentations that no one gets.

High cost-to-value ratio

Enterprise architects usually charge high rates and EA projects take long periods of time before anyone sees tangible deliverables, especially if done in a waterfall approach. According to the Glassdoor careers website, the average annual salary of an enterprise architect is about $110,000 in the United States (https://www.glassdoor.com/Salaries/enterprise-architect-salary-SRCH_KO0,20.htm). This number is an average and can go up to $220,000 per year for a senior director enterprise architect position according to the same source. If you have a team of four working in your EA office, that will cost your organization nearly $1 million per year if we consider the additional benefits and cost overheads. Additionally, most EA tools are very costly to procure with average license prices of around $10,000 per user (we will talk about EA tools later in this chapter).

Taking into consideration all the aforementioned points, the outcomes of EA projects can be bulky documents that are expensive, theoretical, boring to read, difficult to understand, and do not help in resolving any of the ongoing issues. The decision-makers find it difficult most of the time to justify huge EA investments for the relatively small added value.

TOGAF® is mostly adopted by IT people

Even though EA is an enterprise-level practice and aims to align business and IT within the organization, the reality is that it has mostly been adopted by IT people. This by itself is not an issue because life is full of examples of people who succeeded in different careers and people who quickly gained the required skills and expertise in new domains. IT professionals have always proven that they can lead the trending wave even if it is not just for IT – project management and EA are two examples of that.

The real issue is that IT enterprise architects kept focusing on IT operation and software development, and for them, every deliverable or artifact must serve as an IT solution. You can see this very clearly when browsing the job descriptions of enterprise architect positions on any recruitment website. You will see that most of the offered positions are titled enterprise architect, but the description is mainly looking for deep software development and programming skills or core network operations skills. This usually ends up with EA as a subdivision under the IT unit and the enterprise architect reporting to the IT manager or the Chief Technology Officer (CTO) in the best-case scenario. EA in this case will be limited to IT and will fail to achieve the most important goal it is established for, which is bridging the gaps between business and IT and aligning IT to business strategies.

After having this quick overview of TOGAF®, highlighting its benefits and drawbacks, it is time to introduce a solution that utilizes all of the benefits keeping you away from the drawbacks.

Left arrow icon Right arrow icon
Download code icon Download Code

Key benefits

  • Discover the various artifacts that enterprise architects need to develop for stakeholders to make sound decisions
  • Build a functional enterprise architecture repository that is rich in information, references, and metamodels
  • Learn how to use Sparx Enterprise Architect from scratch

Description

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.

Who is this book for?

This book is for enterprise architects at all architectural layers and practices of any maturity level. Many of the artifacts suggested in this book are inspired by The Open Group Architecture Framework (TOGAF®); however, familiarity with TOGAF® is not required. Whether you work within the business, applications, data, or technology layers, this book covers examples that apply to your work. Although not mandatory, experience modeling in Sparx Systems Enterprise Architect using any modeling language will be helpful. No prior knowledge of ArchiMate® is required to get started with this book.

What you will learn

  • Discover how enterprise architects can contribute to projects and departments within organizations
  • Use Sparx Enterprise Architect to build a rich architecture repository
  • Learn about the ArchiMate® 3.1 specification as you apply it in real-world projects
  • Use the focused metamodel technique to build the information necessary for maintaining your repository s consistency and accuracy
  • Understand the importance of keeping architectural artifacts simple yet eye-catching
  • Define an operational model that fits your initial needs and expands as required

Product Details

Country selected
Publication date, Length, Edition, Language, ISBN-13
Publication date : May 13, 2022
Length: 412 pages
Edition : 1st
Language : English
ISBN-13 : 9781801072762
Vendor :
Microsoft
Category :
Tools :

What do you get with eBook?

Product feature icon Instant access to your Digital eBook purchase
Product feature icon Download this book in EPUB and PDF formats
Product feature icon Access this title in our online reader with advanced features
Product feature icon DRM FREE - Read whenever, wherever and however you want
Product feature icon AI Assistant (beta) to help accelerate your learning
OR
Modal Close icon
Payment Processing...
tick Completed

Billing Address

Product Details

Publication date : May 13, 2022
Length: 412 pages
Edition : 1st
Language : English
ISBN-13 : 9781801072762
Vendor :
Microsoft
Category :
Tools :

Packt Subscriptions

See our plans and pricing
Modal Close icon
$19.99 billed monthly
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Simple pricing, no contract
$199.99 billed annually
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just $5 each
Feature tick icon Exclusive print discounts
$279.99 billed in 18 months
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just $5 each
Feature tick icon Exclusive print discounts

Frequently bought together


Stars icon
Total $ 186.97
Hands-On Software Architecture with Java
$54.99
Practical Model-Driven Enterprise Architecture
$41.99
Solutions Architect's Handbook
$89.99
Total $ 186.97 Stars icon

Table of Contents

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

Customer reviews

Top Reviews
Rating distribution
Full star icon Full star icon Full star icon Full star icon Half star icon 4.3
(7 Ratings)
5 star 71.4%
4 star 14.3%
3 star 0%
2 star 0%
1 star 14.3%
Filter icon Filter
Top Reviews

Filter reviews by




Cirby Oct 11, 2022
Full star icon Full star icon Full star icon Full star icon Full star icon 5
I have been practicing enterprise architecture(EA) for a good while and have purchased many books looking for a better way to explain the value and methodology of EA. Especially important is how the use of a shared repository with agreed upon deliverables to document our EA process would help us in our work. I needed something ‘down to earth’, i.e. practical and I think this book really helped me in that regard.I found the practice scenarios in Chapter II extremely helpful in naming and describing the development of architecture documents along with their interface to the repository.Especially interesting to me was the connection made to User Stories. How to relate EA and its artifacts to the Agile methodology is not well understood and the identification of corresponding user stories was a real bonus.I bought the book looking for a way to improve the practice of EA at my firm and this book was really helpful to me and my colleagues with whom I shared it.The book is ‘practical’ as advertised and it did help me improve the day-to-day work that I do.
Amazon Verified review Amazon
Dr. Christoph F. Strnadl Jun 12, 2022
Full star icon Full star icon Full star icon Full star icon Full star icon 5
This is a superb, lively, easy to follow, step-by-step, and comprehensive introduction into the most relevant Archimate 3.1 concepts using Sparx Systems’ Enterprise Architect (“Sparx EA”) as the underlying repository-based modelling tool. It is targeted primarily towards novice or early-stage enterprise architects who may want to get kick-start or rejuvenate their enterprise architecture work practices; more seasoned architects will find the book helpful if they need to turn to Archimate for the first time or when revisiting or reusing the standard after some hiatus.I especially liked the no-nonsense, down-to-earth language of the authors who thereby manage to link the (somewhat lofty and theoretical, I am ready to admit) concepts of TOGAF and Archimate to real-world situations enterprise architects and their stakeholders undoubtedly will encounter. All of the theoretical architectural deliberations are immediately modelled in Sparx EA – so the readers will also get a very good practical introduction into this tool as a by-product of studying the examples.The effectiveness of their approach especially for not so experience enterprise architects lies in the fact that they use a common (simplified, but realistic!) example enterprise as the concrete backdrop against which they construct use cases and problems for the enterprise architect to address and to solve. This allows them to clearly explain and demystify many of the seemingly superficial concepts of Archimate such as capability, function, service, or node, by relating metamodel terms directly to their exemplar company setting. Furthermore, they also introduce the concept of so-called “focused metamodels” (for Archimate) where they choose the most relevant entities of the various Archimate layers (application, technology & physical, business layer including strategy & implementation) such as “application component”, “node”, “business service”, “node”, or “gap”) and diagrammatically depict the most important typical relations this entity possesses in the Archimate metamodel. This very nicely complements the approach of the Archimate standard’s own documentation which typically depicts many entities and their respective relations for a single layer.I have actually studied and used the original Archimate standard which really is not such a bad piece to read but, alas, it’s a standard and, as such, has to be precise and not enjoyable. But reading the exposition and explanations of this book it was (almost) entertaining to get to know the authors’ opinion on how to actually use the concepts in practice. In passing, they also give crucial pieces of modelling advice, for instance, that contrary to their common name, “microservices” have to be modelled as “application components” in Archimate and rather not as “application services”: They also make the reader understand the (important) difference between these two concepts.While the book certainly is also attractive to any reader interested in doing enterprise architecture with the Archimate 3.1 standard alone, its greatest strength lies in the swiftness with which it links its architectural and modelling advice to the Sparx EA tool. Besides an excellent, step-by-step introduction on how to use the (admittedly, really powerful) modelling tool (including all relevant screen shots), the book also touches often overlooked but extremely helpful concepts Sparx EA supports such as switching to the list view or matrix view of diagrams, hierarchically linking diagrams, using layering and filtering to manage diagram complexity, importing XLS files containing architecture-relevant artifacts and relationships, and generating reports and publishing models. Because enterprise architects continuously deal with “as-is”, “to-be”, and several transition architectures at the same time, a dedicated section on how to efficiently model this is in Sparx EA is very welcomed. All of the described diagrams can be (freely) downloaded from GitHub in the form of chapter-specific Sparx EA repositories – a nice additional service for the readers!In addition, the book contains many very helpful pieces of advice to novice or early-career architects such as fitting all diagrams on a single page or spitting the view, aligning similar artifacts for better readability, or using a “sandbox” branch of an architecture as a playground for testing and parallel architecture development – all well-established and proven practices for decades! The book deservedly will get a prominent spot right between my Archimate 3.1 standard and Lankhorst’s more academic “Enterprise Architecture at Work”.Finally, I am confident that readers of “Practical Model-Driven Enterprise Architecture” will be able to understand, use, and appreciate Archimate’s intricacies and broad applicability much better and much faster than just by trying and experimenting with this powerful enterprise architecture modeling standard and method alone.
Amazon Verified review Amazon
Timothy D. Jul 12, 2022
Full star icon Full star icon Full star icon Full star icon Full star icon 5
Great Architecture book that delves into bridging actual implementation of an Architecture Framework and a Tool. There are many books on Architecture Frameworks, and there are many tool specific books, but very few that explain how to implement a framework in a tool.Mudar and Williams have taken the ArchiMate 3.1 Framework which can be easily transposed onto other modeling standards such as UML, TOGAF, BPMN and created a step by step process for implementing a repository. As most tools are fairly similar for modeling, I would recommend this book for those that are using other UML Modeling tools as well.Very well written as it takes a standard (ArchiMate) and shows how to implement using an imaginary shipping company. If you do not know ArchiMate, this book is a great introduction. If you do, this book is a very good implementation guide.Finally, one of the best parts of this book is the guides for implementing architectural frameworks in a repository. If you use another framework, and even another tool, the best practices in implementing a repository make this book valuable for starting up a new architectural repository (or optimizing one currently in use).
Amazon Verified review Amazon
Dr. Christoph F. Strnadl Jun 13, 2022
Full star icon Full star icon Full star icon Full star icon Full star icon 5
This is a superb, lively, easy to follow, step-by-step, and comprehensive introduction into the most relevant Archimate 3.1 concepts using Sparx Systems’ Enterprise Architect (“Sparx EA”) as the underlying repository-based modelling tool. It is targeted primarily towards novice or early-stage enterprise architects who may want to kick-start or rejuvenate their enterprise architecture work practices; more seasoned architects will find the book helpful if they need to turn to Archimate for the first time or when revisiting or reusing the standard after some hiatus.I especially liked the no-nonsense, down-to-earth language of the authors who thereby manage to link the (somewhat lofty and theoretical, I am ready to admit) concepts of TOGAF and Archimate to real-world situations enterprise architects and their stakeholders undoubtedly will encounter. All of the theoretical architectural deliberations are immediately modelled in Sparx EA – so the readers will also get a very good practical introduction into this tool as a by-product of studying the examples.The effectiveness of their approach especially for not so experience enterprise architects lies in the fact that they use a common (simplified, but realistic!) example enterprise as the concrete backdrop against which they construct use cases and problems for the enterprise architect to address and to solve. This allows them to clearly explain and demystify many of the seemingly superficial concepts of Archimate such as capability, function, service, or node, by relating metamodel terms directly to their exemplar company setting. Furthermore, they also introduce the concept of so-called “focused metamodels” (for Archimate) where they choose the most relevant entities of the various Archimate layers (application, technology & physical, business layer including strategy & implementation) such as “application component”, “node”, “business service”, “node”, or “gap”) and diagrammatically depict the most important typical relations this entity possesses in the Archimate metamodel. This very nicely complements the approach of the Archimate standard’s own documentation which typically depicts many entities and their respective relations for a single layer.I have actually studied and used the original Archimate standard which really is not such a bad piece to read but, alas, it’s a standard and, as such, has to be precise and not enjoyable. But reading the exposition and explanations of this book it was (almost) entertaining to get to know the authors’ opinion on how to actually use the concepts in practice. In passing, they also give crucial pieces of modelling advice, for instance, that contrary to their common name, “microservices” have to be modelled as “application components” in Archimate and rather not as “application services”: They also make the reader understand the (important) difference between these two concepts.While the book certainly is also attractive to any reader interested in doing enterprise architecture with the Archimate 3.1 standard alone, its greatest strength lies in the swiftness with which it links its architectural and modelling advice to the Sparx EA tool. Besides an excellent, step-by-step introduction on how to use the (admittedly, really powerful) modelling tool (including all relevant screen shots), the book also touches often overlooked but extremely helpful concepts Sparx EA supports such as switching to the list view or matrix view of diagrams, hierarchically linking diagrams, using layering and filtering to manage diagram complexity, importing XLS files containing architecture-relevant artifacts and relationships, and generating reports and publishing models. Because enterprise architects continuously deal with “as-is”, “to-be”, and several transition architectures at the same time, a dedicated section on how to efficiently model this is in Sparx EA is very welcomed. All of the described diagrams can be (freely) downloaded from GitHub in the form of chapter-specific Sparx EA repositories – a nice additional service for the readers!In addition, the book contains many very helpful pieces of advice to novice or early-career architects such as fitting all diagrams on a single page or spitting the view, aligning similar artifacts for better readability, or using a “sandbox” branch of an architecture as a playground for testing and parallel architecture development – all well-established and proven practices for decades! The book deservedly will get a prominent spot right between my Archimate 3.1 standard and Lankhorst’s more academic “Enterprise Architecture at Work”.Finally, I am confident that readers of “Practical Model-Driven Enterprise Architecture” will be able to understand, use, and appreciate Archimate’s intricacies and broad applicability much better and much faster than just by trying and experimenting with this powerful enterprise architecture modeling standard and method alone.
Amazon Verified review Amazon
Howard Bolling May 30, 2022
Full star icon Full star icon Full star icon Full star icon Full star icon 5
I've been in environments with failed EA practices, with struggling EA practices, with developing practices, and with none at all. Practical Model-Driven Enterprise Architecture is helpful in all of them.The "middle-out" organization of the book couples effectively with the increasing levels of detail as you build a metamodel of a business and gain the skills to implement a business model as an Enterprise Architect, a Solution Architect, or a Business Architect. Mudar's use of the Archimate standard provides a foundation to build on either with the tool he describes in the book or with other available, low-cost tools.If you're curious about how to implement an effective Enterprise Architecture, this book is an invaluable introduction and reference. Although it doesn't provide a guide for navigating the politics and organizational stresses of an EA implementation, its comprehensive explanation of models provides a valuable backdrop for architects implementing EA, rather than just talking about it.I bought the paperback format because I hang sticky notes off pages for easy reference, and the book's physicality forces me to take my hands off the keyboard and my brain off the minutiae. The sheer amount and interrelatedness of the reference material, though, begs for the Kindle edition.
Amazon Verified review Amazon
Get free access to Packt library with over 7500+ books and video courses for 7 days!
Start Free Trial

FAQs

How do I buy and download an eBook? Chevron down icon Chevron up icon

Where there is an eBook version of a title available, you can buy it from the book details for that title. Add either the standalone eBook or the eBook and print book bundle to your shopping cart. Your eBook will show in your cart as a product on its own. After completing checkout and payment in the normal way, you will receive your receipt on the screen containing a link to a personalised PDF download file. This link will remain active for 30 days. You can download backup copies of the file by logging in to your account at any time.

If you already have Adobe reader installed, then clicking on the link will download and open the PDF file directly. If you don't, then save the PDF file on your machine and download the Reader to view it.

Please Note: Packt eBooks are non-returnable and non-refundable.

Packt eBook and Licensing When you buy an eBook from Packt Publishing, completing your purchase means you accept the terms of our licence agreement. Please read the full text of the agreement. In it we have tried to balance the need for the ebook to be usable for you the reader with our needs to protect the rights of us as Publishers and of our authors. In summary, the agreement says:

  • You may make copies of your eBook for your own use onto any machine
  • You may not pass copies of the eBook on to anyone else
How can I make a purchase on your website? Chevron down icon Chevron up icon

If you want to purchase a video course, eBook or Bundle (Print+eBook) please follow below steps:

  1. Register on our website using your email address and the password.
  2. Search for the title by name or ISBN using the search option.
  3. Select the title you want to purchase.
  4. Choose the format you wish to purchase the title in; if you order the Print Book, you get a free eBook copy of the same title. 
  5. Proceed with the checkout process (payment to be made using Credit Card, Debit Cart, or PayPal)
Where can I access support around an eBook? Chevron down icon Chevron up icon
  • If you experience a problem with using or installing Adobe Reader, the contact Adobe directly.
  • To view the errata for the book, see www.packtpub.com/support and view the pages for the title you have.
  • To view your account details or to download a new copy of the book go to www.packtpub.com/account
  • To contact us directly if a problem is not resolved, use www.packtpub.com/contact-us
What eBook formats do Packt support? Chevron down icon Chevron up icon

Our eBooks are currently available in a variety of formats such as PDF and ePubs. In the future, this may well change with trends and development in technology, but please note that our PDFs are not Adobe eBook Reader format, which has greater restrictions on security.

You will need to use Adobe Reader v9 or later in order to read Packt's PDF eBooks.

What are the benefits of eBooks? Chevron down icon Chevron up icon
  • You can get the information you need immediately
  • You can easily take them with you on a laptop
  • You can download them an unlimited number of times
  • You can print them out
  • They are copy-paste enabled
  • They are searchable
  • There is no password protection
  • They are lower price than print
  • They save resources and space
What is an eBook? Chevron down icon Chevron up icon

Packt eBooks are a complete electronic version of the print edition, available in PDF and ePub formats. Every piece of content down to the page numbering is the same. Because we save the costs of printing and shipping the book to you, we are able to offer eBooks at a lower cost than print editions.

When you have purchased an eBook, simply login to your account and click on the link in Your Download Area. We recommend you saving the file to your hard drive before opening it.

For optimal viewing of our eBooks, we recommend you download and install the free Adobe Reader version 9.