0% found this document useful (0 votes)
3 views

REPORT

The document presents a final project report on the Student Record Management System (SRMS), which aims to centralize and manage student data efficiently. It outlines user requirements, access roles for students, teachers, and administrators, and details the entities involved such as students, courses, grades, and lecturers. The report concludes with plans for future enhancements to the system, including additional functionalities to improve data management and user experience.

Uploaded by

78fcf28vrx
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views

REPORT

The document presents a final project report on the Student Record Management System (SRMS), which aims to centralize and manage student data efficiently. It outlines user requirements, access roles for students, teachers, and administrators, and details the entities involved such as students, courses, grades, and lecturers. The report concludes with plans for future enhancements to the system, including additional functionalities to improve data management and user experience.

Uploaded by

78fcf28vrx
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 11

Fundamental of Databases

Final Project Report

__________________________________________________

Student Record Management


__________________________________________________

Đào Tuyết Ngân [[email protected]]


Nguyễn Lê Minh Đức [[email protected]]
Nguyễn Phạm Quốc An [[email protected]]
Đào Duy Mạnh Hà [[email protected]]
Nguyễn Thế Kiên [[email protected]]
Table of Contents

Table of Contents....................................................................................................................2
Group Info:..............................................................................................................................3
Introduction............................................................................................................................3
User Requirements..................................................................................................................3
Access Roles.....................................................................................................................................3
Students............................................................................................................................................................. 3
Teachers.............................................................................................................................................................4
Administrators....................................................................................................................................................4
Entities............................................................................................................................................4
Student...............................................................................................................................................................4
Course................................................................................................................................................................ 4
Grade..................................................................................................................................................................5
Lecturer.............................................................................................................................................................. 5

ERD.........................................................................................................................................5
DB Schema..............................................................................................................................6
Implementation......................................................................................................................7
Delete an entry from the table.........................................................................................................7
Modify an entry from the tables......................................................................................................8
Find student by any field..................................................................................................................8
Get list of students by year/major/course........................................................................................8
Get list of students can apply for scholarship...................................................................................9
Get a list of students need to retake one or more courses..............................................................10
Conclusion and Discussion.....................................................................................................10
References............................................................................................................................11

2
Group Info:
 Đào Tuyết Ngân [[email protected]]
 Nguyễn Lê Minh Đức [[email protected]]
 Nguyễn Phạm Quốc An [[email protected]]
 Đào Duy Mạnh Hà [[email protected]]
 Nguyễn Thế Kiên [[email protected]]

Introduction
For generations, everyone and especially students all face the same problem: how to manage
their data. The problem is that the data is scattered all over the place. It is in different formats,
in different places, and in different systems. It is hard to find, hard to retrieve, and hard to
categorize.

Therefore it should be of utmost importance to have a system that can manage all the data in a
centralized way using SQL and NoSQL

In the following report, we hope to show you how we have solved this problem. We have
developed a database system that can manage all the data in a centralized way. This system is
called the Student Record Management System (SRMS). SRMS will be able to
accept/delete/modify and categorize data regarding students (concerning ID, name, DOB,
address, gender, enrolment year, major and email), courses (concerning course ID, name,
weight of attendance, midterm and final, lecturer ID, course year and ECTS), lecturers
(concerning ID, name, email and phone number), and grade (concerning student ID, course ID,
attendance, midterm and final). It will also have the ability to retrieve data based on arguments
regarding the key to entities.

This system will not only be able to reduce our dependence on paper, Excel, and other systems,
but also will be able to provide a more efficient way to manage data.

User Requirements

Access Roles
Students
 Read Access
o student table, entries that have ID equal to
their ID: ID, name, DOB, address, gender, enroll_year, major, email.
o lecturer table: lecturer_id, name, email, phone.
o course table: ID, name, ETCs, attendance_weight, midterm_weight, final_weight,
lecturer_id, course_year.
o grade table: student_id, course_id, attendance, midterm, final.

3
Teachers

 Read access:
o student table: ID, name, DOB, address, gender, enroll_year, major, email.
o lecturer table: lecturer_id, name, email, phone.
o course table: ID, name, ETCs, attendance_weight, midterm_weight, final_weight,
lecturer_id, course_year.
o grade table: student_id, course_id, attendance, midterm, final.
 Write access:
o course table, entries that have lecturer_id equal to
their lecturer_id: ID, name, ETCs, attendance_weight, midterm_weight, final_wei
ght, lecturer_id, course_year.
o lecturer table, entries that have lecturer_id equal to
their lecturer_id: lecturer_id, name, email, phone.
o grade table, entries that have course_id of the course that
have lecturer_id equal to
their lecturer_id: student_id, course_id, attendance, midterm, final.

Administrators

 Read/write access:
o student table: ID, name, DOB, address, gender, enroll_year, major, email.
o lecturer table: lecturer_id, name, email, phone.
o course table: ID, name, ETCs, attendance_weight, midterm_weight, final_weight,
lecturer_id, course_year.

Entities
Student
 Student ID (key)
 Student name
 DOB (date of birth)
 Email
 Gender
 Address
 Major
 Year enrolled

Course
 Course ID (key)
 Course name

4
 ECTS
 Course year
 Lecturer
 Assessment
o Attendance weight
o Midterm weight
o Final weight

Grade
 Student ID (key)
 Course ID
 Attendance point
 Midterm point
 Final point

Lecturer
 Lecturer ID (key)
 Lecturer name
 Phone number
 Email
 Course ID

ERD
 Student – Course (many–to-many): Student engages in the course, and many students
can engage in 1 course, or 1 student can engage in many courses.
 Grade – Course (many-to-one): A course can have many points for many students.
 Student – Grade (one-to-one): Students achieve grades when engaging in a course.
 Lecturer – Course (one-to-many): A lecturer can teach in many courses.

5
DB Schema
Table description:
Entity Descriptions
Students Collects information of students
Lecturers Collects information of lecturers
Courses Collects information about the courses
Grades Collects grades of students of the course

6
Implementation

Delete an entry from the table

7
Modify an entry from the tables

Find student by any field

Get list of students by year/major/course

8
Get list of students can apply for scholarship

9
Get a list of students need to retake one or more courses

Conclusion and Discussion


The student record management system's prime function is storing, updating, and retrieving
student records. The system is designed to store student records in a database. The centralized
system will provide a single point of access to student records. The system will allow different
users to access the data efficiently and effectively.

In the near future, the system will be expanded to include other functionalities such as a daily
attendance system to eliminate our dependency on paper, Excel, and other manual systems.
The system will also be expanded to include a student personalized calculator to guide students
toward their desired academic achievement. In addition, it will work towards a more inclusive
range of scholarships and rewards for students.

10
Studying this topic has cleared up many of our misconceptions and opened up a multitude of
learning opportunities for us. It has certainly enlightened us on the journey of widening our
personal field of interest's comprehension.

References
 MySQL Tutorial
 Using Roles - MySQL

11

You might also like