WEBVTT 00:00.120 --> 00:06.720 Now, when we consider and hardware description, language or an idea, OK, that it may be still are 00:06.720 --> 00:07.230 very low. 00:07.770 --> 00:14.910 So we have at least four ways of implementing a SIEM system and that is referred to as a modeling state. 00:14.930 --> 00:15.210 Right. 00:15.510 --> 00:19.790 So what modeling state basically mean for a specific kind of a system? 00:19.800 --> 00:22.770 We follow us specific style of accounting. 00:23.100 --> 00:23.480 OK. 00:23.550 --> 00:26.500 And when you correctly follow the modeling style. 00:26.670 --> 00:32.100 OK, you get your system implemented with a less amount of code, right? 00:32.180 --> 00:36.760 So that is the only difference that you'll be finding if you consider any of a system. 00:36.780 --> 00:39.420 So we at least have a few weeks to implement it. 00:39.660 --> 00:39.900 Right. 00:40.740 --> 00:48.000 The advantage of choosing the correct modeling style is you'll be able to implement a system with a 00:48.000 --> 00:49.290 less amount of rate. 00:49.560 --> 00:52.820 So how do we recognize which modeling state to proceed? 00:53.040 --> 00:57.090 So first, let's just discuss what are the different modeling studies that we have. 00:57.120 --> 00:57.360 Right. 00:57.360 --> 01:03.450 So the first modeling saying that we have is the audit of low modeling state. 01:04.780 --> 01:14.140 OK, this is the first model and say, OK, this second modeling say that we have witnesses of behavioral 01:14.140 --> 01:14.590 modeling. 01:16.130 --> 01:21.890 The toll modelling saying that we have with the structural modeling stay. 01:23.120 --> 01:30.310 The last modelling state that we have with thisis switch level modeling state. 01:31.370 --> 01:31.700 OK. 01:32.030 --> 01:37.580 The first modeling state that is Dataflow could also be referred to as acute level modeling. 01:39.960 --> 01:47.640 So these are the four ways that we have, and these are the differing modeling say that we have in our 01:47.670 --> 01:47.930 midst. 01:48.180 --> 01:48.340 Right. 01:48.390 --> 01:53.520 So these are the four ways by which you would implement the system know the uniqueness about each morning. 01:53.520 --> 01:57.050 Staley's each have a specific skeleton that you need to find, right? 01:57.390 --> 02:03.300 And when you follow a correct skeleton, you leave it to automatically input the correct modeling. 02:03.570 --> 02:03.840 Right. 02:04.140 --> 02:06.210 So we have a data flow modeling state. 02:06.630 --> 02:08.020 We have behavioral modeling. 02:08.940 --> 02:10.760 We have a structural modeling shape. 02:11.400 --> 02:14.010 And we have a search level model, right? 02:15.520 --> 02:21.460 So now let's try to understand how we choose out of this role model and style, which modelling state 02:21.460 --> 02:24.830 to adopt to implement the system under consideration. 02:24.860 --> 02:25.120 Right. 02:25.390 --> 02:33.220 So if OK, so let's just consider the specific logic that we adopt to easily choose which modelling 02:33.220 --> 02:34.810 state you work around with, right? 02:36.350 --> 02:42.830 So if you have a system, right, so let's assume this is a system that you are implementing, right? 02:43.520 --> 02:48.560 So if you can replace this system with a set of basic logic, it. 02:50.050 --> 02:56.320 Then in search geese, we prefer to go with the geek level or dataflow more links. 02:56.710 --> 03:03.130 So this is the simplest way to recognize when you could use the date of the morning stay for an implementation. 03:03.160 --> 03:04.870 OK, so just to give you an example. 03:05.200 --> 03:05.560 OK. 03:05.800 --> 03:10.330 So if we considered that, is it you that we are implementing? 03:11.320 --> 03:12.090 Do to one. 03:12.610 --> 03:15.760 Right, so this is what we are implementing, misrepresent our system. 03:16.120 --> 03:20.550 Now let's assume that we have to include and be OK. 03:20.890 --> 03:22.090 We have an output. 03:22.090 --> 03:22.630 Why? 03:22.670 --> 03:23.020 OK. 03:23.030 --> 03:27.580 And since we only have two inputs to select line will be all, say, single bit rate. 03:27.940 --> 03:30.680 And if you know how much operate. 03:30.700 --> 03:33.400 OK, so why will be simply the do? 03:33.500 --> 03:40.000 OK, so let's do men selected zero that you select, but you will be choosing to say whatever value 03:40.000 --> 03:40.930 that we have one in. 03:41.740 --> 03:43.600 And if selected, is one, right? 03:43.660 --> 03:47.410 So in that case will be sending whatever the value that we have on. 03:47.750 --> 03:47.930 Right. 03:47.950 --> 03:51.010 So this completes an expression of our output. 03:51.250 --> 03:55.420 Right now, if you just implement this with basic logic, it right? 03:55.780 --> 03:57.760 So you required 198. 03:58.900 --> 04:03.940 OK, so this is a first and then we require one more and get over here. 04:04.900 --> 04:07.900 OK, and finally, we need to order them together, right? 04:08.320 --> 04:11.220 So we require finally when it. 04:12.440 --> 04:14.830 And then you have your right. 04:15.080 --> 04:24.230 So on this side of this, I great you have select by OK, Andy, and on this side you have select and 04:24.380 --> 04:25.040 be right. 04:25.040 --> 04:27.650 So this completes our entire system now. 04:27.890 --> 04:36.170 Our system is this one that is to to one looks OK, but we are able to convert it into a set of basic 04:36.170 --> 04:36.560 logic. 04:36.620 --> 04:40.310 Great to be able to represent our system with a basic logic. 04:40.670 --> 04:48.200 So if whenever you able to do the same thing, if you have your system and if you are able to replace 04:48.200 --> 04:56.650 it with an basic logic, it the preferred modeling state will always be either a dataflow or v refactor 04:56.670 --> 04:58.510 that state level modeling state. 04:58.630 --> 04:58.810 Right. 04:58.830 --> 05:02.070 So this is how we choose the readability modeling state, right? 05:02.780 --> 05:09.410 Then second, modeling style that we have it assists the behavioral modeling so late. 05:09.410 --> 05:13.610 So what we're going to do is behavioral modeling state will be considering at the end. 05:13.640 --> 05:13.970 Great. 05:14.000 --> 05:19.560 So the second modeling state that is considered, you have an example of collider. 05:20.420 --> 05:25.720 Right now, we already know that Collider could be big considering you have partners, right? 05:25.730 --> 05:26.870 So you have. 05:27.710 --> 05:28.620 First half, right? 05:28.910 --> 05:29.230 Right. 05:29.820 --> 05:35.090 So that it's you would have three three, I'm to be be. 05:36.260 --> 05:40.400 And then two output sum out OK and see. 05:40.670 --> 05:40.910 Right. 05:41.180 --> 05:43.720 So these are the ports which are present on the full. 05:44.090 --> 05:45.540 So far, first half and. 05:45.920 --> 05:46.220 Right. 05:46.550 --> 05:49.790 We feed A and B and the output of this. 05:49.820 --> 05:50.160 OK? 05:51.160 --> 05:56.810 And then let us assume that this is some and this is scary off our topic right now. 05:56.830 --> 06:01.990 We need to feed the summer first half made it to the second half. 06:02.770 --> 06:08.530 So this will be feeding to one up an input and then third input, which is seen, will be going to the 06:08.530 --> 06:11.770 other input final topic to write. 06:12.140 --> 06:17.620 And finally, the carry out of this, do we need to or them together? 06:17.690 --> 06:19.480 OK, and we get to see out right? 06:19.990 --> 06:24.760 And sort of this hotbed will basically give us some out of. 06:25.700 --> 06:29.930 Therefore, like the rate, so here what we are doing is we are reusing. 06:30.230 --> 06:33.800 We are using Halfaker, who OK to implement the flag. 06:33.920 --> 06:40.850 So whenever you are in a situation where you reduce the use of company. 06:42.960 --> 06:47.040 So we refer to this half hour to here as a company to build. 06:48.180 --> 06:49.200 Complex. 06:50.290 --> 06:50.950 System. 06:51.430 --> 06:57.850 OK, so whenever you are in a situation where you have your existing component, no existing component 06:57.850 --> 07:02.410 could be made by you or it could also be of a specific IP. 07:02.450 --> 07:07.870 Xray type is basically a component provided by a vendor to us with a reliable rate. 07:08.080 --> 07:14.260 So the component could be the component that you build on your own, or it could also be represent types 07:14.260 --> 07:17.650 which are present with the IED that we are utilizing. 07:18.130 --> 07:26.530 So if we are using a component to build a complex system in, that is the margin state that will be 07:26.530 --> 07:30.730 peppering his structural modeling stack. 07:31.360 --> 07:33.010 Right now, we have a clear distinction. 07:33.010 --> 07:39.820 So if you have a system and if I produced equitably psychological, I label to use the gate or the flow 07:39.820 --> 07:41.650 modeling state for its implementation. 07:42.370 --> 07:48.670 If I have my own component and if I want to use it to build a complex system, in that case, I'll be 07:48.670 --> 07:51.000 referring to Google structure modeling state. 07:51.430 --> 07:53.470 The third modeling is the. 07:54.570 --> 07:56.610 There is you you have your system. 07:57.690 --> 07:58.080 OK. 07:58.350 --> 08:02.340 And then you able to replace it with the set of. 08:03.400 --> 08:07.570 Switches, rates, the switches basically represent and most MP emails. 08:08.530 --> 08:11.500 OK, so you have a system and you able to create. 08:12.670 --> 08:19.690 The schematic, which consists of only and most AP Moss in that piece, we prefer to remove it. 08:20.230 --> 08:23.440 Switch level modeling. 08:24.610 --> 08:31.360 Stay right now, this is the lowest level of an abstraction that we have in a nation and you'll be noticing 08:31.360 --> 08:32.830 indicators of a complex system. 08:32.900 --> 08:39.600 This is simply not a good choice to have a switch level modeling stay right. 08:39.910 --> 08:47.650 So in the case of a complex system, you simply can't implement your system with the success rate. 08:47.920 --> 08:49.330 And the reason being. 08:50.630 --> 08:56.330 Neither difficulty with the switch level modelling, say now we face two difficulty with the switch 08:56.330 --> 08:56.960 level modelling. 08:57.230 --> 09:04.160 First one is if you have a really complex system, then in that case, finding an equivalent representation 09:04.160 --> 09:09.350 of a switches is close to impossible right now, and the second difficulty is revival. 09:09.350 --> 09:12.980 Do not support switch level model extent, so you would perform a simulation. 09:13.160 --> 09:16.170 But this is simply not synthesized. 09:16.170 --> 09:21.200 We will learn our agenda in this course will be to understand this and decisively construct only. 09:21.380 --> 09:25.700 So we will not be doing much discussion on the switch level modelling standard. 09:25.850 --> 09:31.730 So the logic is very simple you have your system and you are able to find an equal representation of 09:31.760 --> 09:33.620 a system with the switches. 09:33.620 --> 09:35.870 Now, switches include must be more seamless. 09:36.250 --> 09:42.350 OK, so if you're able to find out an equal representation of the switches in that case, we prefer 09:42.350 --> 09:44.060 to go with the switch level modelling state. 09:44.110 --> 09:46.810 Right now, we know three different categories of warming. 09:47.840 --> 09:53.150 So if you are able to replace your system with a basic logic gate, go ahead with a heat level or the 09:53.150 --> 09:54.260 data flow monolithic. 09:54.710 --> 10:03.020 If you could replace your system with the switches, which include and most and be most, then we prefer 10:03.020 --> 10:05.210 to go with the switch level modelling state. 10:05.450 --> 10:12.170 If you are reusing the previous debate company to form a complex system, then we prefer to go with 10:12.170 --> 10:13.370 the structural modelling. 10:13.370 --> 10:20.090 Say, say, the last modelling stylists behaved great and most of the complex process. 10:20.240 --> 10:24.160 This will be the modelling style that we start work on, right? 10:24.170 --> 10:30.470 So whenever you do not know what is an internal architecture of the system, so this will usually be 10:30.470 --> 10:36.320 a case when we work on a new project, so we do not have the representation with the basic logic gate 10:36.320 --> 10:37.090 for our system. 10:37.100 --> 10:43.250 We also do not know how to represent our system with the basic switches, or we also do not know what 10:43.250 --> 10:46.780 are the subsystem that is required for our system. 10:47.060 --> 10:50.900 When we are working first time on a new system, so whenever you cannot. 10:52.160 --> 10:59.690 So whenever you do not know what is an internal architecture that you have for a system and that is 10:59.690 --> 11:02.780 we prefer to go within behavioral modeling standards. 11:03.260 --> 11:07.160 So these are the four alternatives that we have with us today. 11:07.190 --> 11:13.640 So just to summarize, if you able to replace your system, right, so you have a system. 11:14.770 --> 11:20.770 Okay, so if you have a system and if you can replace that with a set of four basic logic. 11:21.670 --> 11:29.740 OK, and that is we can see that we will be refereeing the gate or data flow modelling. 11:30.190 --> 11:39.130 OK, if we have a system and if we can represent this with the suitcase, OK, in that case, we will 11:39.130 --> 11:44.350 be efforting to go with switch level modelling stay. 11:45.340 --> 11:45.770 Right. 11:46.180 --> 11:52.720 The third one that we have is if we have a prepaid component, right, so existing. 11:53.990 --> 12:04.040 Components that we reuse to build a complex system, OK, and that is we prefer to go ahead and use 12:04.130 --> 12:05.120 structural. 12:06.150 --> 12:08.130 Modeling stay right, this makes sense. 12:09.310 --> 12:12.370 And the last one is then we do not know. 12:12.550 --> 12:19.930 And in doing that architecture of resistance, right, so internal architecture is unknown. 12:20.990 --> 12:27.680 OK, in that case, we prefer to go with the behavioral modeling modeling study. 12:28.070 --> 12:34.160 So when we see we do not know an internal architecture of a system that basically mean we cannot represent 12:34.160 --> 12:36.890 it with a basic logic gate or switches is OK. 12:37.070 --> 12:44.090 So we know an abstract idea of the system so we can represent our system with a set of a set system, 12:44.270 --> 12:44.570 right? 12:44.750 --> 12:50.060 And then we independently build a set of subsystems and finally, we use the structural model. 12:50.180 --> 12:56.480 And so when we work with a complex project, usually the thing will be that you have the fundamental 12:56.480 --> 12:58.670 block design of your system, right? 12:58.880 --> 13:02.630 So you start implementing the simple subsystems, right? 13:02.900 --> 13:07.760 And then finally, at the end, when you complete all this system, you prefer to go with the structural 13:07.760 --> 13:08.070 modeling. 13:08.810 --> 13:15.680 So usually when we consider the behavioral modeling state, so we have certain construct that could 13:15.860 --> 13:20.840 help us to implement a system if you know the behavior of a system, right? 13:21.010 --> 13:27.280 What we mean by behavior of the system is that it it's you that you are implementing seemed to us to 13:27.740 --> 13:27.930 right. 13:28.640 --> 13:31.790 But here in this case, instead of the. 13:32.840 --> 13:36.120 Data flow modelling say we prefer to go with a behavior one days. 13:36.360 --> 13:41.360 So again, we have Eby, which represents the input to at least one must we have a select line? 13:41.780 --> 13:42.920 OK, and then we have. 13:43.130 --> 13:43.720 Right, right. 13:43.970 --> 13:46.730 But here we do not know an internal architecture of a system. 13:46.740 --> 13:48.710 So what is inside to is to and must. 13:48.710 --> 13:49.520 We do not know. 13:49.760 --> 13:54.320 OK, but we know our behavior, for example, when we considered a system operation. 13:54.320 --> 14:01.090 So we already know that depending on the value of a select OK, we choose the value of life, right? 14:02.040 --> 14:09.330 So if select is zero, right, so if selected zero in that case, why should be we? 14:09.840 --> 14:12.920 And if selected as one, why should be cost to be paid? 14:12.930 --> 14:16.650 So this is the behavior that we all really do right now. 14:16.660 --> 14:22.060 Behavioral modeling, say, gives us the set of construct that could be used to implement such behavior. 14:22.060 --> 14:25.650 That is, we can use this construct if. 14:26.540 --> 14:28.900 Select is equal to. 14:29.950 --> 14:33.670 Well, right, then we could just see that. 14:33.840 --> 14:34.420 Why? 14:35.470 --> 14:37.450 Will be equal to a. 14:38.500 --> 14:38.740 OK. 14:39.070 --> 14:47.830 Else and why will be equals to the right and yes, Dave will just be ending in. 14:48.860 --> 14:49.190 Right. 14:49.520 --> 14:53.870 So here you you can see that we do not know an internal architecture of the system. 14:54.770 --> 15:01.010 But just knowing a behavior office system, we could have a set of ActionScript, which are available 15:01.010 --> 15:04.180 with the behavioral modeling state, OK. 15:04.310 --> 15:07.550 And we can utilize them to implement a complex system. 15:07.860 --> 15:10.790 So as we progress further will be understanding the different. 15:11.840 --> 15:16.970 System that we could prefer to implement better behavior in markets doing great, so things will be 15:16.970 --> 15:21.010 much easier to understand as we build up our fundamental understanding. 15:21.500 --> 15:28.070 Just remember this things in your mind that if you have a system and if we can replace this with the 15:28.070 --> 15:35.630 basic logic you use of great authority modeling state, if you can replace your system with the switches 15:35.630 --> 15:42.830 you use, switch level modeling state if you have an existing subsystem that you want to reuse to build 15:42.830 --> 15:46.280 a complex system preferred to go with a structural modeling state. 15:46.550 --> 15:52.160 And if you do not know the internal architecture of the system, but you know the behavior of the system, 15:52.430 --> 15:55.540 in that case, we prefer to go with that behavior in non-league state. 15:55.610 --> 15:55.760 Right. 15:55.800 --> 16:01.090 So these are the four ways by which you could implement any system in a region. 16:01.130 --> 16:07.790 The advantage that you get by correctly choosing a Morningstar analyst with a less line of goal, you 16:07.790 --> 16:09.840 would actually implement system.