ArchiMate Modeling Tutorial

ArchiMate Modeling Tutorial 01 - Basic Viewpoint 01 Organization Pattern

AI-generated summary and notes. Check quotations, numbers, and important claims against the source video. Captions may contain errors.

Watch the source video on YouTube

Estimated reading time: 19 minutes for the text on this page.

Summary

This tutorial, presented by Yasen, covers the basics of ArchiMate modeling with a focus on organizational patterns. It starts with a brief introduction to how the framework is structured with various layers like business, application, and technology. The tutorial specifically delves into creating organizational viewpoints using ARIS, highlighting how elements like actors and departments are modeled. It also touches on color coding schemes and relationships between different elements. Practical demonstrations show how to manipulate the model, and the tutorial provides tips for alignment and organization of components.

Highlights

Introduction to ArchiMate modeling and its layers 🎨.
Focus on organizational viewpoint modeling using ARIS 🏢.
Discussion on horizontal and vertical layers 🔄.
Explanation of color schemes and relation types 🖍️.
Practical demos on manipulating organizational models 🎬.
Understanding of aggregation vs. composition in relationships ⚖️.
Alignment tips and size matching for diagrams 🔧.
Title and label customization techniques 🏷️.

Key Takeaways

Learn about the basic viewpoints in ArchiMate modeling 🎨.
Understand the structure of ArchiMate framework layers 🧩.
Discover how to model organizational elements using ARIS 🏢.
Master color coding for ArchiMate 3.1 🌈.
Get tips on relationship management and alignment in modeling 🔗.
Practical demonstrations for hands-on learning 🎬.
Explore different colors and positions for clarity and organization 🖌️.
Understand the importance of relationships and element meanings over position ⚖️.
Discover how to manipulate and manage models effectively 🛠️.
Learn to set up clear titles and labels in your diagrams 📌.

Overview

The video opens with an introduction to ArchiMate modeling, breaking down the basic structure and layers within the framework. This includes discussing the business, application, technology, strategy, and motivation layers. The tutorial is aimed at helping viewers understand how these layers build upon each other to create a comprehensive viewpoint.

A significant portion of the tutorial focuses on the organizational viewpoint of modeling. Using ARIS, Yasen demonstrates how to model actors, departments, and various elements. This hands-on demonstration provides practical insights into the structuring and relationship of organizational components, offering useful tips for alignment and deployment of different elements.

The tutorial also dives into nuances such as color coding, emphasizing the importance of visual clarity and distinction in diagrams. Yasen explains the specific meanings behind different relationship types like composition and aggregation, and how these contribute to more accurate modeling. The video concludes by showcasing how to manage and customize titles and labels for a professional finish.

Chapters

00:00 - 00:30: Introduction to ArchiMate Modeling The introduction sets the stage for a series on ArchiMate modeling. It assumes that viewers have already familiarized themselves with background information provided in previous materials. The focus of this chapter is on detailed modeling using the ArchiMate framework, as guided by a Spark tutorial.
00:30 - 03:00: Overview of ArchiMate Layers and Colors The chapter "Overview of ArchiMate Layers and Colors" introduces viewers to 12 different views, based on the Sparks shared tutorial, and emphasizes the use of Ary for modeling. The focus is on presenting and modeling the organization.
03:00 - 07:00: Creating an Organization Viewpoint The chapter discusses the concept of organization viewpoints in Archimate, specifically focusing on Sparks systems. It explains the basic horizontal and vertical layers represented in Archimate, namely the business layer, application layer, and technology layer. Additionally, it mentions three types of elements: passive structure, active structure, and behavior, often referred to as the 'trios' or 'triple step'. The chapter aims to provide a foundational understanding of how these elements and layers interact within an organization's architecture.
07:00 - 14:00: Relationship Management in ArchiMate The chapter discusses the ArchiMate framework, focusing specifically on relationship management. ArchiMate situates itself above business, adding elements such as strategy, capability, value stream, resources, and courses of action. It incorporates technology, while also adding aspects related to physical and implementation migration. Three verticals are maintained, and a motivation layer is additionally included in the framework. The chapter likely details these layers and their interactions within ArchiMate.
14:00 - 19:00: Finalizing the Organization Pattern Model This chapter discusses the organization pattern model focusing on its layers and the use of colors. It introduces the basic and additional layers, while providing a description of each. The text also highlights the use of various colors such as blue, green, white, light gray, medium gray, and dark gray in these layers, indicating how color is applied within the model.
19:00 - 25:00: Adding Titles and Labels The chapter focuses on adding titles and labels with a specific emphasis on a matrix format that involves horizontal and vertical alignment. The motivation behind this lies within the context of the 'open group' related to architecture and model development. The chapter also touches upon ArchiMate's development, which entails defining viewpoints, specifically organizational viewpoints, to facilitate structured modeling. It suggests a methodical approach in defining these elements 'one by one.'
25:00 - 27:00: Conclusion and Next Steps The chapter discusses creating a pattern to create elements and a diagram that describe the roles and actors within an organization, entity, or a part of an organization, such as a department or section. It explains how this pattern can be used to model an entire enterprise organization, a business unit, or even smaller segments, like a department or a sub-team. The discussion emphasizes the flexibility of this pattern in modeling various levels of organizational structure.

ArchiMate Modeling Tutorial 01 - Basic Viewpoint 01 Organization Pattern Transcription

00:00 - 00:30 [Music] [Music] hello everyone uh welcome back I hope you got enough background information about this serious videos about uh archimate modeling based on spark tutorial introduction so from this video is we move to those detail modeling uh
00:30 - 01:00 the demos uh so starting from this basic wave point there's 12 different uh views uh and this uh is coming from the Sparks shared tutorial and we will use Ary to to do this so this video we focus on how to uh present uh and model the organization so let's go to the content directly so if you come to this tutorial here
01:00 - 01:30 is uh the Sparks uh systems they show you is what this basic horizontal and vertical layers about archimate so structure is originally is just a business layer application layer technology layer and they have these three types of the element passive active structure and in the middle is a behavior this like that uh the three uh the trios three step triple as well uh
01:30 - 02:00 and then the full archimate framework is above business there's adding the strategy uh like capability value stream uh resource course of actions and both uh below the technology also add physical and implementation migration these three vertical are still keep and also uh additionally adding the motivation layer so if you come to the uh R key to you may see all these layers
02:00 - 02:30 uh spark EA also have those and you can read these uh a description for each layer uh the additional layer and the basic layer is uh here uh and then the uh use of colors uh layer is the use color blue green so like uh these uh different colors aspect is white light gray medium gray dark gray so
02:30 - 03:00 uh those are the uh this Matrix uh horizontal and vertical uh and the mo motivation is just white uh and within the open group and tograph when they develop archimate they also develop uh the relationship we will mention that during our modeling uh and uh uh those with point is one by one is we are starting to uh Define that uh in AR to so first is this organization Viewpoint
03:00 - 03:30 uh this kind of pattern create elements and a diagram that describe the role and actors of an organization or ENT entity or part of a organization such as a department or section so uh you can use this to model the whole uh the this Enterprise uh organization or you can come to our business unit or even like is when it come to a department you can even uh model the team the sub team uh
03:30 - 04:00 and then this uh you can also use the same actor to model the individual so uh is not have any limitation is on which layer you will have those uh uh this notations uh used uh so you can use that on the many different uh levels uh and uh we first is let's draw this one so as I mentioned is uh this is the ary2 uh my
04:00 - 04:30 current version is the recent released 5.4.0 so if you go to the AR key uh the uh the site is uh you will get uh this uh this tool I hope is you already uh uh install that and uh you don't need any additional uh the this uh plugins uh so uh you just have only AR is fine so you can use the new empty model or you can click this one empty model so this icon
04:30 - 05:00 then we we will see here is uh let me put that is 01 organization and let's see that is the pattern so we build this as a pattern and we also put this uh uh let's uh use the same name as overview when you click the empty one
05:00 - 05:30 you can see these icons coming so less familiar with those is these are the strategy layer uh for this uh folder these are the business layer these are application technology physical implementation and migration uh the bottom one uh is migration uh and this one uh sorry this one is the motivation this is the implementation and the migration so uh all these are the uh
05:30 - 06:00 comply with this uh color uh scheme all the color coding published by the uh this archimate 3.1 uh there's also another uh the color plate is published by uh the this uh archimate uh so let me show you that uh I uh if you search is my other serious the book uh course all
06:00 - 06:30 uh the videos you can find is a cookbook uh I put a reference here uh so here is the archimate classic uh color so I will put these uh two files also in this new repository so that you can find that as well so this is the you can say classic uh the the color scheme uh and archimate is also gave you our alternative
06:30 - 07:00 color set the if you uh want to have a different uh color coding uh the most useful here is this uh color uh the numbers so use these uh uh the different color code uh you can exactly uh get this uh color that 100% the same as the archimate needed so I think it's uh here I think unfortunately this classic doesn't have this color coding uh but I
07:00 - 07:30 believe you can extract those uh colors directly all is uh the current uh the archimate to is already used uh good enough this uh color coding uh some color May slightly difference on this tutorial from this ea uh the Sparks to uh but uh I believe you can recognize that they are not too big difference so first of of all is uh we have uh three
07:30 - 08:00 levels on this uh pattern so all of them are used business actor so you drag this one so we call that is business actor one that is our highest level uh and we have our three business actor so uh one is this A.1 we treat this this a as the company name so now you have are uh a.2 a.3 so
08:00 - 08:30 let me see so a do 3 a.2 and on every uh the this uh where you can trade that as the department uh you uh have another one so I don't need this I think is I have three uh three s of this enough so this one this
08:30 - 09:00 one okay you can see here now is uh we can uh change the name is this is the A1 one a12 1 three four
09:00 - 09:30 2.2 this is a.2 so you you may see here is uh I happened uh to see these are the exact same name that is allowed in uh ar2 because these are uh only on this label you all you can see is on this display the name they are duplicate but actually they have the totally different unique ID uh in the mode model so I also
09:30 - 10:00 have some practical demos to show you is what behind on this AR key uh modeling tool so you can see the uh s this source code and you can also manage this source code uh through this changing on certain line of code is uh you can uh make this uh the frontend change uh in the model so as long as you are familiar with those XML based uh uh Source uh source
10:00 - 10:30 code you can play around on do background then you can see here uh we have these uh four departments or sub department so you can make them uh drag like this way so here I put that not uh too much uh care about their alignment so uh as long as you can put that roughly okay then that's uh is fine uh
10:30 - 11:00 that is again uh is one philosophy is for modeling in Arch is uh the actual uh position uh all this uh uh position in one of whe is not too much uh the important if you put that a little right or a little closer uh that that is fine uh the more important is when you build up your the this model
11:00 - 11:30 is the two parts one is the meaning of your Source or destinations uh elements uh what's that representing uh the second is the relationship uh relationship means is what's the connections meaning uh those are all this uh important uh meaning that we need to uh consider more than uh just care about the position of one element in one view that is totally less uh important uh and I can build this uh
11:30 - 12:00 drag this as a bigger and you can select this uh uh the number seres and putting them inside when you put them uh inside you will be ask is what kind of the relations you will build between those lower level business actor to higher level business actor you can click here to see is there's a some allowed or valid uh relationship uh the top
12:00 - 12:30 recommended is the composition and the second is aggregation and the specialization so you can choose e uh either of them or you can just accept this composition and aggregation they have a different meaning composition is more stronger than the uh aggregation and they are represented like this number two so this solid dount with our solid link uh so but if you make them
12:30 - 13:00 Nate uh those link is not shown so that is the Mak sense uh so uh and you can read from the archimate language specification to understand is what are the uh these uh uh uh the meanings uh and the difference uh between those uh uh this aggregation compared to the composition uh and another part is I think is we have our uh the from this
13:00 - 13:30 edit in the AR to you can go to the preference uh and here I think is so we have our uh here so the AR RM which is the automatic relationship management this is are very uh useful things but I tend to keep that as our default uh so they have three parts is relation type offered when
13:30 - 14:00 creating new relation so that is the uh the why is the composition is above aggregation and also above specialization uh so uh within this default setting uh is not say uh show serving not show influence it's just those highlight things and why when we come to the business actor putting the another business actor you only say that
14:00 - 14:30 three uh so that is based on actually is this part so it's all the possible uh relation are showing here when we want to do the next uh but these are are only the allowed things so uh if I just let show you using this magic uh drag that uh you can see those are showing more because the all those are allowed uh but uh not all of them are allowed as the
14:30 - 15:00 nested relationship so you'll see that three so that is the thing is that you you can change that uh if you don't want to uh use the default so for example you can see I want to see only aggregation so I don't want to see the uh composition then you can uncheck the composition then that will not show uh and then this uh if I move to this department two or the business is actor two uh I don't want to use you can use
15:00 - 15:30 this way to drag that and find this uh but you you cannot do this at the same time on both the horizontal and the vertical uh so you can use one uh the tip is H choose this one use the shift or control click the target one you find this icon this icon means the match match size so when you click that is the your first element will match the size
15:30 - 16:00 to your second elements so that uh will give your convenience then you are okay to track uh this uh four the level three uh into this and then choose this uh click either one so click this then you have this department one then you can put this here uh and actually the D will is finishing your three departments uh and
16:00 - 16:30 then we have uh putting them closer uh and you don't need to expand this uh big enough first uh uh so you can just try select all as long as your CER can come inside so that means is uh you are going to put uh all of the selected element as a nested uh position into this uh uh
16:30 - 17:00 this highlight one so when you click all of this will be ask is A1 A2 A3 to be composed so just click that and you can see the their boundary so now it's easier for you to drag your uh bigger one to enough uh size uh to handle your the this uh uh the inside ones uh with this is we have provide the equivalent
17:00 - 17:30 modeling for what this spark uh tutorial uh provide to you uh one another thing is uh how about the title so uh I may use our label to make the title uh but I don't want to uh make our typing uh you definitely you can use uh here if you uh want to see the uh this one I want to see the text test then you can show that here uh
17:30 - 18:00 but that is not the actual title to maintain this uh I want this show just this views name then you can use a label expression uh I demo this in my other courses in quite detail way so just to show you if you uh don't uh know this yet so use a dollar like the JavaScript is uh to point to certain the variables
18:00 - 18:30 so uh and add a view view means is your variable uh is related to the Views uh uh the object so that will come to the view level then use this craes and uh WRA this name we start is your uh view name will be captured uh into this uh label uh so definitely is if you keep uh
18:30 - 19:00 F tune so you can go to the appearance and gave some uh the nice view like is I don't want dark ear uh I just wanted to see a n so there's a no dog ear anymore all you want to see is I want to see our rectangle so they have this Edge uh so normally so for our title we don't care about Edge uh and here is you can have a text position so
19:00 - 19:30 I by default is left and top so I put that both on the middle uh and I click uh this font make that in bold uh and also a little bigger so 10 bolt uh then that is becoming uh a little nice uh the text here uh so this is our way is you can uh put together of your uh diagram here uh and then uh we uh we already
19:30 - 20:00 duplicate that is uh you can read about those discussions uh to see uh some use cases for this organization pattern uh then this we finish this video and next video we uh will go to create our uh equivalent uh examples under the organization through some open samples so see you in the sample video bye for now for