Public - Sample Project Report
Public - Sample Project Report
Submitted by
John Doe (20B1234)
Mary Brown (20C2235)
August 2021
Abstract
Video Explanation of the sample project
2
This report mainly includes the background and development process of the
project. The main steps in the development process are identifying the Entities
and the Relationship among them and presenting them in graphical form with an
ER Diagram. It also includes some of the SQL queries used in the implementation
of the MySQL Database.
This project can be useful for JMC and other similar institutions.
ACKNOWLEDGEMENTS
We are very pleased to present the report “Database Management System for Janata
Multiple Campus” which has been prepared for the partial fulfillment of the Bachelor of
Business Management (BBM).
We would like to express our deep gratitude 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 entire
semester and the program in charge of BBM, Mr. Peter, for his continuous support
during the period of the project work.
Table of Contents
Introduction ……………………………………………................ 5
Background ……………………………………………….…….... 7
ER Diagram …….…….…….…….…….…….…….…….……….. 12
Summary …….…….…….…….…….…….…….…….…….……. 45
Problem Statement
Currently, JMC uses two methods for Managing its Database.
● Traditional Pen and Paper Method
● File Management System in Computer
Duplication 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 multiple 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 partially.
Besides, this project can also be used to Integrate the Data with an MIS
Application in the future.
Background
The project uses the following technologies.
DBMS: MySQL
MySQL is an open-source relational database management system (RDBMS).
XAMPP
XAMPP is a stack of software that provides easy access to MySQL.
phpMyAdmin
phpMyAdmin is an open-source client for MySQL. It provides the functionality of
operating 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). Introduction to Database System. Kriti
Books Publishers & Distributors Pvt. Ltd., 2nd ed
2. Abraham Silberchatz, Henry F. Korth, S.Sudarshan; Database System
Concepts. McGraw Hill, 6th ed
Entity-Relationship Model
The Entity-Relationship Model (ER Model) is used to describe the structure of the
Database. It takes into account the following:
ER Diagram
The core of the ER Model is the Entity-Relationship Diagram (ER Diagram), a
graphical representation of the ER model. It is like a blueprint of a database.
1. Department
2. Program
3. Student
4. Lecturer
5. Subject
Attributes
The Properties of an entity are called Attributes. The attribute(s) which can
uniquely identify the Entity is called Primary Key. The main Attributes of all the
above Entities are listed in the table below. The Primary Keys are underlined.
Entity Attributes
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 Lecturer_Id
First_name
Last_name
Gender
Contact_number
Email_address
DOB
Designation
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
Depart Progra
ment m
Student
Lecture
Subject
r
ER Diagram: Step 2
Depart Progra
ment Mana m
ges
Regis
ters Enro
lls
Student
Works Specif
for ies
Lect
ures
Lecture
Subject
r Teac
hes
ER Diagram: Step 3
Depart 1 N Progra
ment Mana m
1 ges
N M
Regis 1
ters Enro
N N lls
Student
Works N
Specif
for ies
Lect
M ures
M N
Lecture M N Subject
r Teac
hes
ER Diagram: Step 4
Program
_Id No_of
Depart Program _years
Dept_ Depar
ment_Id _name Progr
N
1 Man Total_f
name tment am
HOD 1 age ees
N Reg s 1 M Program_
ister Enr coordinato
s N Stude N olls r
nt
Wor N Spe
ks Lec cifie
M
for ture s
Ms N
Lectur N
Subje
M
er Tea ct
che
s
ER Diagram: Step 5
Program
_Id No_of
Depart Program _years
Dept_ Depar
ment_Id _name Progr
N
1 Man Total_f
name tment am
HOD 1 age ees
N Reg s 1 M Program_
ister Stud Enr coordinato
s ent_I
N Stude N olls r
Ro d
ll_ nt Gen
Work no N der
DOB Spe
Email_
s for Lec cifie
M First_na Last_ addres
tur me name s s
M es N
Lectur N
Subje
M
er Te ct
ach
es
ER Diagram: Step 6
Program
_Id No_of_
Departm Program years
Depar
Dept_n ent_Id _name Progr
N
1 Man Total_fe
ame tment am
HOD 1 ages es
N Regi 1 M Program_c
ster Stude Enr oordinator
s N Stude nt_Id N olls
Roll
_no nt
N Ge
Work nd Spe
DOB Email_
s for Lec er cifie
M First_na Last_addres
ture me names s
Ms Contact N Total_Pr
Lectur _numbe
N
Subje eiods
M r
er Tea ct
Subje
Ge
che ct_Id Subject_
Lectu Contact_ Subject Credit_
ndDesignnumber s _Code
name
Firstrer_Id hours
_na Last eration
me _na
me
Note: Some Attributes of Student and Lecturer entities are not present in the ER Diagram. They
have been excluded to avoid the over-complexity of the ER Diagram.
Program
_Id No_of_
Departm Program years
Depar
Dept_n ent_Id _name Progr
1 N
ame tment Man am Total_fe
HOD ages es
Program_c
oordinator
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’ Relationship between the Department and Lecturer.
So, we will create a new table for Works For Relationship. Also, we will create a
separate table for Contact_number as it has multiple values.
Depart
Depart
Dept_n ment_I
ame d ment
HOD
N
Works
for
M
Lectur
er
Lectur Ge Contact_n
nd
First_ er_Id Designaumber
nam Last_ er
tion
e nam
e
Lecturer
Lecturer_Id First_name Last_name Gender Email_address DOB Designation
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’ Relationship 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 multiple values.
Program_Id
No_of_year
Program_nam s
e
Program Total_fees
1 Program_coordin
Enrolls ator
Student_I
d N
Roll_no
Student
Gend
er
DOB Email_addr
ess
First_name Last_na
me
Contact_num
ber
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’ Relationship between Program and Subject. There is
also a ‘Many to Many’ Relationship between Lecturer and Subject. So, we will
create two separate tables for Specifies and Teaches Relationship.
Program
_Id No_of
Program _years
_name Progr
N Total_f
am
ees
M Program_
coordinat
or
Spe
cifie
s
N Total_P
Lectu Subje reiods
M N
rer Te ct
Subj
Ge Contact_
ach ect_I
Subjec
Subject
Lectu _name Credit_
ndDesignnumber es d
t_Cod
Firstrer_I hours
_nad Last eration e
me _na
me
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 Designation
Lecturer_Works_For_Department
Lecturer_Id(FK) Department_Id(FK)
Lecturer_Contact_number
Lecturer_Id(FK) Contact_number
Student
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 Creation
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 Insertion
Inserting 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)
('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 Updating their
data on a regular basis. This will help them get rid of the Data Duplication,
Inconsistency and many other issues they were facing due to the use of
traditional Methods.
The two main limitations of this project are it lacks relations for Library and
Fees/Billing management. This limitation was caused due to the time 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 Sections.
https://bit.ly/4kxR1p6