WEBVTT 00:00.360 --> 00:02.680 Now, we'll begin with the --. 00:02.890 --> 00:03.540 So far. 00:04.510 --> 00:08.800 This specific U.S. target will be to understand how we. 00:10.670 --> 00:13.130 Declared an implicit. 00:14.350 --> 00:22.390 V of mapping put in a structural modeling state, we will also understand how we can use an explicit 00:22.390 --> 00:29.320 way of mapping up to the different design, OK, how we can use and we to. 00:30.690 --> 00:34.770 IPA, that is IP integrated to simplify the structure modeling. 00:35.520 --> 00:36.390 And finally. 00:37.610 --> 00:41.660 Oh, how you handle defying. 00:43.470 --> 00:45.670 And I'll fine. 00:45.900 --> 00:53.040 OK, so these are the few things that will be understanding along with this, we will start with then 00:53.280 --> 00:54.300 structural. 00:56.480 --> 00:57.230 Malling. 00:58.840 --> 00:59.370 Style. 01:00.040 --> 01:04.780 OK, so these are the few things that you need to know to succeed in this section. 01:04.810 --> 01:09.220 OK, so will understand how we proceed with the structure model. 01:09.570 --> 01:14.080 OK, so the typical flu or typical cold that will be frequently finding. 01:14.240 --> 01:20.110 OK, then how you use a component and how you connect the food between the different components. 01:20.150 --> 01:24.700 OK, so connecting up what can happen with and implicitly or an explicit. 01:24.750 --> 01:26.380 We will understand both of them. 01:26.380 --> 01:31.510 In fact, when we are discussing about attachment, we have little to do about an implicit and explicit. 01:31.960 --> 01:38.110 OK, then we'll also understand how we can use a value API to really simplify the structure, let's 01:38.110 --> 01:38.240 say. 01:38.710 --> 01:45.810 Finally, the thing which you also need to focus is how you define how you handle the systems. 01:46.860 --> 01:53.340 And how you communicate between them when you have all the net which defined inside the system that 01:53.340 --> 01:58.260 you are building, or if you have a situation where you have someone defined it, how you handle the 01:58.260 --> 02:02.620 situation, you'll be finding when we work on a real scenario. 02:02.640 --> 02:07.080 So we work in a team where there are subsistent, which. 02:08.820 --> 02:12.810 I've been developed by different engineers working on the same system. 02:13.170 --> 02:19.230 Again, the final step is to merge an entire subsystem so that we get our complex system right. 02:19.470 --> 02:26.640 So all in all, the scenarios, when you are building a real scenario or real applications will be finding 02:26.640 --> 02:28.620 the last step of. 02:29.430 --> 02:36.600 We will always be a structural model, and hence you will be frequently required to use the structural 02:36.600 --> 02:39.000 modeling state when you leave. 02:40.020 --> 02:41.070 Working with real.