Now, when we consider and hardware description, language or an idea, OK, that it may be still are
very low.
So we have at least four ways of implementing a SIEM system and that is referred to as a modeling state.
Right.
So what modeling state basically mean for a specific kind of a system?
We follow us specific style of accounting.
OK.
And when you correctly follow the modeling style.
OK, you get your system implemented with a less amount of code, right?
So that is the only difference that you'll be finding if you consider any of a system.
So we at least have a few weeks to implement it.
Right.
The advantage of choosing the correct modeling style is you'll be able to implement a system with a
less amount of rate.
So how do we recognize which modeling state to proceed?
So first, let's just discuss what are the different modeling studies that we have.
Right.
So the first modeling saying that we have is the audit of low modeling state.
OK, this is the first model and say, OK, this second modeling say that we have witnesses of behavioral
modeling.
The toll modelling saying that we have with the structural modeling stay.
The last modelling state that we have with thisis switch level modeling state.
OK.
The first modeling state that is Dataflow could also be referred to as acute level modeling.
So these are the four ways that we have, and these are the differing modeling say that we have in our
midst.
Right.
So these are the four ways by which you would implement the system know the uniqueness about each morning.
Staley's each have a specific skeleton that you need to find, right?
And when you follow a correct skeleton, you leave it to automatically input the correct modeling.
Right.
So we have a data flow modeling state.
We have behavioral modeling.
We have a structural modeling shape.
And we have a search level model, right?
So now let's try to understand how we choose out of this role model and style, which modelling state
to adopt to implement the system under consideration.
Right.
So if OK, so let's just consider the specific logic that we adopt to easily choose which modelling
state you work around with, right?
So if you have a system, right, so let's assume this is a system that you are implementing, right?
So if you can replace this system with a set of basic logic, it.
Then in search geese, we prefer to go with the geek level or dataflow more links.
So this is the simplest way to recognize when you could use the date of the morning stay for an implementation.
OK, so just to give you an example.
OK.
So if we considered that, is it you that we are implementing?
Do to one.
Right, so this is what we are implementing, misrepresent our system.
Now let's assume that we have to include and be OK.
We have an output.
Why?
OK.
And since we only have two inputs to select line will be all, say, single bit rate.
And if you know how much operate.
OK, so why will be simply the do?
OK, so let's do men selected zero that you select, but you will be choosing to say whatever value
that we have one in.
And if selected, is one, right?
So in that case will be sending whatever the value that we have on.
Right.
So this completes an expression of our output.
Right now, if you just implement this with basic logic, it right?
So you required 198.
OK, so this is a first and then we require one more and get over here.
OK, and finally, we need to order them together, right?
So we require finally when it.
And then you have your right.
So on this side of this, I great you have select by OK, Andy, and on this side you have select and
be right.
So this completes our entire system now.
Our system is this one that is to to one looks OK, but we are able to convert it into a set of basic
logic.
Great to be able to represent our system with a basic logic.
So if whenever you able to do the same thing, if you have your system and if you are able to replace
it with an basic logic, it the preferred modeling state will always be either a dataflow or v refactor
that state level modeling state.
Right.
So this is how we choose the readability modeling state, right?
Then second, modeling style that we have it assists the behavioral modeling so late.
So what we're going to do is behavioral modeling state will be considering at the end.
Great.
So the second modeling state that is considered, you have an example of collider.
Right now, we already know that Collider could be big considering you have partners, right?
So you have.
First half, right?
Right.
So that it's you would have three three, I'm to be be.
And then two output sum out OK and see.
Right.
So these are the ports which are present on the full.
So far, first half and.
Right.
We feed A and B and the output of this.
OK?
And then let us assume that this is some and this is scary off our topic right now.
We need to feed the summer first half made it to the second half.
So this will be feeding to one up an input and then third input, which is seen, will be going to the
other input final topic to write.
And finally, the carry out of this, do we need to or them together?
OK, and we get to see out right?
And sort of this hotbed will basically give us some out of.
Therefore, like the rate, so here what we are doing is we are reusing.
We are using Halfaker, who OK to implement the flag.
So whenever you are in a situation where you reduce the use of company.
So we refer to this half hour to here as a company to build.
Complex.
System.
OK, so whenever you are in a situation where you have your existing component, no existing component
could be made by you or it could also be of a specific IP.
Xray type is basically a component provided by a vendor to us with a reliable rate.
So the component could be the component that you build on your own, or it could also be represent types
which are present with the IED that we are utilizing.
So if we are using a component to build a complex system in, that is the margin state that will be
peppering his structural modeling stack.
Right now, we have a clear distinction.
So if you have a system and if I produced equitably psychological, I label to use the gate or the flow
modeling state for its implementation.
If I have my own component and if I want to use it to build a complex system, in that case, I'll be
referring to Google structure modeling state.
The third modeling is the.
There is you you have your system.
OK.
And then you able to replace it with the set of.
Switches, rates, the switches basically represent and most MP emails.
OK, so you have a system and you able to create.
The schematic, which consists of only and most AP Moss in that piece, we prefer to remove it.
Switch level modeling.
Stay right now, this is the lowest level of an abstraction that we have in a nation and you'll be noticing
indicators of a complex system.
This is simply not a good choice to have a switch level modeling stay right.
So in the case of a complex system, you simply can't implement your system with the success rate.
And the reason being.
Neither difficulty with the switch level modelling, say now we face two difficulty with the switch
level modelling.
First one is if you have a really complex system, then in that case, finding an equivalent representation
of a switches is close to impossible right now, and the second difficulty is revival.
Do not support switch level model extent, so you would perform a simulation.
But this is simply not synthesized.
We will learn our agenda in this course will be to understand this and decisively construct only.
So we will not be doing much discussion on the switch level modelling standard.
So the logic is very simple you have your system and you are able to find an equal representation of
a system with the switches.
Now, switches include must be more seamless.
OK, so if you're able to find out an equal representation of the switches in that case, we prefer
to go with the switch level modelling state.
Right now, we know three different categories of warming.
So if you are able to replace your system with a basic logic gate, go ahead with a heat level or the
data flow monolithic.
If you could replace your system with the switches, which include and most and be most, then we prefer
to go with the switch level modelling state.
If you are reusing the previous debate company to form a complex system, then we prefer to go with
the structural modelling.
Say, say, the last modelling stylists behaved great and most of the complex process.
This will be the modelling style that we start work on, right?
So whenever you do not know what is an internal architecture of the system, so this will usually be
a case when we work on a new project, so we do not have the representation with the basic logic gate
for our system.
We also do not know how to represent our system with the basic switches, or we also do not know what
are the subsystem that is required for our system.
When we are working first time on a new system, so whenever you cannot.
So whenever you do not know what is an internal architecture that you have for a system and that is
we prefer to go within behavioral modeling standards.
So these are the four alternatives that we have with us today.
So just to summarize, if you able to replace your system, right, so you have a system.
Okay, so if you have a system and if you can replace that with a set of four basic logic.
OK, and that is we can see that we will be refereeing the gate or data flow modelling.
OK, if we have a system and if we can represent this with the suitcase, OK, in that case, we will
be efforting to go with switch level modelling stay.
Right.
The third one that we have is if we have a prepaid component, right, so existing.
Components that we reuse to build a complex system, OK, and that is we prefer to go ahead and use
structural.
Modeling stay right, this makes sense.
And the last one is then we do not know.
And in doing that architecture of resistance, right, so internal architecture is unknown.
OK, in that case, we prefer to go with the behavioral modeling modeling study.
So when we see we do not know an internal architecture of a system that basically mean we cannot represent
it with a basic logic gate or switches is OK.
So we know an abstract idea of the system so we can represent our system with a set of a set system,
right?
And then we independently build a set of subsystems and finally, we use the structural model.
And so when we work with a complex project, usually the thing will be that you have the fundamental
block design of your system, right?
So you start implementing the simple subsystems, right?
And then finally, at the end, when you complete all this system, you prefer to go with the structural
modeling.
So usually when we consider the behavioral modeling state, so we have certain construct that could
help us to implement a system if you know the behavior of a system, right?
What we mean by behavior of the system is that it it's you that you are implementing seemed to us to
right.
But here in this case, instead of the.
Data flow modelling say we prefer to go with a behavior one days.
So again, we have Eby, which represents the input to at least one must we have a select line?
OK, and then we have.
Right, right.
But here we do not know an internal architecture of a system.
So what is inside to is to and must.
We do not know.
OK, but we know our behavior, for example, when we considered a system operation.
So we already know that depending on the value of a select OK, we choose the value of life, right?
So if select is zero, right, so if selected zero in that case, why should be we?
And if selected as one, why should be cost to be paid?
So this is the behavior that we all really do right now.
Behavioral modeling, say, gives us the set of construct that could be used to implement such behavior.
That is, we can use this construct if.
Select is equal to.
Well, right, then we could just see that.
Why?
Will be equal to a.
OK.
Else and why will be equals to the right and yes, Dave will just be ending in.
Right.
So here you you can see that we do not know an internal architecture of the system.
But just knowing a behavior office system, we could have a set of ActionScript, which are available
with the behavioral modeling state, OK.
And we can utilize them to implement a complex system.
So as we progress further will be understanding the different.
System that we could prefer to implement better behavior in markets doing great, so things will be
much easier to understand as we build up our fundamental understanding.
Just remember this things in your mind that if you have a system and if we can replace this with the
basic logic you use of great authority modeling state, if you can replace your system with the switches
you use, switch level modeling state if you have an existing subsystem that you want to reuse to build
a complex system preferred to go with a structural modeling state.
And if you do not know the internal architecture of the system, but you know the behavior of the system,
in that case, we prefer to go with that behavior in non-league state.
Right.
So these are the four ways by which you could implement any system in a region.
The advantage that you get by correctly choosing a Morningstar analyst with a less line of goal, you
would actually implement system.