Meeting Transcription

Meeting started: Nov 18, 2024, 1:20:10 PM

Meeting duration: 34 minutes
Meeting participants: 1012 Rakshanda Shamin, 1224_ OZEAR KHAN,
SubhajyotiBarman, anamitra roy 22

View original transcript at Tactiq.

Detailed summary

# Meeting Summary

## Date: \[Insert Date\]

## Participants:

* Subhajyoti Barman

* Alexander

* 1012

* 1224

* Anamitra

## Agenda:

1. Review of user stories and acceptance criteria.

2. Discussion on epic categories and user roles.

3. Planning for development tasks and database structure.

4. Backend API structure and deployment options.

### Key Discussions:

#### 1\. User Stories and Acceptance Criteria

* **Status Update**: Alexander shared the current status of user stories,

indicating that only admin-related stories were completed. He plans to work on
student and faculty stories soon.

* **Action Item**: Finalize user stories and acceptance criteria promptly to

initiate the development process.

#### 2\. Epic Categories and User Roles

* **Epic Identification**: The team discussed the need to narrow down epic
categories to facilitate user story development.

* **User Roles Identified**: The primary user roles include:

* Students

* Teachers

* Parents

* Administrators
 * Heads of Departments (HODs)

* Teaching Assistants/Lab Helpers

* **Recommendation**: User stories should be framed from the perspective of

user roles rather than system functionalities to ensure clarity for end users.

#### 3\. Development Planning

* **Initial Focus**: The team agreed to prioritize the development of admin-

related user stories, as they are foundational for other functionalities.

* **Database Structure**:

* The team was tasked with identifying a rough database structure using an
Entity-Relationship Diagram (ERD).

* Emphasis was placed on careful planning to avoid extensive modifications

later in the development process.

#### 4\. Backend API Structure

* **Technology Stack**:

* Frontend: React

* Backend: Express

* **API Development**:
 * The team discussed the importance of structuring the backend APIs
modularly, separating middleware and controllers for better organization.

* A sample project structure was reviewed, and suggestions for improvements

were made.

#### 5\. Deployment Options

* **Deployment Platforms**:

* Options discussed included Render and AWS for hosting the application.

* The team acknowledged the need for guidance in DevOps and deployment
processes.

* **Database Considerations**:

* Concerns were raised about using free database services due to potential
limitations on data storage.

* MySQL was suggested as a reliable option for long-term use, with the
possibility of self-hosting on a virtual machine.

### Action Items:

1. Finalize user stories and acceptance criteria for admin, student, and faculty
roles.

2. Create a rough database structure using an ERD.

3. Develop a modular backend API structure.

4. Explore deployment options and prepare for potential DevOps challenges.

### Conclusion:

The meeting concluded with a clear plan for the next steps in the project,
focusing on user story finalization, database structure, and backend
development. The team agreed to reconvene to discuss progress and any
challenges encountered in the upcoming week.

Highlights

01:17 1012 Rakshanda Shamin: So, at the last moment, we have only are done.
Done the user stories as a admin sir, which I have already shared it to you by
tonight. I'll walk up on the rest of the topics like, as a student. And as a faculty
also,
02:00 1224_ OZEAR KHAN: issue. Like I'll share you this notion page. so, we
are facing an issue, like, if you could Narrow down epic categories. So this
would be then easier for us to work on the user stories.
02:24 1224_ OZEAR KHAN: Yeah, that's why we're facing issue with.
02:28 SubhajyotiBarman: So what kind of issue can you, could
11:42 1012 Rakshanda Shamin: assigning, the roles to the faculty.
14:51 SubhajyotiBarman: Hmm. Then from the department. You have to create
the schedule. That means this is the schedule for this class. and within, And
during scheduled creation, you have to assign faculty. For that class, right?
24:53 SubhajyotiBarman: so, I will see here that By tomorrow. Okay. Then we
can see here the idea over Whatsapp.
26:35 SubhajyotiBarman: Okay. And do you have any idea regarding this
Github?
26:38 1224_ OZEAR KHAN: Yeah, we have the code in our github, only.
32:12 SubhajyotiBarman: Certain amount of you. after that, we will face issue
 and 500 MB is not very much Very large amount of data, right? It will get filled
very quickly.
32:56 SubhajyotiBarman: Okay, so In the next week, we will discuss this thing
further.
33:47 SubhajyotiBarman: Right. Right. Later on. We will add more complexity
within that thing. As per our requirement, we will face issue. In that case, we
will create new

Notes

us -6 add create faculty

us-8 opt out
add us to register resources
us to create subject creatattion

just User roles are

Admin
Faculty
Student

ERD

Transcript

00:00 1224_ O.K.: I'll just call them to join this meet.
00:03 SubhajyotiBarman : Sure.
01:06 SubhajyotiBarman : Alexander. Could you please share your screen and
show me the final status of the user stories?
01:17 1012 R.S.: So, at the last moment, we have only are done. Done the user
stories as a admin sir, which I have already shared it to you by tonight. I'll walk up
on the rest of the topics like, as a student. And as a faculty also,
01:33 SubhajyotiBarman : Okay, so have you discussed with the with the
developing development team?
01:39 1012 R.S.: I've already discussed it with us.
01:42 SubhajyotiBarman : Okay. So you should perform finalize this thing, user
stories, and their corresponding acceptance criteria as early as possible so that
we can start the development process. So in
01:56 1224_ O.K.: So yeah, regarding that, we have an
01:56 1012 R.S.: Yes.
01:57 1224_ O.K.: Hi everyone, this is an automated message to let you know my
Tactiq extension: https://tactiq.io/r/transcribing is transcribing this meeting for me
so I can give my full attention to you.
01:57 SubhajyotiBarman : the
02:00 1224_ O.K.: issue. Like I'll share you this notion page. so, we are facing an
issue, like, if you could Narrow down epic categories. So this would be then easier
for us to work on the user stories.
02:19 SubhajyotiBarman : So, you at first, you should identify the apex. Have you
identified that thing?
02:24 1224_ O.K.: Yeah, that's why we're facing issue with.
02:28 SubhajyotiBarman : So what kind of issue can you, could
02:30 1224_ O.K.: Like we don't know how much epic
02:30 SubhajyotiBarman : you please remember?
02:32 1224_ O.K.: should be real. Like, if we take the subsystem into account,
Then there should be like, what 14 epics? Under all the subsystems.
02:44 SubhajyotiBarman : The substitution you have identified, those are the top
level view when you start development, probably, there will be more such
subsystems. Okay? So, I will suggest to think this user story from the prospective
of the user roles, don't think, from the perspective of the system, because in the
user story, we write
03:07 1224_ O.K.: Hmm.
03:09 SubhajyotiBarman : User specific requirements, right? So
03:12 1224_ O.K.: Right.
03:12 SubhajyotiBarman : admin admin will think what functionality they want? So
you should write your users tree in this way so that end user can easily validate
them those things from their site. Because users, yeah.
03:25 1224_ O.K.: So, like users, we have for students teachers parents and
administrators. There are only four users, right?
03:33 SubhajyotiBarman : Yeah, from the faculty side, we have H O DS because
hod have some more control over the system. They want to see data from other
users or other faculty also. Others student also. So we need some hoda kind of
role. There exist some teaching assistant or Lab helper. Okay. They should, they
03:58 1224_ O.K.: Yeah.
04:00 SubhajyotiBarman : have some limited role on the system
04:00 anamitra r.2.: Feel.
04:02 SubhajyotiBarman : so you should think in that way.
04:06 1224_ O.K.: Okay, so then we first finalize, the
04:10 1012 R.S.: Third exams would work.
04:11 1224_ O.K.: set of epic.
04:13 1012 R.S.: Exemption.
04:13 SubhajyotiBarman : Exam.
04:16 1012 R.S.: exams also,
04:19 SubhajyotiBarman : Yes, exemption is also required. I will suggest you, I, I
will suggest
04:23 1012 R.S.: Okay, so
04:26 SubhajyotiBarman : to that, identify all the users. Okay, do not write each.
And every user story in the current state, Later on, add the user stories because
because real world scenario, it's happened. That at first, you should identify all
the user stories then you should start development, but those people have
already idea how to develop a system. Okay. So, so they can identify those things
at the initial stays.
04:52 SubhajyotiBarman : Precisely. But for your case, you are not. Very much
familiar with this agile, kind of development. So later on you will identify some
more requirements. Okay. And the system, the development model itself agile, so
that if required we can add them later. Also, I will suggest you to create the admin
related users, stories fast because if we able to create all that resource, then
other can cover it on the system, right? Because if I want to create a class to
upload study materials, so in that case, we need some students we need faculty.
Okay? So those can be done.
05:33 SubhajyotiBarman : If we have all the functionalities in the admin panel,
right? So initially target admin student and
05:39 1224_ O.K.: Okay.
05:43 SubhajyotiBarman : faculty these three rules and at the very beginning, we
have to cover the functionalities for the admin. Later on you can add the user
studies as for the requirement of the system.
05:59 1224_ O.K.: Okay. So here.
06:02 SubhajyotiBarman : if you have any other idea, you can share,
06:07 1224_ O.K.: Now we're getting confused in this. User story section only like
how to proceed with it.
06:16 SubhajyotiBarman : Are so you think in this way suppose you want to deal
with your client?
06:19 1224_ O.K.:
06:22 SubhajyotiBarman : Okay, they are assumed. They are non-technical
persons.
06:26 1224_ O.K.: Okay.
06:26 SubhajyotiBarman : Assume you are developing this system for any arts
college. They are not familiar with computer related things, okay? So how you will
present
06:34 1224_ O.K.: Right.
06:36 SubhajyotiBarman : your work? So, you should talk to in their own. They will
not understand your technical things. You should say that that, in my system,
there will be this kind of roles. So probably they do all those things manually in
pain and paper, so they will understand. Yes, those kinds of role are already
present in our system. Now, you want to digitize those rules? Okay, next, you
should say that your
07:02 1224_ O.K.: Okay.
07:04 SubhajyotiBarman : admin do this kind of stuff in your Excel.
07:08 1224_ O.K.: Yeah.
07:09 SubhajyotiBarman : like, whenever you Take admission, you write the
student name. Email ID, all those things in a Excel set, so we will. Upload that
excelsior in our system and it will create digital version of the students in the
system. Okay, now you will also create user profile so that those students can
login into the system and check what are the Available functionality in THERE
Dashboard.
07:42 1224_ O.K.: Hmm.
07:42 SubhajyotiBarman : So those functionality are related to the students. So,
as a student, I can login into the system, I can check, which is my present class,
which course are already registered for that course for that class. Okay, I can
check. What are the
07:57 1224_ O.K.: Right.
07:59 SubhajyotiBarman : study? Materials are already uploaded. What is the
schedule? So these are the end user view of the system. So you should write all
the user story from the end user prospective so that in user can easily
understand the Users today and using the their corresponding acceptance
criteria. They can validate whether that users story is implemented properly or
not.
08:26 1224_ O.K.: Okay, so
08:27 1012 R.S.: So so sorry to interrupt so, but I've
08:28 SubhajyotiBarman : What it? Yeah.
08:31 1012 R.S.: already shared you one PDF about the user stories of like as
admin so was that the perfect one like can we follow that pattern or else like what
else we need to add on it. So
08:46 SubhajyotiBarman : I already approved this thing, and I mentioned that, you
from your admin panel, you can now create only the students So, all the users
stories are related to the students, but admin will also create the faculty. They
also create the resources, like what are the class?
09:07 1012 R.S.: You know, like the admin is one thing you who can access the
students database, the faculties database and everything.
09:14 SubhajyotiBarman : I just suggest you to extend this user story list so that
we can have other functionalities also. Because Admin will not manage only the
students, but also they will manage faculty as well as the resources. Resources
means classroom and lab seminar hall. This kind of things
09:35 1012 R.S.: Class allotments or the events, which are going to have done the
seminar, all all those things.
09:43 SubhajyotiBarman : No. And will not do that. That thing they will upload
that these are the available classroom. Okay. Now, when
09:49 1012 R.S.: Okay.
09:49 SubhajyotiBarman : Someone from the department wants to create the
serials. They will have the access. The so from the prospective of the system, all
are the objects define kind of objects student objects, are there. So you need
faculty objects. Also in the system, you also need some object to represent the
class. Classrooms. Then only I can create the schedule.
10:13 1224_ O.K.: All right.
10:14 SubhajyotiBarman : So, and admin will just registered
10:15 1012 R.S.: Yes.
10:18 SubhajyotiBarman : those resources in the system.
10:23 1224_ O.K.: So from the current document could
10:23 SubhajyotiBarman : so, these
10:25 1224_ O.K.: you lists are the missing? Functionalities.
10:29 SubhajyotiBarman : I already mentioned in the word so
10:30 1224_ O.K.: Okay.
10:31 SubhajyotiBarman : you can check that you specify on user stories related
to the student kind of object. Right. Past one admin, login. So using this they can
get access to their dashboard. Next is enroll news student, so if they want to add
a single student. So this user story will work, what is the third one? Probably the
bulk update someone. Yeah. So this is the bulk update. Okay? Now, update
student records, if some is data is missing or wrong entry, are there they can
update, okay? Delete option is also there.
11:11 SubhajyotiBarman : Then reset password that is also present. So this is
related to student probably
11:19 1224_ O.K.: Right.
11:19 SubhajyotiBarman : Configure. Yeah. Next is Configure System Role. What is
the meaning of this point?
11:26 1224_ O.K.: like who has like golf faculty or teachers or a student giving the
access Like this is this account is for teacher so they will get the access for
teacher level.
11:40 SubhajyotiBarman : Okay. So before
11:40 1012 R.S.: Basically saying here, the admin is
11:42 SubhajyotiBarman : That.
11:42 1012 R.S.: assigning, the roles to the faculty.
11:47 SubhajyotiBarman : Okay, so before that, you should have one user story to
create the faculty.
11:52 1224_ O.K.: Okay.
11:53 SubhajyotiBarman : Right. Then generate audit logs. What is the meaning of
this thing? That means is it implementable? That's my question. At the initial
stage. What is the
12:04 1224_ O.K.: Yeah.
12:06 SubhajyotiBarman : meaning of audit? Look.
12:09 1224_ O.K.: This could be opted out.
12:10 SubhajyotiBarman : so, if the task is too much complicated, you have to
Eliminate that thing from from your current list, or you should decompose this
thing if I want to generate audit logs, what are the steps? Probably, this is, not an
atomic task right in the user story. I, we
12:24 1224_ O.K.: Right.
12:28 SubhajyotiBarman : provide atomic task So, for the timing you can skip it.
12:33 1224_ O.K.: Okay.
12:33 SubhajyotiBarman : Next, same notification to the users which kind of
notification. Any message.
12:41 1224_ O.K.: Oh, yeah, any or any or notification admin want to send like a
system? Is going to be down or any anything?
12:47 SubhajyotiBarman : Any notice or
12:47 1224_ O.K.: Regarding that. Yeah.
12:50 SubhajyotiBarman : University level notice also can be circulated using this
option, Okay
12:52 1224_ O.K.: Right.
12:53 SubhajyotiBarman : that's good. Next is export student data so this is for
backup per purpose, right?
12:59 1224_ O.K.: Right.
13:02 SubhajyotiBarman : Okay, so, basically the faculty creation uses story is not
present and we also need to register resources. that means how many
classrooms are
13:12 1224_ O.K.: Okay.
13:14 SubhajyotiBarman : available because if I want to create a schedule, For the
for any class I have to check. Now what are the room available?
13:21 1224_ O.K.: Hmm.
13:22 SubhajyotiBarman : I should have one log where I can check. What are the
room available? When I will allocate that resource
13:27 1224_ O.K.: Right.
13:30 SubhajyotiBarman : for that given time letters. If someone try to Access
that room in that same timing, it should show that this is occupied.
13:40 1224_ O.K.: Okay.
13:41 SubhajyotiBarman : Right? So for that purpose, what you have to do, we
have to register the resource. So, that should be done from using that user story.
13:49 1224_ O.K.: Okay.
13:51 SubhajyotiBarman : Or using that option present in my Advent dashboard.
13:56 1224_ O.K.: So there are three user first is to
13:56 SubhajyotiBarman : Right.
13:58 1224_ O.K.: create the faculties. Then we could opt out the user story 8.
This auditing one and we have to create one user story for registering resources.
Anything else are from the Admin panel.
14:14 SubhajyotiBarman : For the timing. It is. Okay, later. Probably we have to
add. We will identify new things. Okay.
14:19 1224_ O.K.: Okay.
14:20 SubhajyotiBarman : For the private, think our system will be very basic with
very basic functionalities. So at first admin will register student faculty and
classrooms later.
14:31 1224_ O.K.: Okay.
14:34 SubhajyotiBarman : of faculty can be assigned to a specific class for For
specific subject. So that means subject creation or course creation, that will be
another functionality of the admin, right?
14:48 1224_ O.K.: Just to create. Subject creation. Okay.
14:51 SubhajyotiBarman : Hmm. Then from the department. You have to create
the schedule. That means this is the schedule for this class. and within, And
during scheduled creation, you have to assign faculty. For that class, right?
15:11 1224_ O.K.: Okay.
15:13 SubhajyotiBarman : So that can be done from the faculty dashboard.
15:20 1224_ O.K.: so we'll first confirm the Admin Dashboard workflow and then
move on to the faculty and then to the Student dashboard
15:31 SubhajyotiBarman : yeah, that will be Easy for you. Probably? Right.
Because if I think multiple things
15:36 1224_ O.K.: Right.
15:38 SubhajyotiBarman : together it will make your development complicated.
Give me just two minutes. I want to connect my charger. Just
16:21 SubhajyotiBarman : Okay, so These things are related to the project
management now. Your
16:26 1224_ O.K.: Right.
16:27 SubhajyotiBarman : development team, should start working on the
development part.
16:31 1224_ O.K.: Okay.
16:32 SubhajyotiBarman : so first of all, what you have to do, you have to identify
the rough database structure
16:38 1224_ O.K.: Yeah.
16:40 SubhajyotiBarman : Okay. So database structure is represented with the
help of ERD.
16:45 1224_ O.K.: Hmm.
16:45 SubhajyotiBarman : Fine. So you should identify what, what should be the
probability tables and their corresponding attributes?
16:52 1224_ O.K.: Okay.
16:52 SubhajyotiBarman : So initially, you will identify rough structure. Probably
you have to modify these things several times. During the development process.
If your initial identification is good, then less effort will be required later.
Otherwise, you have to make drastic changes, Okay, so think very carefully during
the year development process. Otherwise what will happen you have to make lots
of code modification letter
17:22 1224_ O.K.: Okay.
17:23 SubhajyotiBarman : So, that's your first technical task or technical task
objective in the coming week.
17:30 1224_ O.K.: Alright.
17:31 SubhajyotiBarman : You have to decide what should be the database
structure. With using an ear diagram. Fine. And next one, we will start our
development process from the backend side. Okay.
17:45 1224_ O.K.: Okay.
17:46 SubhajyotiBarman : So we should think, what are the probable? API, that
will be applicable for for the front end. So generally when you learn this next
probably, you will use nexus, right?
18:04 1224_ O.K.: Oh, we were thinking of using react. We could use Nexus if you
say so. But I didn't find any of the use
18:12 SubhajyotiBarman : oh, Yes, you, we discuss it for the front
18:14 1224_ O.K.: case.
18:17 SubhajyotiBarman : end. You will use react. And in the back end, we will use
next. Not next story. What is the name
18:24 1224_ O.K.: Express.
18:25 SubhajyotiBarman : express we will use Express for the
18:26 1224_ O.K.: Yeah.
18:28 SubhajyotiBarman : vacant. So, if you watch any tutorial regarding this
express, you will identify that they just create a single file and write all the APIs as
a single function. But that's not the proper way you, you should split the task into
multiple level.
18:48 1224_ O.K.: Okay.
18:50 SubhajyotiBarman : Okay, so you should think, what should the structure of
your backend API? In which folder you will store. Which data at first, do some
research, then I will provide my point of view. You should you should initially do
some identity regarding this thing. What? Should be the structure of the backend
system then I will make rectification on it.
19:14 1224_ O.K.: Okay, basically high level structure
19:15 SubhajyotiBarman : If we could.
19:17 1224_ O.K.: follows like there was one folder for models. Models which in
which files are for database is our present, like any credit applications are present
in model. And we keep it, we keep the endpoint folder, very generic like we just
inside the routes to it. And we do not. Specify the general logic to it. We use
middleware another folder middleware. Which where we implement the logic.
19:47 SubhajyotiBarman : Okay.
19:48 1224_ O.K.: And keep the route simple. We just import the middleware and
specify the specific routes and endpoints for the application. So I may have one
project. I could
20:00 SubhajyotiBarman : Could you please?
20:02 1224_ O.K.: you show you then we could Discuss. Like what other
improvements we could use? Just let me find that project. System back. In just a
moments.
20:21 SubhajyotiBarman : just,
21:29 1224_ O.K.: Is my screen visible.
21:36 SubhajyotiBarman : You know, is it visible?
21:37 1224_ O.K.: Yeah. So for this software, we follow this backend structure. So
I mean this maybe too much structure for it, for all the use cases like the Chat Aiv
implemented in the foldering chart API. So this consists all of the chat API logic.
And we keep the routes, very clean. Like there is an yeah.
22:02 SubhajyotiBarman : Hmm, show me the route.
22:05 1224_ O.K.: We use router then we export just the router. so, in our
services, this is the main Routing page. So on, this is a cluster because we use
socket io. So this was added here, the main routes are here. So, I have exported
routers specifically. And these routers have been defined in this folder routes. So
this is for the Auth. So any endpoints which is, which is, which are for
authentications are here, present in this auth folder,
22:42 SubhajyotiBarman : Okay.
22:42 1224_ O.K.: This is easier for us to for versioning. Also here, we could
version our APIs. so, Yeah.
22:52 SubhajyotiBarman : So this is for the root.
22:54 1224_ O.K.: About right.
22:55 SubhajyotiBarman : Route.
22:59 1224_ O.K.: This is the consultation route.
23:02 SubhajyotiBarman : Then controller. Where is the controller folder?
23:06 1224_ O.K.: Yeah, controller are specifically defined in middle wheels
sections.
23:10 SubhajyotiBarman : Okay, we should split this thing middleware and
controller in separate separate folder. Otherwise it will
23:17 1224_ O.K.: Okay.
23:18 SubhajyotiBarman : get complicated now because our specific task must be
done from a specific function. You should not collaborate multiple things together.
23:28 1224_ O.K.: Okay.
23:30 SubhajyotiBarman : I will provide one updated, modified structure. And we
will discuss if you want any modification. You can do that thing. Okay, but what is
my objective? I want to make all
23:43 1224_ O.K.: Welcome.
23:43 SubhajyotiBarman : the things modular.
23:46 1224_ O.K.: All right.
23:46 SubhajyotiBarman : A single module, should not merge two things. Within it.
23:52 1224_ O.K.: Okay.
23:52 SubhajyotiBarman : They should have only a specific task. and after
middleware, Next, what do we have? From this part how to access database next
in, which file it will transfer the control.
24:09 1224_ O.K.: oh,
24:09 SubhajyotiBarman : after this video delivered, Service.
24:13 1224_ O.K.: Yeah. This is the main.
24:14 SubhajyotiBarman : Where is the service folder?
24:17 1224_ O.K.: Server. This is where we implement all the logic and I exported
in App. Middleware, here we have initialized our routes
24:30 SubhajyotiBarman : I'm not saying that this is not well structured, but in
some place, some modification may enhance the quality of this structure. So
24:39 1224_ O.K.: Okay.
24:41 SubhajyotiBarman : I will share one of my idea with you,
24:43 1224_ O.K.: Okay.
24:43 SubhajyotiBarman : okay? And discuss. And if any modification required in
that thing, we can merge. These two idea. That is also possible.
24:52 1224_ O.K.: Yeah.
24:53 SubhajyotiBarman : so, I will see here that By tomorrow. Okay. Then we can
see here the idea over Whatsapp.
25:01 SubhajyotiBarman : So basically, you know, how to create
25:02 1224_ O.K.: alright, so
25:04 SubhajyotiBarman : the backend APIs. So based on the user stories of the
admin, you can start working on the API development, but
25:13 1224_ O.K.: First, we need to find the database,
25:13 SubhajyotiBarman : Okay, after final finalize. The structure
25:16 1224_ O.K.: right?
25:18 SubhajyotiBarman : Yes.
25:19 1224_ O.K.: so first
25:19 SubhajyotiBarman : First part is to define the year D. Then we have to
finalize the structure.
25:25 1224_ O.K.: Right.
25:25 SubhajyotiBarman : We will try to fix this structure then we can start
working on the API development and Probably where you will deploy this code. In
the local, even what?
25:38 1224_ O.K.: Yeah, for the deployment. We could use. render, if we could go
for AWS also like, but, Render would easier.
25:49 SubhajyotiBarman : Yesterday. Okay.
25:51 1224_ O.K.: For backend and for front end for sale.
25:58 SubhajyotiBarman : Okay, but It is that you also possible. If I if we use AWS
don't you think this is better? Because in the AWS we can host our Fontana and
back and both the thing. And student version is freely
26:15 1224_ O.K.: Yeah.
26:16 SubhajyotiBarman : available.
26:19 1224_ O.K.: Yeah, then we may need guidance in Devops and deployment
part.
26:25 SubhajyotiBarman : Okay, we can sit together and fix this thing. And you
already know these two platform, right?
26:33 1224_ O.K.: Right.
26:35 SubhajyotiBarman : Okay. And do you have any idea regarding this Github?
26:38 1224_ O.K.: Yeah, we have the code in our github, only.
26:44 SubhajyotiBarman : So, how many developers are in your team? You and
26:49 1224_ O.K.: Oh, that's right. He's the front end developer. Akash will also
help. In the front end.
26:55 SubhajyotiBarman : in the in the backend system talking
26:58 1224_ O.K.: Oh, I'm there. So.
26:58 SubhajyotiBarman : about
27:01 1224_ O.K.: Only.
27:01 SubhajyotiBarman : Okay.
27:03 1224_ O.K.: So, this is the
27:03 SubhajyotiBarman : There is no other backend developer. Okay, fine.
27:06 1224_ O.K.: For a project. This the projector I have showed you in the local
post. And this is the deployed version of it.
27:22 SubhajyotiBarman : What is the day and database structure for this project?
Could you please show me?
27:27 1224_ O.K.: Yeah, I may have to look. Okay. I don't remember where I saved
it. Not this.
27:53 SubhajyotiBarman : Okay, fine. I can assume that you have basic idea how
to create here it is and all the dependencies management thing. You can handle
that thing, right?
28:00 1224_ O.K.: Yeah. Yeah. This is all. quite a complicated one, because Along
with the storing the user credentials. We Also need to store this. Information of
the given symptoms here. This should be also stored and Could be given back to
the user. so, it's data was
28:25 SubhajyotiBarman : So in the in the backend RDBMS is present or no, SQL
kind of thing.
28:30 1224_ O.K.: Rdma. So we have used Prisma.
28:35 SubhajyotiBarman : Okay.
28:41 1224_ O.K.: Put it, please not be easier to configure and you could sort of
the deployment part later on.
28:49 SubhajyotiBarman : Please, my is not free, probably after certain usage, it
will ask some registration fees like this or it's
28:58 1224_ O.K.: Now 500.
28:58 SubhajyotiBarman : entirely free.
29:01 1224_ O.K.: Prisma is used for ORM for the database. We have used neon
dB, neon, dB allowed for about 500, MB of database. Free database. The Free
Model 500, MB. And please, we proud recently. Introduces, Database rdb. Initially,
it was only used for ORM only. so, We could use neon. DB for our database.
29:35 SubhajyotiBarman : No. You try to understand the problems let's say you
you use a free version for your initial initial task
29:41 1224_ O.K.: Yeah.
29:42 SubhajyotiBarman : but later on when I we will keep in adding new features
to this project. So later on it will we have to pay the money now. So, I want to use
one technology which will remain free forever.
29:58 1224_ O.K.: Okay.
29:59 SubhajyotiBarman : So, for that purpose, we can go for my school.
30:03 1224_ O.K.: Okay.
30:06 SubhajyotiBarman : And I have some other idea by which we can
implement our own word in without using any third-party things. So, I can
provide technical help in that part.
30:19 1224_ O.K.: So okay. Got it.
30:23 SubhajyotiBarman : And I have realized one thing most of the time we have
to write complicated query. And those scenario, we have to write our own custom
SQL syntax, most of the time, what? I'm kind of features failed there. What is
okay, if I have very simple logic for their
30:40 1224_ O.K.: Yeah, like credit operations.
30:42 SubhajyotiBarman : dinner. So for that reason, if I Want to write Select start
from this table. Why should I use Word? It's better to always rely on the custom
SQL because you have lot. Too much freedom, you can precisely specify. What is
your requirement if I have custom SQL?
31:00 1224_ O.K.: Yeah.
31:03 SubhajyotiBarman : Many people like who are in but I'm not very much fan
of this thing. Okay.
31:08 1224_ O.K.: Yeah, I agree with you.
31:11 SubhajyotiBarman : So we can do one thing we can use. MySQL for the data
storage and in such, you know, we can write our own query. For the execution
purpose. For the data interval or modification purpose.
31:25 1224_ O.K.: So this my school. Do they provide deployed database? We do,
we need to host it.
31:37 SubhajyotiBarman : so suppose you, if you get the server in the server, you
can install your MySQL
31:42 1224_ O.K.: All right.
31:44 SubhajyotiBarman : Okay, so this is like normal software, installation.
31:47 1224_ O.K.: yeah, but the point
31:48 SubhajyotiBarman : In your server. Okay, after that, what you have to do if
you have local database, so you just export the entire database in a single SQL
file, and then just run that file in the server. So you will get the Enter database in
your server.
32:04 1224_ O.K.: Okay.
32:06 SubhajyotiBarman : you can use that approach also, but if I, if I use any
software which is free for,
32:12 1224_ O.K.: Certain amount of.
32:12 SubhajyotiBarman : Certain amount of you. after that, we will face issue and
500 MB is not very much Very large amount of data, right? It will get filled very
quickly.
32:25 1224_ O.K.: Time. So for the deployment purpose we would go for AWS,
right? Or azure
32:32 SubhajyotiBarman : Hmm.
32:34 1224_ O.K.: And we'll get a virtual instance of a machine and host, our front-
end backend and database. On that machine.
32:41 SubhajyotiBarman : Wait wait.
32:43 1224_ O.K.: Okay, so
32:43 SubhajyotiBarman : So that means we will have one Linux machine in the
server. Now we can do anything on it, just like our local system.
32:50 1224_ O.K.: Yeah.
32:51 SubhajyotiBarman : So that's my idea.
32:52 1224_ O.K.: Yeah, got it. So
32:56 SubhajyotiBarman : Okay, so In the next week, we will discuss this thing
further.
33:01 1224_ O.K.: Yeah.
33:01 SubhajyotiBarman : So for the timing complete this year, depart and I will
see, are the, what is called? The structure of the backend system? The
architecture.
33:11 1224_ O.K.: Okay.
33:12 SubhajyotiBarman : And we will refine it. Put.
33:15 1224_ O.K.: Okay.
33:16 SubhajyotiBarman : That any other query from? For this meeting. From
other members.
33:22 1224_ O.K.: No, I think for the admin panel, we have already noted down. To
add some user stories and opts. so basically there are what if I have to name user
rules. There is admin. Then faculty. Then student, right? So currently we are
working on admin. The story, so we'll complete the admin user stories then move
on to the faculty dashboard. And then to the student dashboard.
33:47 SubhajyotiBarman : Right. Right. Later on. We will add more complexity
within that thing. As per our requirement, we will face issue. In that case, we will
create new
33:57 SubhajyotiBarman : users,
33:58 1224_ O.K.: Okay.
34:00 SubhajyotiBarman : User roles, right? Right.
34:02 1224_ O.K.: Right. And then there is another task, which is ERD, right? Okay,
so that's it for this week.
34:10 SubhajyotiBarman : Okay. Sure. Okay, bye. Take care of you.
34:14 1224_ O.K.: Okay, so thank you. So,
34:15 1012 R.S.: Thank you.

View original transcript at Tactiq.