Let us try to understand the typical schematic that will be finding for a behavioral more negotiated
rate.
So again, we start with an entity, OK, we provide a name to an entity depending on the system that
we are implementing, right?
It's then we declare the series of great.
So after we complete declaration of support, OK, we will just be ending our entity.
Right.
So this will be the entity name that we have provided.
Right.
Then we proceed with an architecture.
OK, we provide a name to an architecture, then we linked it with an entity.
OK, is right.
Then again, we have a space to declare war thing between architecture and baking, so they are also
allowed over here.
So we will be frequently finding that we required a signal over here.
Right?
We could also utilize the user defined data type or the memory over here, right?
So all the food things are also allowed over here.
But when we consider the component, so that is used predominantly in a structural modeling stalemate.
So we have a signal or user.
Defined.
Do today.
OK.
Or a members declaration or here?
So this three things you'll be finding between architecture and begin, right?
Then the first key word that is used to recognize that we are utilizing behavioral modeling stylings.
The process of block rate to process is a mandatory will be finding process is not available for any
other modeling state.
And so it is predominantly for a behavioral model.
Excel and this is where you start declaring that the type of modeling state via utilizing is the behavioral
modeling state, right?
So depending on the system that you are implementing.
So if it is combination is so good, you need to specify all the inputs over here.
If it is sequential circuit, you just need to add a clock over here, right?
So in the case of an eye synchronous reset, you need to again add a reset along with the clock right
then between process and begin.
Right.
We have a space to declare a local variable rate, so variables are only allowed in it.
Behave it in more detail that you can get straight.
Then as we complete our definition of a system, we will just be adding first and in process.
OK.
And finally, we will be ending our architecture, right?
So this is the typical skeleton that we have for behavioral modeling.
Remember that behavioral modeling style will start when we are to process OK between process and begin,
we could add a variable and then in between we call ideological right now here in between right between
the beginning and end process.
We could use the assignment operator that we discuss, right?
So whenever you want to connect the value to signal or support.
So the assignment operator that is Signal Assignment Operator is allowed to be utilized in a behavioral
modeling style also, right?
Whereas if you want to assign a value to the variable, then you need to use the variable assignment
operator, right?
So remember this student whenever you have a signal or a pool to which you want to assign a value to.
In this case, we need to use signal assignment operator, right?
So that it shows like this.
Right.
This we already used in the dataflow modeling style or wherever you want to assign a value to a variable.
In that case, you need to use the variable assignment operator, right?
So this is allowed and this is how we assign a value to a signal pool type variable right.
Along with this, the operators that we discuss in a little more Lusail are also allowed to use.
OK, so we could use an automatic operator.
They could use the logical operator, the shift operator, OK, the rotation operator and the relational
operator, right?
So there's all the operators are allowed to utilize in between the processes and in-process rates.
Along with this, we also have behavioral behavioural construct.
So that is something which is only valid in that behavioral model exchange rate.
So the operator, the type of operator will be signal assignment operator in the case.
We want to assign value to signal input.
Right.
If you want to assign your value to a variable, we will be utilizing a variable the same way an operator
in a case when we want to use the operator.
So all the operator that we're discussing the data flow modeling style are also eligible in the behavioral
modeling states.
So we could use automatic logical shift rotation and relational operator in between the process and
in process.
And along with this, we also get the behavioral construct rates.
So these include the key statement, which is very, very useful.
And if that's right, that's something that we frequently used straight.
So we have a statement, we have NFL statement.
It will be primarily focusing on this since most of the system could be easily implemented with this
to construct, right?
So these are some of the things that are allowed to be utilized in a behavioral modeling stage.
So what you could do is you could just keep this in your circle.
Just keep a note of this.
OK.
So something that we already discussed is how you use a signal assignment operator and a variable assignment
operator, the different operators that we have.
Only thing that is left is the behavioral constructs right to how we use a key statement and field statement
we will be discussing along with an example.
So you could clearly understand how you implement the combination of line, the sequential system with
the behavioral modeling exchange rate.
So remember this the behavioral modeling style will start with a declaration of a process, so you need
to specify an argument depending on the circuit that you are.
Specify.
OK.
And then in between beginning and end process, you have this option, OK, which are allowed to be
utilized, right?
So as we further build up our understanding, we'll be understanding what else you can do in an behavioral
more next day.
Later agenda will be for us to understand how we utilize the entire thing that we have written over
here in a behavioral modernistic.
And then as we build up, our foundation will be understanding the different complex thing that you
could do with the behavioral modeling stay.