WEBVTT 00:10.450 --> 00:13.390 OK, great guidelines for packaging, then. 00:15.160 --> 00:21.910 So how do you go about so you know that you have this large set of elements, what's the first steps 00:21.910 --> 00:24.220 you do to try to find the packages? 00:24.280 --> 00:25.990 That's what we're going to talk about here. 00:27.790 --> 00:30.210 So let's take this concrete example. 00:30.760 --> 00:36.460 So we have load units of, for example, the subtypes train package, container truck. 00:36.970 --> 00:42.130 And we have a shipment that is including a number of shipped units. 00:42.520 --> 00:46.270 And it's the shipper that sent it to the receiver. 00:46.450 --> 00:48.460 And we can have different shipment types. 00:48.460 --> 00:52.960 And the receiver is a party who could be either a person or an organization. 00:53.110 --> 00:59.660 So this is just a sub set of all the classes, of course, needed in complete logistics domain. 01:00.880 --> 01:08.890 But let's say that we try to see if we can package these classes into some larger chunks. 01:11.560 --> 01:18.970 So you start by considering the uppermost class in each generalization or aggregate structure to a package. 01:19.810 --> 01:22.330 So do we have any generalizations going on here? 01:23.710 --> 01:26.680 Yeah, we have one here and we have one here. 01:27.250 --> 01:27.650 Right. 01:28.570 --> 01:29.830 So that's rule one. 01:31.660 --> 01:38.160 Then you consider each class not in a generalization or aggregate structure to a package. 01:38.380 --> 01:40.710 So let's see, which other classes do we have? 01:40.720 --> 01:43.210 We have shipment and shipment type. 01:43.210 --> 01:43.680 Right. 01:44.230 --> 01:49.930 Then you do three refine the packages by applying the whole part organization of the problem domain 01:49.930 --> 01:51.050 that its experts use. 01:51.380 --> 01:53.890 So you have to start thinking yourself and see that. 01:53.950 --> 02:01.420 Yeah, OK, I could have a shipment type package and a shipment package, but I know semantically that 02:01.420 --> 02:04.510 shipment types and shipments are very similar. 02:04.510 --> 02:04.870 Right. 02:05.440 --> 02:09.250 Or they're very connected, not similar, but they're very connected, of course. 02:10.870 --> 02:14.760 So that for I will actually consider them to be the same package. 02:16.510 --> 02:21.670 And then for I refine the packages for minimal interdependency between the packages. 02:22.030 --> 02:28.480 So I try to see how could I minimize the dependencies and this case, I think it's already good. 02:28.780 --> 02:32.670 That means that we should also have the shipment type and shipment in the same package. 02:33.070 --> 02:35.230 So that was kind of four easy steps here. 02:35.950 --> 02:39.050 So what will the result look like in this case? 02:39.670 --> 02:45.160 So this would actually result in three different packages, shipments package, a load Lajeunesse package 02:45.160 --> 02:46.400 and the party's package. 02:47.500 --> 02:49.720 Of course, this was a very simple example. 02:49.870 --> 02:55.330 And I sort of showed you when we now evaluating packages, you usually don't have just one or two classes 02:55.330 --> 02:55.900 in the package. 02:55.900 --> 02:59.590 You usually maybe have five or six or seven classes in a package. 03:00.040 --> 03:04.510 But also you can actually start finding packages top down very early on. 03:04.750 --> 03:09.130 And in that case, you can actually just have one or two classes because you know that they are going 03:09.130 --> 03:13.730 to contain more when you start documenting more and finding out more about the demand. 03:15.760 --> 03:22.030 But this was a very simple example of a kind of a four step rule that you use here. 03:22.450 --> 03:26.490 And in the next section, I'm going to talk about how you can evaluate packages better. 03:27.520 --> 03:28.000 Very good.