WEBVTT 00:00.060 --> 00:05.400 So now we know that we have a three mile island state which are synthesizing and when a humbling state 00:05.640 --> 00:07.290 which is not synthesized, right? 00:07.590 --> 00:14.250 So we'll start discussing a Morgan Stanley analyst in, though we will be considering a simple example 00:14.250 --> 00:16.860 to understand the different construct that we have right. 00:17.100 --> 00:20.940 And the simplest modeling style that you could guess is the idea of state. 00:21.020 --> 00:21.200 Great. 00:21.210 --> 00:27.390 So whenever we could replace that system with a basic logic, we will be free to go with three different 00:27.450 --> 00:29.270 Morganstern know each more. 00:29.570 --> 00:33.210 They have a specific syntax that you need to follow, right? 00:33.480 --> 00:37.500 So that can be considered as the skeleton of the marketing, right? 00:37.770 --> 00:42.510 So remember, at the beginning, it will be very difficult to remember the skeleton. 00:42.510 --> 00:47.070 But as you progress and practice more, the things will become much easier to understand. 00:47.330 --> 00:54.980 So in this specific video, we will be understanding the typical skeleton that we have for the of low 00:54.990 --> 00:55.860 mortgage rates. 00:55.860 --> 01:02.610 So whether it is the data flow modeling style, structural modeling style or behavior modeling state. 01:02.960 --> 01:10.650 OK, so this two part that is adding a library, OK, which represent the first part of the code and 01:10.650 --> 01:14.970 then adding an entity which represent the second part of the ground. 01:15.000 --> 01:21.450 Finally, we have the third part, right, which represented an architecture of obviously OK, so only 01:21.450 --> 01:27.090 differences that you'll be finding between our different modeling styles in the third part, right where 01:27.090 --> 01:28.650 we specify an architecture. 01:29.070 --> 01:35.130 So whether it is D.W modeling state or a behavioral modeling state or a structural modeling state in 01:35.130 --> 01:41.550 the first two part will remain exactly similar to whatever we discuss on them. 01:41.820 --> 01:44.070 OK, that is valid for all the modeling. 01:44.760 --> 01:50.130 But when we consider the differing modeling, say the differences that I use when we start. 01:51.380 --> 01:55.710 So differences will be there when we start writing inoculate. 01:56.000 --> 01:58.040 So that is what we're going to over here. 01:58.050 --> 02:03.530 So as we choose the model and say the differences will only be inoculated. 02:03.710 --> 02:06.080 So this is something that you need to remember, right? 02:06.740 --> 02:08.930 So when we consider that a let's say. 02:10.420 --> 02:13.300 OK, so we start with an architecture again. 02:14.370 --> 02:20.610 OK, then we provide the name to an architecture, then we need to specify the entity name to which 02:20.610 --> 02:22.650 this architecture is attached. 02:22.800 --> 02:23.040 Right. 02:23.100 --> 02:29.170 So architecture, the name of an architecture all, then the entity name is right. 02:29.550 --> 02:31.530 Then we have a space to add a begin. 02:32.890 --> 02:33.250 OK. 02:33.430 --> 02:40.270 And finally, we end our architecture, right, so this is the typical syntax that we have for in the 02:40.660 --> 02:41.470 morning stay right. 02:41.470 --> 02:43.030 So only reference been here. 02:44.130 --> 02:49.650 We will be predominantly finding a signal when present, right, so you'll always find the signal will 02:49.650 --> 02:52.650 be there in in between the architecture and begin. 02:52.830 --> 02:56.930 If you have some undefined net or signals simply is not required, right? 02:57.180 --> 03:03.230 And then between begin and name, we have a set of an operator, OK? 03:03.240 --> 03:04.180 And the. 03:05.550 --> 03:12.150 And the assignment operator, right, so these are the two things that are allowed to use. 03:12.570 --> 03:12.920 OK? 03:13.180 --> 03:18.090 In between beginning and end architecture, when we are working within the flow model. 03:18.600 --> 03:22.530 So this will be our typical skeleton when we work around with the data from Morgan State. 03:22.800 --> 03:24.240 We start with an architecture. 03:24.450 --> 03:32.310 If your design consists of any undefined net, you need to use the signal OK, and signal is simply 03:32.310 --> 03:32.940 not required. 03:33.240 --> 03:35.130 Then we start with the begin. 03:35.400 --> 03:40.260 OK, and then you have a series of statements which are developed with the help of an operator which 03:40.260 --> 03:41.940 did a little modeling style support. 03:42.210 --> 03:44.340 And then you have an assignment operator, right? 03:44.340 --> 03:45.240 So to. 03:46.190 --> 03:47.930 All the construct that are available. 03:49.100 --> 03:56.690 So the construct that are available for sale include the set of phone operators and anything we. 03:57.350 --> 04:02.470 So you'll just need to know this two things and you are ready to proceed with that detail. 04:03.440 --> 04:08.510 So what are we going to do is we will be understanding what other operators that are available with 04:08.510 --> 04:11.950 us and what kind of assignment operators that are available for us. 04:12.410 --> 04:19.280 So once we have an idea about this too, we will be finally summarizing what will be there when we consider 04:19.280 --> 04:20.390 our data flow modelling.