WEBVTT 00:10.660 --> 00:16.180 OK, but again, that was storytelling, so now we're going to talk about a more specific technique 00:16.180 --> 00:20.210 they can use during the workshop if you get stuck in an area. 00:20.680 --> 00:25.480 So I call it using Ozbek diagrams as an example to exemplify. 00:26.680 --> 00:29.620 So complexity does not mean that is wrong. 00:30.820 --> 00:32.970 So stuff could be quite complex. 00:33.490 --> 00:34.980 I need to be prepared for that. 00:35.290 --> 00:37.720 So just because it's complex doesn't mean that is wrong. 00:37.900 --> 00:41.680 Of course, you should try to simplify as much as possible. 00:42.040 --> 00:44.110 But sometimes complexity is needed. 00:46.540 --> 00:55.360 However, to make complexity more easy to understand, you could utilize examples because when we are 00:55.360 --> 01:00.690 doing concept maps, we are actually mapping the concepts and not the concrete objects. 01:01.090 --> 01:08.350 But as I showed you and you know, you have the possibility to actually also map the objects and that 01:08.350 --> 01:09.890 can be quite useful. 01:11.380 --> 01:16.870 So among the objects of a real world scenario, it's easier to understand complex structures with many 01:16.870 --> 01:19.230 involved in direct, interrelated concepts. 01:19.240 --> 01:25.600 If you first understand kind of the ground zero level, which is the kind of the total picture or one 01:25.600 --> 01:26.900 specific example here. 01:27.850 --> 01:28.950 So take an example of that. 01:29.020 --> 01:37.690 And so this is a concept model about lowed, units that could be part of, for example, a logistics 01:37.690 --> 01:38.140 domain. 01:39.400 --> 01:44.590 So what I'm saying here that there is something called a load unit that could have a power type of load, 01:44.590 --> 01:46.540 unique types, Bitauto power types. 01:46.580 --> 01:47.680 We've talked about UML. 01:47.830 --> 01:48.480 Remember that? 01:49.240 --> 01:55.630 And that could be lowed unit type rule, and that is connecting different types together. 01:56.050 --> 02:01.990 And then different load units could have a load unit connection so they could be connected in some way. 02:02.140 --> 02:09.490 And the connection is actually regulated if it's well, if it's a valid or not valid connection, depending 02:09.490 --> 02:12.630 on if there exists the type rule for the loan units. 02:12.940 --> 02:21.370 And then there are the actual here's an incomplete set of the generalize generalizations of a load unit. 02:21.640 --> 02:27.280 So there are a truck, for example, or a package or a swap, but they are all different types of load 02:27.280 --> 02:27.700 units. 02:28.510 --> 02:33.450 And I can tell you that I can experience reading those type of models. 02:33.460 --> 02:40.230 I will understand this, but I know the people might have a problem understanding it, even if I, I 02:40.240 --> 02:46.330 can directly see that the this is a very powerful model and can be used to model very many concrete 02:46.330 --> 02:47.110 situations. 02:47.350 --> 02:49.810 So it's actually correct, but it's quite complex. 02:50.890 --> 02:56.080 So if you then run into situations, we actually need to create those models to have the flexibility 02:56.080 --> 03:01.690 in the model you would like to have, then you might need to be in place to actually give concrete examples 03:01.690 --> 03:05.250 so that people see that it's a valid way of thinking about it. 03:05.890 --> 03:09.700 So then go down to the most concrete examples here. 03:09.700 --> 03:15.730 So try to be as concrete as possible, like take up whatever you have in the room and start counting 03:15.730 --> 03:17.800 and saying here's a cup or whatever it is. 03:18.160 --> 03:22.240 So be down to serve your example. 03:22.270 --> 03:23.890 So let's say baseload units here. 03:23.890 --> 03:25.390 You actually take a few examples. 03:25.390 --> 03:29.980 You have SWAC body, you have a truck and you have a package right 03:33.220 --> 03:33.380 there. 03:33.410 --> 03:40.810 You're saying that we need to have some way of knowing how we can actually connect different types of 03:40.810 --> 03:41.970 load units together. 03:41.980 --> 03:45.170 So could I connect a package with a swap body? 03:45.220 --> 03:46.650 Yeah, let's say that's fine. 03:47.320 --> 03:49.930 Could I connect a swap buddy to a truck? 03:50.080 --> 03:51.940 Yeah, that should also be OK. 03:52.450 --> 03:55.230 But could I connect the package directly onto a truck? 03:55.510 --> 03:56.340 Probably not. 03:57.370 --> 04:04.540 So you see that the way how you connect the different types is something that is important. 04:05.200 --> 04:08.920 And that was the room that I showed you in the concept model. 04:09.580 --> 04:15.520 So here you can explain to people we need to know whether different connections between load units are 04:15.730 --> 04:20.140 OK or not, depending on some type of regulation framework. 04:22.030 --> 04:29.770 OK, so then the specification part of the load units here so we can have then this rule, which is 04:29.770 --> 04:34.600 then exemplified just as I as I wrote here, there's a swap body and truck. 04:34.990 --> 04:36.130 Yeah, that's one rule. 04:36.130 --> 04:39.910 Let's call it rule one, which is of the type load unit type rule. 04:40.180 --> 04:48.390 OK, that means that the load unit type truck could be connected to the load unit type swap body. 04:49.150 --> 04:55.150 OK, so here we have the two power types of two instances of the power type and then we have another 04:55.150 --> 04:59.580 rule saying the rule to load unit type rule. 05:00.160 --> 05:01.780 And that's the that's the class. 05:04.020 --> 05:11.670 We're saying that packages could be contained in swap bodies, OK, and that means that the swap body 05:11.850 --> 05:16.870 load union type is connected via a rule with the low union type package. 05:18.270 --> 05:18.800 Very good. 05:19.500 --> 05:21.890 So then I have a concrete configuration. 05:21.900 --> 05:28.920 So if that was my specification side, so before I even got a specific truck, I talked about the types. 05:29.100 --> 05:34.670 So he drove me back to the discussion of power types that we had when we talked about Yamal in general. 05:35.460 --> 05:39.930 So then let's say they have a specific truck, one that's my truck. 05:41.250 --> 05:46.080 And on this T1, I have one swap body, S.B one. 05:46.230 --> 05:46.580 Yeah. 05:46.920 --> 05:51.210 And so I have a connection between my truck and this specific swap body. 05:51.630 --> 05:56.840 And I also in this specific spot body, have one package, P1. 05:57.510 --> 06:01.250 So I also have a load unit connection between the swap body and the package. 06:01.740 --> 06:02.100 Right. 06:03.310 --> 06:07.500 And then actually the swap what I had another package as well as I actually had two packages in this 06:07.500 --> 06:09.840 swap body, so I have another load unit connection. 06:09.840 --> 06:11.130 We'd package P2. 06:12.120 --> 06:14.600 OK, so that aspecific configuration. 06:15.030 --> 06:21.360 Well we like to know here if this configuration is a valid configuration according to the specification, 06:22.470 --> 06:25.810 and then we need to find the actual connections here. 06:25.830 --> 06:27.640 So is this a valid configuration? 06:27.900 --> 06:32.430 Yeah, there's something called a truck and we have a prototype for that load. 06:32.430 --> 06:33.860 Unique type truck. 06:33.870 --> 06:34.650 That's fine. 06:34.680 --> 06:36.470 That's directly in the model. 06:36.480 --> 06:37.710 So here's the prototype. 06:39.340 --> 06:44.680 And we have the power type Facebook body and power type for truck for package as well down there, and 06:44.680 --> 06:49.480 we see that the first load, unique connection here between our truck and the specifics of our body 06:49.630 --> 06:56.380 is actually correct, because there is a rule in the specification saying that you could combine a load 06:56.380 --> 07:02.280 unit type truck with the load unit type swap body, and hence that connection is OK. 07:03.310 --> 07:10.570 And there's also the load utility package, which both package one and package two are the type of and 07:10.570 --> 07:16.120 there's also a load unit type rule specifying that you could have a connection between swap bodies and 07:16.120 --> 07:17.560 packages and hands. 07:17.740 --> 07:21.520 Those two connections are also correct and hence the whole configuration is correct. 07:22.630 --> 07:29.830 So you see now in this example, and this is an object model that you can reason about, that this is 07:29.830 --> 07:36.670 the way the world actually looks already in this domain, actually sees this knowledge and hence the 07:36.670 --> 07:39.970 model that we had, which was a little bit more complex. 07:41.740 --> 07:43.270 That is correct. 07:43.480 --> 07:47.320 So the question then is, is this now a little bit easier to understand? 07:47.350 --> 07:53.740 So here we see that we have the specification part of it to his right and we have a configuration part 07:53.740 --> 07:59.860 to the left and we see that the connection goes between the power type and the actual type of the load 07:59.860 --> 08:03.240 unit, the actual class of the load unit. 08:03.430 --> 08:10.540 And there is a connection between the actual configuration back to the specification that validates 08:10.540 --> 08:13.370 and the correctness of the connection. 08:14.230 --> 08:20.980 So I think that those two in combination, the omic diagram that you can then right up on the whiteboard 08:20.980 --> 08:27.640 while you're doing this modelling or you write it as a separate diagram and have in your model as well. 08:27.640 --> 08:36.310 So you can have multiple diagrams in the same model as we talked about, makes the class diagram easier 08:36.310 --> 08:39.490 to grasp and understand if you come into complex situations. 08:40.330 --> 08:46.780 So that was a concrete example how you can use objects, diagrams during your workshop and also when 08:46.780 --> 08:49.750 you document the model or the diagram you're doing. 08:49.750 --> 09:00.040 So I usually actually tend to do on big diagrams, on complex parts of my conceptual models and ship 09:00.040 --> 09:05.080 them in the documentation as well so that everybody can see how it actually works on the ground level. 09:07.480 --> 09:10.540 But again, that was using only diagrams. 09:10.730 --> 09:13.270 So now we're rushing to pattern recognition.