So now we know that we have a three mile island state which are synthesizing and when a humbling state
which is not synthesized, right?
So we'll start discussing a Morgan Stanley analyst in, though we will be considering a simple example
to understand the different construct that we have right.
And the simplest modeling style that you could guess is the idea of state.
Great.
So whenever we could replace that system with a basic logic, we will be free to go with three different
Morganstern know each more.
They have a specific syntax that you need to follow, right?
So that can be considered as the skeleton of the marketing, right?
So remember, at the beginning, it will be very difficult to remember the skeleton.
But as you progress and practice more, the things will become much easier to understand.
So in this specific video, we will be understanding the typical skeleton that we have for the of low
mortgage rates.
So whether it is the data flow modeling style, structural modeling style or behavior modeling state.
OK, so this two part that is adding a library, OK, which represent the first part of the code and
then adding an entity which represent the second part of the ground.
Finally, we have the third part, right, which represented an architecture of obviously OK, so only
differences that you'll be finding between our different modeling styles in the third part, right where
we specify an architecture.
So whether it is D.W modeling state or a behavioral modeling state or a structural modeling state in
the first two part will remain exactly similar to whatever we discuss on them.
OK, that is valid for all the modeling.
But when we consider the differing modeling, say the differences that I use when we start.
So differences will be there when we start writing inoculate.
So that is what we're going to over here.
So as we choose the model and say the differences will only be inoculated.
So this is something that you need to remember, right?
So when we consider that a let's say.
OK, so we start with an architecture again.
OK, then we provide the name to an architecture, then we need to specify the entity name to which
this architecture is attached.
Right.
So architecture, the name of an architecture all, then the entity name is right.
Then we have a space to add a begin.
OK.
And finally, we end our architecture, right, so this is the typical syntax that we have for in the
morning stay right.
So only reference been here.
We will be predominantly finding a signal when present, right, so you'll always find the signal will
be there in in between the architecture and begin.
If you have some undefined net or signals simply is not required, right?
And then between begin and name, we have a set of an operator, OK?
And the.
And the assignment operator, right, so these are the two things that are allowed to use.
OK?
In between beginning and end architecture, when we are working within the flow model.
So this will be our typical skeleton when we work around with the data from Morgan State.
We start with an architecture.
If your design consists of any undefined net, you need to use the signal OK, and signal is simply
not required.
Then we start with the begin.
OK, and then you have a series of statements which are developed with the help of an operator which
did a little modeling style support.
And then you have an assignment operator, right?
So to.
All the construct that are available.
So the construct that are available for sale include the set of phone operators and anything we.
So you'll just need to know this two things and you are ready to proceed with that detail.
So what are we going to do is we will be understanding what other operators that are available with
us and what kind of assignment operators that are available for us.
So once we have an idea about this too, we will be finally summarizing what will be there when we consider
our data flow modelling.