1
00:00:08,250 --> 00:00:17,190
In this video, I'm going to show you the process involved from ideation to data modeling or how we

2
00:00:17,190 --> 00:00:20,700
can transform ideas into data.

3
00:00:20,730 --> 00:00:22,800
So let's get going.

4
00:00:23,160 --> 00:00:24,660
Let's take that.

5
00:00:24,690 --> 00:00:34,230
Lucky for you, you got a contract as a developer and you are going to develop a blog application or

6
00:00:34,230 --> 00:00:36,360
school management application.

7
00:00:36,600 --> 00:00:39,120
Now, what would be the next step?

8
00:00:39,270 --> 00:00:44,200
The next step is you are going to sit down and talk to your client.

9
00:00:44,220 --> 00:00:50,070
So let's say that this is a client and this is you, the developer.

10
00:00:50,370 --> 00:00:56,700
Now, your client is going to tell you the requirements about the application.

11
00:00:56,970 --> 00:01:06,120
The client is going to speak in broad terms, but as a developer, you are going to take those ideas

12
00:01:06,120 --> 00:01:09,570
and then form what is called data modeling.

13
00:01:09,930 --> 00:01:17,940
So after the meeting, meaning that after you got all the client want, now it is up to you and your

14
00:01:17,940 --> 00:01:18,720
computer.

15
00:01:19,050 --> 00:01:24,660
So at this point, we need to think through how you are going to model the data.

16
00:01:25,020 --> 00:01:28,460
For me, sometimes this is how it happens to me.

17
00:01:28,470 --> 00:01:36,600
First, I need to think about how I'm going to model the data, and even when I go to bed, I still

18
00:01:36,600 --> 00:01:40,620
think about how I'm going to model the data.

19
00:01:40,800 --> 00:01:46,310
But lucky for you, I'm going to show you my experience how I model data.

20
00:01:46,320 --> 00:01:54,750
But lucky for you, I'm going to show you my experience, how I model data in a simple way.

21
00:01:54,780 --> 00:01:55,670
So I.

22
00:01:55,680 --> 00:01:56,370
Ready?

23
00:01:56,460 --> 00:01:58,260
Let me show you my techniques.

24
00:01:58,290 --> 00:01:59,100
Great.

25
00:01:59,640 --> 00:02:07,220
The first point is what you call the planning stage, and that is what we have done by sitting with

26
00:02:07,230 --> 00:02:08,039
a client.

27
00:02:08,039 --> 00:02:16,230
So now that I've got the idea for my client, the next step is I look to give the database name.

28
00:02:16,380 --> 00:02:21,450
So if you don't know database, we have a database and the MongoDB.

29
00:02:21,720 --> 00:02:29,970
So let's say that you are going to build a school management system or a block application, the database

30
00:02:29,970 --> 00:02:32,970
name going to be our school management system.

31
00:02:32,970 --> 00:02:36,900
So first of all, you got the database name.

32
00:02:37,440 --> 00:02:41,850
The next step is called the collection in MongoDB.

33
00:02:42,150 --> 00:02:48,930
So the collection comprises of the individual entities that are related together.

34
00:02:49,290 --> 00:02:52,680
So let's say you are building a school management system.

35
00:02:52,680 --> 00:02:53,700
Definitely.

36
00:02:53,700 --> 00:02:55,170
You need students.

37
00:02:56,000 --> 00:03:05,090
So student here is one collection and courses is one collection and staff is also one collection.

38
00:03:05,090 --> 00:03:12,740
So now you know all this collection based on the client what needs so you've got know the collection

39
00:03:12,770 --> 00:03:14,900
during the planning stage.

40
00:03:15,140 --> 00:03:15,980
Do you get it?

41
00:03:15,980 --> 00:03:16,640
Yes.

42
00:03:16,640 --> 00:03:22,820
So now the next step is this is what we call the database relationship.

43
00:03:23,270 --> 00:03:27,800
See that I've given it a question mark because we are going to cover it in details.

44
00:03:27,830 --> 00:03:29,000
So what do I mean?

45
00:03:29,000 --> 00:03:32,090
What I mean is that let's say we have this collection.

46
00:03:32,120 --> 00:03:34,610
Collection number one is for courses.

47
00:03:35,280 --> 00:03:37,260
Number two is for students.

48
00:03:37,500 --> 00:03:39,270
And then, let's say staff.

49
00:03:39,540 --> 00:03:43,170
So how are these collection are related together?

50
00:03:43,500 --> 00:03:45,000
We can say that.

51
00:03:45,000 --> 00:03:52,680
Well, a student can have many courses and a course can belongs to many students.

52
00:03:52,800 --> 00:03:55,610
And this what you call the relationship.

53
00:03:55,620 --> 00:03:59,710
And we have a section to talk about database relationship.

54
00:03:59,730 --> 00:04:01,650
So let's get going.

55
00:04:01,890 --> 00:04:06,680
The next planning stage is what we call the document.

56
00:04:06,690 --> 00:04:13,090
So after you finish the relationship, now it's time to create document.

57
00:04:13,110 --> 00:04:15,950
So we get document from collection.

58
00:04:15,960 --> 00:04:19,579
So document simply means the actual record.

59
00:04:19,589 --> 00:04:27,090
So if we have student collection and then you register one student, that student is now what called

60
00:04:27,090 --> 00:04:28,740
the documents.

61
00:04:29,010 --> 00:04:29,820
All right.

62
00:04:29,820 --> 00:04:36,900
So this is a process involved that you need to take before we even open Visual Studio code.

63
00:04:37,170 --> 00:04:44,070
In the next video, I'll show you the steps of going through how we can model a data.

