In this video, I'm going to show you the process involved from ideation to data modeling or how we
can transform ideas into data.
So let's get going.
Let's take that.
Lucky for you, you got a contract as a developer and you are going to develop a blog application or
school management application.
Now, what would be the next step?
The next step is you are going to sit down and talk to your client.
So let's say that this is a client and this is you, the developer.
Now, your client is going to tell you the requirements about the application.
The client is going to speak in broad terms, but as a developer, you are going to take those ideas
and then form what is called data modeling.
So after the meeting, meaning that after you got all the client want, now it is up to you and your
computer.
So at this point, we need to think through how you are going to model the data.
For me, sometimes this is how it happens to me.
First, I need to think about how I'm going to model the data, and even when I go to bed, I still
think about how I'm going to model the data.
But lucky for you, I'm going to show you my experience how I model data.
But lucky for you, I'm going to show you my experience, how I model data in a simple way.
So I.
Ready?
Let me show you my techniques.
Great.
The first point is what you call the planning stage, and that is what we have done by sitting with
a client.
So now that I've got the idea for my client, the next step is I look to give the database name.
So if you don't know database, we have a database and the MongoDB.
So let's say that you are going to build a school management system or a block application, the database
name going to be our school management system.
So first of all, you got the database name.
The next step is called the collection in MongoDB.
So the collection comprises of the individual entities that are related together.
So let's say you are building a school management system.
Definitely.
You need students.
So student here is one collection and courses is one collection and staff is also one collection.
So now you know all this collection based on the client what needs so you've got know the collection
during the planning stage.
Do you get it?
Yes.
So now the next step is this is what we call the database relationship.
See that I've given it a question mark because we are going to cover it in details.
So what do I mean?
What I mean is that let's say we have this collection.
Collection number one is for courses.
Number two is for students.
And then, let's say staff.
So how are these collection are related together?
We can say that.
Well, a student can have many courses and a course can belongs to many students.
And this what you call the relationship.
And we have a section to talk about database relationship.
So let's get going.
The next planning stage is what we call the document.
So after you finish the relationship, now it's time to create document.
So we get document from collection.
So document simply means the actual record.
So if we have student collection and then you register one student, that student is now what called
the documents.
All right.
So this is a process involved that you need to take before we even open Visual Studio code.
In the next video, I'll show you the steps of going through how we can model a data.