Database Management System
Database Management System
Submi ed by
John Doe (20B1234)
Mary Brown (20C2235)
August 2021
Abstract
This report describes the implementa on of a Database Management System for
Janata Mul ple Campus. It was developed for Storing, Managing, and Upda ng
the Data that the Campus generates.
This report mainly includes the background and development process of the
project. The main steps in the development process are iden fying the En es
and the Rela onship among them and presen ng them in graphical form with an
ER Diagram. It also includes some of the SQL queries used in the implementa on
of the MySQL Database.
This project can be useful for JMC and other similar ins tu ons.
ACKNOWLEDGEMENTS
We are very pleased to present the report “Database Management System for Janata
Mul ple Campus” which has been prepared for the par al fulfilment of the Bachelor of
Business Management (BBM).
We would like to express our deep gra tude to the report supervisor Lecturer Mr. Alex
for his guidance, and supervision.
We are also thankful to Campus chief Dr. James for advising throughout the en re
semester and the program in charge of BBM, Mr. Peter, for his con nuous support
during the period of the project work.
Table of Contents
Introduc on ……………………………………………................ 5
Background ……………………………………………….…….... 7
ER Diagram …….…….…….…….…….…….…….…….……….. 12
Summary …….…….…….…….…….…….…….…….…….……. 45
Problem Statement
Currently, JMC uses two methods for Managing its Database.
● Tradi onal Pen and Paper Method
● File Management System in Computer
Duplica on of Data
The Records of the Students are being Duplicated in Accounts, Library and other
Departments.
Update Issues
The updates have to be done in mul ple places and there is no proper system to
check if it is updated correctly everywhere.
No Backup
There is no backup system which means the Campus is always at a risk of losing
Data completely or par ally.
Besides, this project can also be used to Integrate the Data with an MIS
Applica on in the future.
Background
The project uses the following technologies.
DBMS: MySQL
MySQL is an open-source rela onal database management system (RDBMS).
XAMPP
XAMPP is a stack of so ware that provides easy access to MySQL.
phpMyAdmin
phpMyAdmin is an open-source client for MySQL. It provides the func onality of
opera ng and managing Databases in MySQL.
Books
For understanding the theory of DBMS and SQL, we took the following books for
reference.
1. Saud, A.S and Saud, B.S (2073). Introduc on to Database System. Kri Books
Publishers & Distributors Pvt. Ltd., 2nd ed
2. Abraham Silberchatz, Henry F. Korth, S.Sudarshan; Database System
Concepts. McGraw Hill, 6th ed
● En es and En ty Sets
● The A ributes of those En es
● Rela onships among those En es
ER Diagram
The core of the ER Model is the En ty-Rela onship Diagram (ER Diagram), a
graphical representa on of the ER model. It is like a blueprint of a database.
1. Department
2. Program
3. Student
4. Lecturer
5. Subject
A ributes
The Proper es of an en ty are called A ributes. The a ribute(s) which can
uniquely iden fy the En ty is called Primary Key. The main A ributes of all the
above En es are listed in the table below. The Primary Keys are underlined.
En ty A ributes
Department_Id
Department Department_name
HOD
Program_Id
Program_name
Program No_of_years
Total_fees
Program_coordinator
Student_Id
Roll_no
First_name
Last_name
Gender
Contact_number
Student
Email_address
DOB
Country
City
Street
Ward_no
Lecturer_Id
First_name
Last_name
Gender
Lecturer
Contact_number
Email_address
DOB
Designa on
Country
City
Street
Ward_no
Subject_Id
Subject_Code
Subject Subject_name
Credit_hours
Total_Preiods
ER Diagram
Note: The diagram is shown stepwise to make it easy to understand. You can
directly put the final ER Diagram in your project.
ER Diagram: Step 1
ER Diagram: Step 2
ER Diagram: Step 3
ER Diagram: Step 4
ER Diagram: Step 5
ER Diagram: Step 6
Note: Some A ributes of Student and Lecturer en es are not present in the ER Diagram. They
have been excluded to avoid the over-complexity of the ER Diagram.
Department
Department_Id Department_name HOD
Program
Program_Id Program_name No_of_years Total_fees
Program_coordinator Department_Id(FK)
Step 2: Lecturer
There is a ‘Many to Many’ Rela onship between the Department and Lecturer. So,
we will create a new table for Works For Rela onship. Also, we will create a
separate table for Contact_number as it has mul ple values.
Lecturer
Lecturer_Id First_name Last_name Gender Email_address DOB Designa on
Lecturer_Works_For_Department
Lecturer_Id(FK) Department_Id(FK)
Lecturer_Contact_number
Lecturer_Id(FK) Contact_number
Step 3: Student
There is a ‘One to Many’ Rela onship between Program and Student. So, we use
Program_Id as a Foreign Key in the Student table. Also, we will create a separate
table for Contact_number as it has mul ple values.
Student
Student_Id Roll_no First_name Last_name Gender Email_address DOB
Student_Contact_number
Student_Id(FK) Contact_number
Step 4: Subject
There is a ‘Many to Many’ Rela onship between Program and Subject. There is
also a ‘Many to Many’ Rela onship between Lecturer and Subject. So, we will
create two separate tables for Specifies and Teaches Rela onship.
Subject
Subject_Id Subject_Code Subject_name Credit_hours Total_Preiods
Lecturer_Teaches_Subject
Lecturer_Id(FK) Subject_Id(FK)
Program_Has_Subject
Program_Id(FK) Subject_Id(FK)
Department
Department_Id Department_name HOD
Program
Program_Id Program_name No_of_years Total_fees
Program_coordinator Department_Id(FK)
Lecturer
Lecturer_Id First_name Last_name Gender Email_address DOB Designa on
Lecturer_Works_For_Department
Lecturer_Id(FK) Department_Id(FK)
Lecturer_Contact_number
Lecturer_Id(FK) Contact_number
Student
Student_Id Roll_no First_name Last_name Gender Email_address DOB
Student_Contact_number
Student_Id(FK) Contact_number
Subject
Subject_Id Subject_Code Subject_name Credit_hours Total_Preiods
Lecturer_Teaches_Subject
Lecturer_Id(FK) Subject_Id(FK)
Program_Has_Subject
Program_Id(FK) Subject_Id(FK)
Table Crea on
Department Table
Program Table
CREATE TABLE Program
(
Program_Id int NOT NULL AUTO_INCREMENT PRIMARY KEY,
Program_name VARCHAR(100) NOT NULL,
No_of_years DECIMAL(2, 2) NOT NULL,
Total_fees DECIMAL(10, 2) NOT NULL,
Program_coordinator VARCHAR(100) NOT NULL,
Department_Id int NOT NULL,
FOREIGN KEY (Department_Id) REFERENCES Department(Department_Id)
);
Lecturer Table
CREATE TABLE Lecturer
(
Lecturer_Id int NOT NULL AUTO_INCREMENT PRIMARY KEY,
First_name VARCHAR(100) NOT NULL,
Last_name VARCHAR(100) NOT NULL,
Gender VARCHAR(15) NOT NULL,
Email_address VARCHAR(320) NOT NULL,
DOB DATE NOT NULL,
Designation VARCHAR(100) NOT NULL,
Country VARCHAR(100) NOT NULL,
City VARCHAR(100) NOT NULL,
Street VARCHAR(100) NOT NULL,
Ward_no int NOT NULL
);
Lecturer_Works_For_Department Table
CREATE TABLE Lecturer_Works_For_Department
(
Lecturer_Id int NOT NULL,
Department_Id int NOT NULL,
PRIMARY KEY (Lecturer_Id, Department_Id),
FOREIGN KEY (Lecturer_Id) REFERENCES Lecturer(Lecturer_Id),
FOREIGN KEY (Department_Id) REFERENCES Department(Department_Id)
);
Lecturer_Contact_number Table
Student Table
CREATE TABLE Student
(
Student_Id int NOT NULL AUTO_INCREMENT PRIMARY KEY,
Roll_no int NOT NULL,
First_name VARCHAR(100) NOT NULL,
Last_name VARCHAR(100) NOT NULL,
Gender VARCHAR(15) NOT NULL,
Email_address VARCHAR(320) NOT NULL,
DOB DATE NOT NULL,
Country VARCHAR(100) NOT NULL,
City VARCHAR(100) NOT NULL,
Street VARCHAR(100) NOT NULL,
Ward_no int NOT NULL,
Program_Id int NOT NULL,
FOREIGN KEY (Program_Id) REFERENCES Program(Program_Id)
);
Student_Contact_number Table
Subject Table
Lecturer_Teaches_Subject Table
CREATE TABLE Lecturer_Teaches_Subject
(
Lecturer_Id int NOT NULL,Subject_Id int NOT NULL,
PRIMARY KEY (Lecturer_Id, Subject_Id),
FOREIGN KEY (Lecturer_Id) REFERENCES Lecturer(Lecturer_Id),
FOREIGN KEY (Subject_Id) REFERENCES Subject(Subject_Id)
);
Program_Has_Subject Table
Final Tables
Data Inser on
Inser ng in Department Table
(`Program_name`,`No_of_years`,`Total_fees`,`Program_coordinator`
,Department_Id`)
VALUES ('BBM',4,400000,'Kimberly',2),
('BBA',4,500000,'David',2),
('BSc General',4,250000,'Edward',1),
('BSc CSIT',4,450000,'Jack',1),
('MSc CSIT',2,200000,'Rachel',1),
('BA English',3,100000,'Leonard',3),
('BA Fne Arts',4,400000,'Victoria',3)
('William','Bond','Male','[email protected]','1980-02-14',
'Professor',
'Nepal','Dang','Main Road',5),
('Vanessa','Anderson','Female','[email protected]',
'1982-04-04',
'Professor','Nepal','Kathmandu','Old Baneshwor',2);
Summary
Now the Campus can use the DBMS for Storing, Managing, and Upda ng their
data on a regular basis. This will help them get rid of the Data Duplica on,
Inconsistency and many other issues they were facing due to the use of tradi onal
Methods.
The two main limita ons of this project are it lacks rela ons for Library and
Fees/Billing management. This limita on was caused due to the me constraint.
In the future, we plan to enhance the DBMS so that it can properly handle the
data from the college’s Library and Accounts Sec ons.
h ps://bit.ly/4kxR1p6