From the course: Complete Guide to Open Source Security
Architecting with ArchiMate
From the course: Complete Guide to Open Source Security
Architecting with ArchiMate
- [Instructor] The need to have central oversight of technology evolved as the deployment of technology into organizations became more pervasive. This is achieved by adopting what is known as an enterprise architecture. The enterprise architecture ensures that the technology is not only effective at the individual business process level, but also is interoperable across the enterprise through adoption of common standards. Furthermore, by leveraging shared systems where appropriate across the enterprise, we can ensure technology is cost effective. The ArchiMate tool is a well known and commonly used open-source enterprise architecture tool. It's used to create models of the enterprise from the business goals down to the individual technology and application components used in the business. Let's see how it works. We can select the Linux version, download it, and unpack it. I've downloaded it, so let's unpack it using tar. Okay, we can now go into the Archi fold and run it by calling Archi.sh. And here we have the welcome screen. Let's see how we might model a digital strategy. We'll create a new ArchiMate model, and we'll put our digital strategy in using a course of action, and we'll change the title to Digital Strategy. We can see that the details below have our digital strategy showing, and we can provide a description, properties and so on. You might like to pause the course and take a couple of minutes to check out the details that can be added. We'll now add a capability below it and we'll call it Digital Customer Management, and we'll connect it with a realization arrow. Next, we'll add a grouping and we'll change its name to reflect that it holds the expanded Digital Customer Management Capability. And we'll connect it with the realization arrow. In the grouping, we'll add a business service and we'll call it Online. And then we'll add a business process and realize it. And we'll add an application component and we'll call it Portal and we'll connect it with a serving arrow. Okay, we now have our first application service modeled. Let's now add another service and call it Customer Service. And we'll put in a business process. And again, we won't bother adding a name to that, but we'll put a realization relationship. And we'll add another application component and we'll call it CRM. And we'll put a serving relationship from the CRM to the Business Process. And in between them, we'll add another application component, which we'll call ERP. We'll connect it to both processes using serving arrows. Okay, to finish off, we'll add a business actor to the right of our Customer Service process, and we'll call it Customer Support Team. And we'll connect it to the business process through an assignment. Okay, so let's save our model as model1 and leave our modeling there for the moment.
Contents
-
-
-
-
(Locked)
Introduction to GRC1m 13s
-
Architecting with ArchiMate5m 52s
-
(Locked)
Modelling security with Archi2m 22s
-
(Locked)
Adding security to the model3m 27s
-
(Locked)
Security risk management with SimpleRisk3m 9s
-
(Locked)
Taking SimpleRisk for a spin7m 34s
-
(Locked)
Using eramba for GRC4m 18s
-
(Locked)
Configuring the eramba system8m 31s
-
(Locked)
Preparing your risk context9m 11s
-
(Locked)
Setting up your assets3m 15s
-
(Locked)
Entering risks into eramba3m 35s
-
(Locked)
-
-
-
-
-
-
-
-
-
-
-
-