Dbms P
Dbms P
Session 2023-24
Submitted
By
Submitted Submitted
By to
KHALID Dr. Sunita Tomar
23SCSE1470004 Associate professor
SCSE
CANDIDATE’S DECLARATION
I/We hereby certify that the work which is being presented in the project, entitled “CAMPUS
MANAGEMENT SYSTEM” in partial fulfillment of the requirements for the award of the BCA (Bachelor
of Computer Application) submitted in the School of Computer Applications and Technology of Galgotias
University, Greater Noida, is an original work carried out during the period of February, 2024 to June 2024,
under the supervision of Dr. Sunita Tomar, Department of Computer Science and Engineering, of School of
The matter presented in the thesis/project/dissertation has not been submitted by me/us for the award of
KHALID (23SCSE1470004)
This is to certify that the above statement made by the candidates is correct to the best
of my knowledge.
CERTIFICATE
This is to certify that Project Report entitled “CAMPUS MANAGEMENT SYSTEM.” which is submitted
by” Khalid” in partial fulfillment of the requirement for the award of degree BCA in Department of Computer
Science School of Computer Applications and Technology, Galgotias University, Greater Noida, India is a
record of the candidate own work carried out by him/them under my supervision. The matter embodied in this
thesis is original and has not been submitted for the award of any other degree
ACKNOWLEDGEMENTS
I am grateful for the guidance and support I received during this DBMS project on campus management. Dr.
Sunita Tomar insightful feedback and encouragement were invaluable in helping me develop a strong
I would also like to thank my fellow BCA classmates for the collaborative discussions and shared
Khalid
(23SCSE1470004)
ABSTRACT
This report describes the implementation of a Database Management System for Galgotia Multiple
Campus. It was developed for Storing, Managing, and Updating 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 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 Galgotias and other similar institutions.
6
Table of Contents
Introduction ……………………………………………................ 5
Background ……………………………………………….…….... 7
ER Diagram …….…….…….…….…….…….…….…….……….. 12
Summary …….…….…….…….…….…….…….…….…….……. 45
7
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
8
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.
9
1. Department
2. Program
3. Student
4. Lecturer
5. Subject
10
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_Id
First_name
Last_name
Gender
Lecturer
Contact_number
Email_address
DOB
Designation
11
Country
City
Street
Ward_no
Subject_Id
Subject_Code
Subject Subject_name
Credit_hours
Total_Preiods
12
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
13
ER Diagram:
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.
14
Department
Department_Id Department_name HOD
Program
Program_Id Program_name No_of_years Total_fees
Program_coordinator Department_Id(FK)
15
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.
Lecturer
Lecturer_Id First_name Last_name Gender Email_address DOB Designation
Lecturer_Works_For_Department
Lecturer_Id(FK) Department_Id(FK)
16
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.
17
Student
Student_Id Roll_no First_name Last_name Gender Email_address DOB
Student_Contact_number
Student_Id(FK) Contact_number
18
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.
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)
19
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
20
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)
21
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)
);
24
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
);
25
26
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)
);
27
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)
);
29
30
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)
);
33
Program_Has_Subject Table
Final Tables
35
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)
37
('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 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.
42