15IT302J – DATABASE MANAGEMENT

SYSTEMS

SEMESTER V
YEAR: 3RD

Project Title:

Hostel Database Management System

Name & Reg No.:

Mini Yadav – RA1711003011479
Srishti Singh – RA1711003011497
Gandharv Vohra – RA1711003011388

SCHOOL OF COMPUTING
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

SRM INSTITUTE OF SCIENCE AND TECHNOLOGY

SRM NAGAR, KATTANKULATHUR – 603203
KANCHEEPURAM DISTRICT

Page | 1
 INDEX

S.No. Content Page No.

1 Problem Description 3
2 ER Diagram 4-11
3 Table creation using integrity constraints 11-16
4 Queries for retrieving the basic information from the table 16-17
5 Queries for performing different actions on data set 17-18

Page | 2
 Hostel Database Management System

1. PROBLEM DESCRIPTION

As the name specifies “HOSTEL DATABASE MANAGEMENT SYSTEM” is developed for

managing various activities in the hostel. From the past few years the number of educational
institutions are increasing rapidly. Therefore the requirement of hostels is also increasing for
the accommodation of the students studying in the institution. And hence there is a lot of strain
on the persons who are running the hostels.
This particular project deals with the problems on managing a hostel and avoids the problems
which occur when carried manually. Identification of the drawbacks of the existing system
leads to the designing of computerized database system. We can improve the efficiency of the
system, thus overcome the drawbacks of the existing system.
1. Less human error
2. Strength and strain of manual labour can be reduced
3. High security
4. Data redundancy can be avoided to some extent
5. Data consistency
6. Easy to handle
7. Easy data updating
8. Easy record keeping
9. Backup data can be easily generated
The system is designed in favor of the hostel management which helps them to save the records
of the students about the rooms and other things like mess etc. It saves them from the manual
work which is very difficult, for example to find the record of the students, the mess bill of the
students and the information about the students who have left the hostel. All the hostel at
present are managed manually by the hostel office and different data processing is done
manually. Thus there are a lot of repetitions which can be easily avoided. This particular project
deals with the problems on managing a hostel and avoids the problems which occur when
handled manually. We design this system of the hostel management especially for the college
hostel.

Page | 3
2. ER DIAGRAM

Page | 4
 Entities:
1. Hostel
2. Students
3. Fees
4. Room
5. Furniture
6. Mess
7. Mess employee/staff
8. Visitor
Hostel:

Many institutes provide the facility of hostel for boys and girls.
But we are mentioning only boys here , almost all the working is same in both hostels.

Reason:

We are taking the entity named as hostel because from here data will move to other entities
and we will manage the database.
This entity will manage the data of students in hostel.

Attributes:
If we talk about the attributes, there can be many but we have mention only few those will be
more help full to make the project workable and simple.

Datatype And Size:

Each attribute have the suitable data-type and size according to the requirement.

Primary Key:
Building_num because one institute can have more than one block or building so by assigning
the num it will be easy to track the data.

Constraints:
Primary key should be unique and cannot be null.

Page | 5
Data Flow:
Only administrator will get in the system and manage the database and check the status of
students and will allocate the room to new students.
It will also do the check and balance of mess.
The data will move from here to different side like the branches of tree.

Students:
Students will be in hostel or hostel has students.

Reason:
The reason for choosing this entity is that ,student is the main entity in the hostel and we will
keep the database of students and logically related things with the students.

Attributes:
Studend_id, Student_name , father_name,department, room_id, cell_no, age, DOB etc
These are selected so that hostel administration can easily manage the whole information about
student and through different perspectives students can be accessed by hostel management.

Datatype And Size:

Each attribute have the suitable data-type and size according to the requirement.

Primary Key:
Student_id is the primary key and it can’t be null.

Constraints:
Primary key should be unique and cannot be null.
When primary key move to the other relation and join the tables the values should be same.

Data Flow:
The admin will enter the data of students (this entity), on the basis of different attributes like
age, department the administrator will assign the room so that the students of same age fellow
and alike department can share the room.

Page | 6
Room:
Students come in the hostel to get the room.

Reason:
Room will be allotted to different students, so the students can be accessed by the attributes of
room as well.

Attributes:
There can be many attribute in this entity
No_of_students, Students_name, furniture_id ,student_id can be added as a foreign key to
relate the both entities.
As we have composite foreign key this is coming from admin to student and then student to
room.

Datatype And Size:

Each attribute have the suitable data-type and size according to the requirement.

Primary Key:
Room_id is the primary key and it can’t be null.

Constraints:
Primary key should be unique and cannot be null.
As we have composite foreign key in this table which is of boys_hostel_admin and student so
there data-type size and values should be same.

Data Flow:
We can also see that there is a composite foreign key which is of boys_hostel_admin and
student so data will flow from admin to student and student to room.
But in ER diagram we can see there is direct relation of admin and room so admin can retrieve
the condition and data of room directly as well.

Fees:

Page | 7
Obviously when students will live in the hostel they will submit fee.

Reason:
This is weak entity here because if the student will exist then fee will be submitted other-wise
not.
When students will live in hostel there will be fees charges on the monthly basis.

Attributes:
There will be few attributes because it is the weak entity and just made to
keep the fees status of student.

Datatype And Size:

Each attribute have the suitable data-type and size according to the requirement.

Primary Key:
student_id is the primary key and it can’t be null.

Constraints:
student_id is the primary key and foreign key as well. it can’t be null.

Data Flow:
The data will follow the route, admin to student and then fees.
Admin will check the student status by getting in the student entity and fees is a weak entity
attached to the student so admin will be able to check the fees status of student.

Furniture:

Reason:
The reason for adding this entity is to just track the either students are getting the facilities
promised by the institute or not.

Attributes:
Furniture_type: chair, table etc

Page | 8
Datatype And Size:
Each attribute have the suitable datatype and size according to the requirement.

Primary Key:
Furniture_id

Constraints:
Primary key should be unique and cannot be null.
Foreign key (room_id) will be same as values in room relation

Data Flow:
The data come from room boys_hostel_admin will track through it.

Mess:
Students will get the facility of mess

Reason:
Students will get the facility of mess. It can be considered as marketing strategy so more
students will come in this hostel because every hostel do not give this facility.

Attributes:
There will be mess incharge , who will handle the mess, there will be monthly expenses of each
student, students name to know which have got their meal or not.
Mess timing can be added to make the environment much better.

Datatype And Size:

Each attribute have the suitable data-type and size according to the requirement.

Primary Key:
Mess_incharge will be the primary key

Constraints:
Primary key should be unique and cannot be null.
Data Flow:

Page | 9
Admin will check the mess staff and then staff will manage it.

Mess employees:

Reason:
There will be staff in mess and hostel as well.
Some will work in mess and others like sweepers in hostel and many more.

Attributes:
Employee_name, address, salary, cell_no etc are the attributes used in this entity.

Datatype And Size:

Each attribute have the suitable datatype and size according to the requirement.

Primary Key:
Employee_id is used as a primary key.

Constraints:
Primary key should be unique and cannot be null.
Mess_incharge will be foreign key in this table.

Data Flow:
The data will flow from admin to staff and then mess.

Visitors:

Reason:
This entity is added as the extra entity so that our project can be look complete from every
aspect.

Attributes:
Student_id,visitor_name,time_in,time_out,date these are the attributes to check what time
visitor came and when he/she will leave the hostel.

Page | 10
Datatype And Size:
Each attribute have the suitable datatype and size according to the requirement.

Primary Key:
CNIC is considered as primary key.

Constraints:
Primary key should be unique and cannot be null.
Student_id will be the foreign key in this.

Data Flow:

This is the optional entity and data will come from student and admin.
Admin can log in to see the student data in which visitor is also attached with the foreign key
so admin can keep eye on the visitor position of every student.

3. TABLE CREATION USING INTEGRITY CONSTRAINTS

The following tables are created using various integrity constraints like : not null, primary
key, unique key, foreign key, check.
1.SQL> create table boys_hostel
(hostel_id int (10) not null, no_of_rooms int (25) not null, no_of_student int (22) not null,
annual_expences int (25) not null, location varchar (10) not null, constraint a_pk primary key
(hostel_id));
SQL>drop table boys_hostel;
SQL>insert into boys_hostel values
(1001,'25','50','2450000','SRM'),
(1002,'30','60','2740000','SRM'),
(1003,'31','62','2870000','SRM'),
(1004,'22','44','2120000','SRM');
SQL>select * from boys_hostel;

Page | 11
2. SQL>create table room
(room_id int (10) not null, capacity int (10) not null, hostel_id int (10) not null,
name_of_student varchar (40) not null, room_status varchar(10) not null, constraint b_pk
primary key (room_id), constraint c_fk foreign key (hostel_id) references boys_hostel
(hostel_id));
SQL>drop table room;
SQL>insert into room values
(2001,'2','1001','Rahul and Kartik','full'),
(2002,'2','1001','Harsh and Abhijeet','full'),
(2003,'2','1001','Raghav and Mukesh','full'),
(2004,'2','1001','Asif and Hussain','full'),
(2005,'2','1001','Anurag and Ayush','full'),
(2006,'2','1001','Anshuman','not_full'),
(2007,'2','1001','Ashu and Tejan','full'),
(2008,'2','1001','Kritik and Chirag','full'),
(2009,'2','1001','Shubhang','not_full'),
(2010,'2','1001','Faiz','not_full'),
(2011,'2','1001','Gandharv','not_full');
SQL>select * from room;

3. SQL> create table student

(student_id int (10) not null, student_name varchar (40) not null, student_father_name varchar
(40), department varchar (30) not null, address varchar (40) not null, cell_no varchar (20) not
null, student_age int (5) not null, student_DOB varchar (15) not null, hostel_id int (10) not
null, room_id int (10) not null, constraint d_pk primary key (student_id), constraint e_fk
foreign key (hostel_id) references boys_hostel (hostel_id), constraint f_fk foreign key
(room_id) references room (room_id));
SQL>alter table student add constraint dept_pk unique( department);
SQL> alter table student add constraint id_pk check( student_id between 100 and 120);
SQL>drop table student;
SQL>insert into student values
(101,'Rahul','Ravi Kumar', 'CSE', 'Delhi ','03xx-xxxxxxx','20','15-june-93','1001',2001),
(102,' Kartik ','Ranjeet Singh','management','Mumbai','03xx-xxxxxxx','23','13-july-
90','1001',2001),

Page | 12
(103,' Harsh ','Sunil Kumar','management','Bihar','03xx-xxxxxxx','21','13-feb-92','1001',2002),
(104,'Abhijeet','Mohit Iyer',' CSE ','Mumbai','03xx-xxxxxxx','22','1-may-91','1001',2003),
(105,'Raghav,'Manoj Singh','CSE','Jamshedpur','03xx-xxxxxxx','21','19-apri-92','1001',2003),
(106,'Mukesh','Anil Kumar','management','Delhi’,'03xx-xxxxxxx','23','28-may-
90','1001',2002),
(107,' Asif ','M.Tareek','CSE','Kolkata','03xx-xxxxxxx','22','19-april-91','1001',2004),
(108,'Hussain','M.Hassan','CSE','Kolkata','03xx-xxxxxxx','20','1-sep-93','1001',2005),
(109,'Anurag,'Vivek Yadav','management','Allahabad','03xx-xxxxxxx','21','20-sep--
92','1001',2005),
(110,'Ayush','Sanjay Kumar','CSE','Lucknow','03xx-xxxxxxx','22','1-may-91','1001',2006),
(111,'Anshuman,'Anshul Sharma','CSE’,'peshawer','03xx-xxxxxxx','22','1-march-
91','1001',2007),
(112,'Ashu','Alok Kumar','CSE’,'Chennai','03xx-xxxxxxx','23','20-march-90','1001',2007),
(113,'Tejan','Harpeet Singh','CSE','Punjab','03xx-xxxxxxx','21','14-aug-92','1001',2008),
(114,' Kritik,'Aman Patni','CSE','Udaipur','03xx-xxxxxxx','21','20-april-92','1001',2008),
(115,’Chirag’,'Sunil Agarwal', 'Electrical engineering','Thailand','03xx-xxxxxxx','22','2-sep-
91','1001',2009),
(116,'Subhang','Arindam Sharma', 'Electrical engineering','Lucknow','03xx-xxxxxxx','23','2-
jun-90','1001',2010),
(117,'faiz','Aamir Ahmad', 'Electrical engineering','Delhi','03xx-xxxxxxx','21','2-sep-
99','1001',2011);
SQL>select * from student;

4.SQL>create table mess

(mess_incharge_Id varchar (20) not null, monthly_avg_expence varchar (30) not null,
mess_bf_timing varchar (45) not null, mess_dinner_timing varchar (45) not null,
sunday_bf_timing varchar (45) not null, constraint g_pk primary key ( mess_incharge_Id));
SQL>drop table mess;
SQL>insert into mess values
('9321','102400','7:00 AM to 8:45 AM','7:30 PM to 8:45 PM','9:00 AM to 11:00 AM'),
('9322','106400','7:30 AM to 8:45 AM','7:00 PM to 8:45 PM','9:00 AM to 11:00 AM');
SQL> select * from mess;

Page | 13
5. SQL>create table staff
(emp_name varchar (40) not null, emp_id int (20) not null, emp_address varchar (50) not null,
emp_salary int (20) not null, emp_cellno varchar (20) not null, hostel_id int (10) not null,
emp_designation varchar (40) not null, mess_incharge_Id varchar (20), constraint j_pk primary
key (emp_id), constraint h_fk foreign key (hostel_id) references boys_hostel (hostel_id),
constraint i_fk foreign key (mess_incharge_id) references mess (mess_incharge_id));
SQL>drop table staff;
SQL>insert into staff values
('Vinod','8321','Potheri','15000','03xx-xxxxxxx','1001','cook','9321')
('Ramu','8322','Gudvencheri','15042','03xx-xxxxxxx','1001','sweeper','null'),
('Sahil','8323','Potheri','15042','03xx-xxxxxxx','1001','mess manager','9322'),
('Rohit','8324','Potheri','12050','03xx-xxxxxxx','1001','sweeper','null'),
('Kumar','8325','Gudvencheri','18000','03xx-xxxxxxx','1001','technician','null'),
('Mahesh','8326','Potheri','18000','03xx-xxxxxxx','1001','technician','null'),
('Mukesh','8327','Potheri','12050','03xx-xxxxxxx','1001','laundryman','null');
SQL>select * from staff;

6. SQL>CREATE table visitor(

visitor_id int (34) not null, student_id int (10) not null, visitor_name varchar (40) not null,
visitor_time_in varchar (40) not null, visitor_time_out varchar (40) not null, student_name
varchar (40) not null, date_entring varchar (24) not null, constraint k_pk primary key
(visitor_id), constraint l_fk foreign key (student_id) references student (student_id));
SQL>drop table visitor;
SQL>insert into visitor values
(4561,'101','Dhruv','8:45 PM','9:25 PM','Ashwin','1-may-19'),
(4562,'101','Sahil','8:45 PM','9:25 PM','Aman','1-may-19'),
(4563,'105','Ayush','6:50 PM','7:10 PM','Vishal','2-april-19'),
(4564,'106','Uday','2:00 PM','2:30 PM','Vaibhav','2-april-19'),
(4565,'107','Sumanyu','3:24 Pm','4:45 Pm','Rahul','10-april-19'),
(4566,'107','Raghav','10:00 AM','11:00 AM','Rithik','10-april-19'),
(4567,'110','Piyush','2:23 PM','3:08 PM','Bilal','20-april-19'),
(4568,'112','Saksham','3:09 pM','4:43 PM','Sajal','3-may-19'),

Page | 14
(4569,'114','Prateek','7:00 PM','8:45 PM','Harsh','4-may-19'),
(4560,'116','Suhail','8:00 AM','9:56 AM','Kunal','23-april-19');
SQL>select * from visitor;

7. SQL>create table furniture

(furniture_id varchar (34) not null, room_id int (10) not null, furniture_type varchar (40) not
null, constraint m_pk primary key (furniture_id), constraint n_fk foreign key (room_id)
references room (room_id));
SQL>drop table furniture;
SQL>insert into furniture values
('AK97','2001','bed'),
('AK98','2001','study chair'),
('AK99','2002','bed'),
('AK10','2002','study chair'),
('AK11','2002','study table'),
('AK12','2003','bed'),
('AK13','2004','study chair'),
('AK14','2004','study table'),
('AK15','2004','bed'),
('AK16','2005','bed'),
('AK17','2006','study chair'),
('AK18','2006','study table'),
('AK19','2006','bed'),
('AK20','2007','bed'),
('AK21','2007','study table'),
('AK22','2008','bed'),
('AK23','2008','study chair');
SQL>select * from furniture;

8. SQL>create table Fee

Page | 15
(fee_year varchar (40) not null, fee_status varchar (40) not null, student_id int (10) not null,
student_name varchar (40) not null, constraint o_pk primary key (fee_month_year,student_id),
constraint p_fk foreign key (student_id) references student (student_id));
SQL>drop table Fee;
SQL>insert into Fee values
('2019','paid','101','Raghav'),
('2019','not paid','102','Chirag'),
('2019','paid','103','Ashu'),
('2019','not paid','104','Anshuman'),
('2019','paid','105','Faiz'),
('2019','paid','106','Tejan'),
('2019','piad','107','Subhang'),
('2019','paid','108','Kritik'),
('2019','not paid','109','Anurag'),
('2019','paid','110','Ayush'),
('2019','not paid','111','Abhijeet'),
('2019','paid','112','Hussain');
SQL>select * from fee;

4. QUERIES FOR RETRIEVING THE BASIC INFORMATION FROM

THE TABLE

1. List the ids of the room which are full.

SQL>select room_id from room where room_status=’full’;

2. Display the room id of the students who are enrolled for the course CSE.

SQL> select room_id from student where department=’CSE’;

3. Display the employ id of the mess staff who are technicians.

SQL> select emp_id from staff where emp_designation=’technician’;

4. Find the no. of rows in the table visitor.

SQL> select count(*) from visitor;

Page | 16
5. Display the name of the students who stay in the hostel and study management.

SQL> select student_name from student where department=”management”;

6. Display the hostel id of hostel which has annual expense of 2450000.

SQL> select hostel_id from boys_hostel where annual_expenses=’2450000’;

7. Display the monthly average expense of breakfast.

SQL> select monthly_avg_expense from mess where mess_incharge_id=’9321’;

8. List the name of students who have not paid their fees.

SQL> select student_name from fee where fee_status=”paid”;

9. List the room id of rooms which have bed.

SQL> select room_id from furniture where furniture_type=”bed”;

10. List the out time of visitor having id 4861.

SQL> select visitor_time_out from visitor where visitor_id=’4861’;

5. QUERIES FOR PERFORMING DIFFERENT ACTIONS ON DATA

SET

1. Join the lists of rooms and their furniture.

SQL>select room.room_id, room.furniture_id, furniture.furniture_type from room inner join

furniture on room.furniture_id = furniture.furniture_id;

2. Join the lists of Students and the visitors.

SQL>select student.student_id, student.student_name, visitor.cnic from students inner join

visitor on students.student_id = visitor.student_id;

3. Find the average of the salaries of all mess employees.

SQL>select avg(emp_salary) from mess_emplyee;

4. Find the count of mess employees with salaries greater than 30000.

SQL>select count(emp_id) from mess_employee where emp_salary>30000;

Page | 17
5. Display the combined list of rooms with their students.

SQL> select * from students union select * from room;

6. Display the common rows of lists of rooms and students .

SQL>select * from students intersect select * from room;

7. List the name of students who have not paid their fees using view with name as
“notpaid”.

SQL>create view notpaid as select student_name from fee where fee_status=”paid”; select *
from notpaid.

8. List the out time of visitor having id 4861 using view statement.

SQL>create view visitor_4861 as select visitor_time_out from visitor where visitor_id=’4861’;

select * from visitor_4861.

9. List the room capacities with good furniture type.

SQL>select capacity from room where furniture_id in (select furniture id from furniture where
furniture_type=”good”);

10. List the visitor name of the students with age less than 15.

SQl>select visitor_name from visitor where student_id in (select student_id from students
where age<15);

Page | 18