BONAFIDE CERTIFICATE

ONLINE HOSTEL MANAGEMENT SYSTEM

Being submitted to the Islamiah College (Autonomous) Vaniyambadi.

By

D.ABISHEK
(Register Number: 31120U09041)
S.RUBAN
(Register Number: 31120U09065)

For the Partial fulfillment for the award of the degree of

B.C.A (Computer Applications)

Is a bonafide record of work carried out by them under the guidance &
supervision of

…..…………… ...…………………..
(Project Guide) (Head of the Department)
Prof . B. JUNAID AHMED M.Sc., M.Phil., NET. Prof P.Magizhan M.sc, M.Phil.,
Assistant Professor DEPT OF COMPUTER SCIENCE
DEPT OF COMPUTER SCIENCE Islamiah College (Autonomous)
Islamiah College (Autonomous) Vaniyambadi.
Vaniyambadi.

The viva-voce examination of this project work was held

on…………………

EXAMINERS:
1.
2.
 ACKNOWLEDGEMENT

With profound gratitude I thank Almighty GOD for all blessings showered on me for
completing my course and project work successfully in time.

I take this opportunity to express my gratitude to all those who contribution in this
project work. First of all I would like to offer my thanks to the principal
Dr. T. MOHAMMED ILYAS ,M.Com., M.B.A., M.Phil., PhD. for the facilities and
assistance provided by him during the course of my study.

My Sincere Thanks to Prof. MAGIZHAN,M.Sc.,M.Phil.,PGDCA. Head of

The Department of Computer Science, Islamiah College (Autonomous) Vaniyambadi for
sharing the ideas with me and full support.

I owe my sincere and enormous gratitude to my venerated faculty guide

Prof . B. JUNAID AHMED M.Sc., M.Phil., NET. Assistant professor, Department of
Computer Science, Islamiah College (Autonomous) Vaniyambadi, for the unfailing support
and valuable suggestions for successful completion of this project.

I render my thankfulness to all faculties and programmer for their precious help
directly and indirectly to complete my project successfully.

At last but not a least I consider my privilege to express our respect to all guided
inspired and helped me in the completion of the project.

-ABISHEK.D
-RUBAN.S
 ABSTRACT

“ONLINE HOSTEL MANAGEMENT SYSTEM” is software developed for managing

various activities in the hostel. For the past few years the number of educational institutions is

increasing rapidly. Thereby the number of hostels is also increasing for the accommodation

of the students studying in this institution. And hence there is a lot of strain on the person

who are running the hostel and software’s are not usually used in this context. 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 system that will be compatible to the existing system with the

system which is more user friendly and more GUI oriented. We can improve the efficiency of

the system, thus overcome the drawbacks of the existing system.

iv
 DEDICATION

This dissertation is dedicated to my family, who passed on a love of reading and respect of

education. Without their huge support, it would not have been possible. And also to my

lovely friends, your inspiration, encouragement and support in diverse forms would always

be remembered and cherished.

v
 TABLE OF CONTENT

STATEMENT OF AUTHENTICITY .................................................................................................... ii

ABSTRACT........................................................................................................................................... iii

DEDICATION ....................................................................................................................................... iv

ACKNOWLEDGEMENT ...................................................................................................................... v

TABLE OF CONTENT ......................................................................................................................... vi

LIST OF TABLES ................................................................................................................................. ix

LIST OF FIGURES ................................................................................................................................ x

CHAPTER ONE

1.1 INTRODUCTION ............................................................................................................................ 1

1.2 PROJECT OVERVIEW ................................................................................................................... 2

1.3 PROBLEM STATEMENT ............................................................................................................... 2

1.4 OBJECTIVES ................................................................................................................................... 2

1.5RESEARCH QUSTION .................................................................................................................... 3

1.6 LIMITATIONS OF STUDY ............................................................................................................ 3

CHAPTER TWO : LITERATURE REVIEW

2.1 INTRODUCTION ............................................................................................................................ 4

2.2 EXISTING SYSTEM ....................................................................................................................... 4

2.2.1 Disadvantages ............................................................................................................................ 4

2.3 PROPOSED SYSTEM ..................................................................................................................... 5

CHAPTER THREE: FEASIBILITY STUDY

3.1 TECHNICAL FGEASIBLITY ......................................................................................................... 6

vi
3.2 ECONOMIC FEASIBILTY ............................................................................................................. 6

3.3 OPERATIONAL FEASIBILTY ....................................................................................................... 6

3.4 REQUIREMENT ANALYSIS AND SPECIFICATION ................................................................. 6

3.4.1 User Module........................................................................................................................ 7

3.4.2 Change Password Module ................................................................................................... 7

3.4.3 Student Module ................................................................................................................... 7

3.4.4 Room Allotment Module .................................................................................................... 7

3.4.5 Room Fees Module ............................................................................................................. 7

3.4.6 Mess Bill Module ................................................................................................................ 7

3.4.7 Visitors Module................................................................................................................... 7

3.4.8 Report Generation Module.................................................................................................. 8

3.4.9 Settings Module .................................................................................................................. 8

3.5 HARDWARE CONFIGURATION .................................................................................................. 8

3.6 SOFTWARE CONFIGURATION ................................................................................................... 9

CHAPTER FOUR: SYSTEM DESIGN

4.1 INTRODUCTION .......................................................................................................................... 10

4.2 ADMINISTRATOR ....................................................................................................................... 10

4.3 DATA FLOW DIAGRAMS ........................................................................................................... 10

4.4 HMS SOFTWARE ......................................................................................................................... 12

4.4.1 Login ........................................................................................................................................ 13

4.4.2 Administrator Panel ................................................................................................................. 13

4.4.3 Add Student Details and view Student..................................................................................... 14

4.4.4 Room Registration ................................................................................................................... 15

4.4.5 Block and Add Rooms Panel ................................................................................................... 15

4.4.6 Change Password ..................................................................................................................... 17

vii
 4.4.7 Add And View Course ............................................................................................................. 17

4.4.8 Fees Forms, Fee Type And Fee Report.................................................................................... 18

4.4.9 Mess Panel ............................................................................................................................... 20

4.5 DATABASE DESIGN (TABLE STRUCTURES)......................................................................... 21

CHAPTER FIVE: IMPLEMENTATION AND TESTING

5.1 INTRODUCTION .......................................................................................................................... 26

5.2 SYSTEM TESTING ....................................................................................................................... 27

5.2.1 Unit Testing ............................................................................................................................. 27

5.2.2 Integration Testing ................................................................................................................... 27

5.2.3 User Acceptance Testing ......................................................................................................... 28

5.3 SUMMARY .................................................................................................................................... 28

5.4 CONCLUSION ............................................................................................................................... 28

viii
 LIST OF TABLES

Table 1.1 Billing ........................................................................................................21

Table 1.2 Block… ......................................................................................................21

Table 1.3 Block Allotment… .....................................................................................22

Table 1.4 Course ........................................................................................................22

Table 1.5 Employee ...................................................................................................22

Table 1.6 Fees… ........................................................................................................23

Table 1.7 Fee Structure ........................................................................................... 23

Table 1.8 Mess Card… ........................................................................................... 23

Table 1.9 Mess Bill… ................................................................................................24

Table 2.0 Visitor… ....................................................................................................24

Table 2.1 Registration… ............................................................................................24

Table 2.2 Student… ................................................................................................ 26

ix
 LIST OF FIGURES

Figure 1.1 DFD for Administrator Panel… ...............................................................10

Figure 1.2 DFD for Student Module ....................................................................... 11

Figure 1.3 DFD for Student Registration… ...............................................................11

Figure 1.4 DFD for Admin Module ...........................................................................11

Figure 1.5 DFD for Admin Module ...........................................................................12

Figure 1.6 DFD for Allotment Process ......................................................................12

Figure 1.7 Login….....................................................................................................13

Figure 1.8 Administrator Panel… ........................................................................... 13

Figure 1.9 Add Student ..............................................................................................14

Figure 2.1 View Student Details… ............................................................................14

Figure 2.2 Room Registration… ................................................................................15

Figure 2.3 Blocks… ...................................................................................................15

Figure 2.4 Block Selection… .....................................................................................16

Figure 2.5 View Blocks .............................................................................................16

Figure 2.6 Add Rooms ...............................................................................................16

Figure 2.7 Change Password…..................................................................................17

Figure 2.8 Add Course ...............................................................................................17

Figure 2.9 View Course .............................................................................................18

Figure 3.1 Fee Type ...................................................................................................18

Figure 3.2 Fee Form… ...............................................................................................19

Figure 3.3 Fee Report… ............................................................................................20

Figure 3.4 Add Mess Card… .....................................................................................20

Figure 3.5 View Mess Card… ...................................................................................21

x
 CHAPTER ONE

1.1 INTRODUCTION

In our current era of automated systems with it being either software or hardware, it’s not

advisable to be using manual system. Hostels without a management system are usually done

manually. Registration forms verification to other data saving processes are done manually

and most at times, they are written on paper. Thus a lot of repetitions can be avoided with an

automated system. The drawbacks of existing systems lead to the design of a computerised

system that will help reduce a lot of manual inputs. With this system in place, we can

improve the efficiency of the system, thus overcome the drawbacks of the existing manual

system.

This system is designed in favour of the hostel management which helps them to save the

records of the students about their rooms and other things. It helps them from the manual

work from which it is very difficult to find the record of the students and the mess bills of the

students, and the information of about the those ones who had left the hostel years before.

This system gives an idea about how a student and fee details, room allocation, mess

expenditure are maintained in a better way. The hostel management system will also contain

special features like how many students are in a room, student’s id and free rooms or space

available. The administration has a unique identity for each member as well as students

details.

1
1.2 PROJECT OVERVIEW

The hostel management system is web based software to provide college students

accommodation to the university hostel more efficiently. This project also keeps details of the

hostellers and applied students. It is headed by Warden. He will be the administrator.

This document is intended to minimize human works and make hostel allocation an easier job

for students and hostel authorities by providing online application for hostel, automatically

select the students from the waiting list and mess calculation, complaint registration, notice

board etc. etc. Students will get approval notification in their mails. Hostellers can view

notice board, hostel fee and mess menu by login into the online system.

1.3 PROBLEM STATEMENT

There are a lot of drawbacks in keeping and maintaining a hostel. Especially with a manual

system. Since most hostels are being run by only one hostel manager, the number of students

in a room are sometimes not known by the officer. He has to go room by room to ensure that

a room is occupied or not. Sometimes people may be owing in the hostel and they are saved

on papers or huge notebooks, and sometimes receipts. If the books should go missing or

stolen, one would never be able to know if a student is owing or not. Room allocation also

becomes a problem as the officer might not know which rooms are available or not. And

some hostels have a lot of rooms or have mare storeys and it would be very tedious to go

through all storeys in search of a free room for an applicant. Also the officer might not know

the number of students in a room or know if a room is full or not.

1.4 OBJECTIVES

 To make it easier for data collection, storage and referencing reliable.

 To maintain the students as hostellers and waiting list students separately.

 To process allotment list.

2
1.5 RESEARCH QUSTION

Based on the need for effective and efficient system for hostels and some amount of probing

into the matter, the following questions were identified:

• What are the easier forms student collection, storage and referenced by the system?

• How can information of students be collected and stored for future reference?

• How can the system reduce errors as compared to the manual system?

1.6 LIMITATIONS OF STUDY

Time and financial constraints were the major factors that hindered the progress of this

research. The study involved a lot of financial obligations such as the cost of stationary,

printing, photocopying and transportation.

Moreover, combining fieldwork and lectures to produce a comprehensive research report

within the time limit was tiresome. Nevertheless, the quality of this study was not

compromised.

3
 CHAPTER TWO

LITERATURE REVIEW

2.1 INTRODUCTION

In this section we are going to analyse the existing system and provide solutions to errors or

build a new system all together.

2.2 EXISTING SYSTEM

The existing system is manual based and need lot of efforts and consume enough time. In the

existing system we can apply for the hostels online but the allotment processes are done

manually. It may lead to corruptions in the allocation process as well as hostel fee

calculation. The existing system does not deals with mess calculation and complaint

registration.

2.2.1 DISADVANTAGES:

 More human power

 More strength and strain of manual labour needed

 Repetition of same procedure.

 Low security.

 Data redundancy.

 Difficulty to handle.

 Difficulty to update data.

 Record keeping is difficult.

 Backup data can be easily generated.

4
2.3 PROPOSED SYSTEM

This project is aimed at developing a system for keeping records and showing information

about or in a hostel. This system will help the hostel officer to be able to manage the affairs

of the hostel. This system will provide full information about a student in the hostel. It will

show rooms available or not and number of people in a particular room. This will also

provide information on students who have paid in full or are still owing. This system will also

provide a report on the summary detail regarding fees and bills students are owing. Also

included is a user module for employees or the hostel officer. There will also be an

administrator module which will accessed by the administrator and has the ability to delete,

add and edit employee records.

This system will be developed based on Software Development Life Cycle (SDLC) with PHP

and My SQL server. PHP is good for the development and design of web based programs

whiles My SQL is good for databases because of its security and its advanced features and

properties.

5
 CHAPTER THREE

FEASIBILITY STUDY

3.1 TECHNICAL FGEASIBLITY

The technical feasibility in the proposed system deals with the technology used in the system.

It deals with the hardware and software used in the system whether they are of latest

technology or not and if it happens that after a system is prepared, a new technology arises

and the user wants the system based on that technology. This system use windows platform,

apache server, sql for database, php as the language and html or xml as user interface. Thus

HOSTEL MANAGEMENT SYSTEM is technically feasible.

3.2 ECONOMIC FEASIBILTY

Economic analysis is the most frequently used method for evaluating the effectiveness of a

new system. More commonly known as cost/benefit analysis. Php, html, xml and sql database

are easily available on internet.

3.3 OPERATIONAL FEASIBILTY

The project has been developed in such a way that it becomes very easy even for a person

with little computer knowledge to operate it. This software is very user friendly and does not

require any technical person to operate .Thus the project is even operationally feasible.

3.4 REQUIREMENT ANALYSIS AND SPECIFICATION

Functions and features delivered to the end users. The end users of the proposed system are:

6
3.4.1 USER MODULE

This helps the administrator and user to login to homepage only if password and username

matches.

3.4.2 CHANGE PASSWORD MODULE

Allows the user to change the password.

3.4.3 STUDENT MODULE

This module is used to store student details i.e. information like profile details, contact

information, educational details etc. Users can search according different criteria such as

name, course, room number etc.

3.4.4 ROOM ALLOTMENT MODULE

This deals with allocation of room to students according to education details, section or

course. Rooms will be allocated to students and an ID will be generated for it. It will display

details students staying in the room or rooms. When a student leaves the room after the

semester, the left date will be also saved.

3.4.5 ROOM FEES MODULE

This displays fee records, student dues status and balance amount status. It is also used to

renew students rent every semester.

3.4.6 MESS BILL MODULE

This module keeps track of all transactions related to mess. The mess item expenditure for

each student is calculated every month and mess bill for each student is calculated and

displayed.

3.4.7 VISITORS MODULE

This allows the visitor details to view the visitors depending on various search criteria.

7
3.4.8 REPORT GENERATION MODULE

This is provided to view summary detail regarding hostel fees and bills. Students can check

hostel fees and bill details by entering the unique hostel ID.

3.4.9 SETTINGS MODULE

In this module, only the administrator can access. Administrator has a unique account with

much special access and permissions over normal users. Module allows add, edit, delete and

employee records, building block information, room details, course details etc.

3.5 HARDWARE CONFIGURATION

The section of hardware configuration is an important task related to the software

development. Insufficient random access memory may affect adversely on the speed and

efficiency of the entire system. The process should be powerful to handle the entire

operations. The hard disk should have sufficient capacity to store the file and application.

Processor: Pentium IV and above

Processor speed: 1.4 GHz Onwards

System memory: 128 MB minimum (256 MB recommended)

Cache size: 512 KB

RAM: 512 MB (Minimum)

Network card: Any card can provide a 100mbps speed

Network connection: UTP or Coaxial cable connection

Printer: Inkjet/Laser Colour printer provides at least 1000 Dpi

Hard disk: 80 GB

Monitor: SVGA Colour 15”

Mouse: 104 keys US Key Serial, USB or PS/2

8
3.6 SOFTWARE CONFIGURATION

A major element in building a system is the section of compatible software since the software

in the market is experiencing in geometric progression. Selected software should be

acceptable by the firm and one user as well as it should be feasible for the system. This

document gives a detailed description of the software requirement specification. The study of

requirement specification is focused specially on the functioning of the system. It allow the

developer or analyst to understand the system, function to be carried out the performance

level to be obtained and corresponding interfaces to be established.

Technology Implemented: Apache Server

Language Used: PHP 5.3 or newer versions

Database: My SQL 5.5 or newer

User Interface: HTML, AJAX

Web Browser: Mozilla, Chrome or Internet Explorer 8(or newer)

Software: XAMPP or WAMP Server

Operating System: Windows XP or higher versions.

9
 CHAPTER FOUR

SYSTEM DESIGN

4.1 INTRODUCTION

This system design is to be divided into two sections or portion. Administrator section and

student section.

4.2 ADMINISTRATOR

 The Administrator can allot different students to the different hostels.

 He can vacate the students for the hostels.

 He can control the status of the fee payment.

 He can edit the details of the students. He can change their rooms, edit and delete the

student records.

 He can edit the news board

 He can check the complaints

 The Hostel Secretary can :

 Make the Mess menu

 Make the mess bill & hostel bill

4.3 DATA FLOW DIAGRAMS

Figure 1.1 DFD for Allotment Process

10
Figure 1.2 DFD for Student module

Figure 1.3 DFD for Student Registration

Figure 1.4 DFD for Admin Module

11
Figure 1.5 DFD for Admin Module

Figure 1.6 DFD for Allotment Process

4.4 HMS SOFTWARE

The hostel management system software comprises of many sections. Each has its own

functions which to help to manage things like mess bills, student details, employee details

and many others.

12
4.4.1 LOGIN

Figure 1.7 Login Panel

This page consists of the administrator and employee login and visitor or student login. One

has have a username or password to be able to access the site.

4.4.2 ADMINISTRATOR PANEL.

Figure 1.8 Administrator Panel

This is page for the administrator. He has the ability to control who and what goes into the

system. He can add, remove and update information in this system. In this panel is used to

13
register a student, view fees, view rooms, view mess bills, allot students to blocks and rooms,

view courses of students and assign them to special or specific rooms. He can also add new

students to the system.

4.4.3 ADD STUDENT DETAILS AND VIEW STUDENT

Fig 1.9 Add Student

Figure 2.1 View Student Details

This panel allows the administrator to add students to the system. He can collect student
details in order to assign rooms for the student.

14
4.4.4 ROOM REGISTRATION

Figure 2.2 Room Registration

This section deals with allot of rooms to a student. A student details would be already on the

system so it would be at student details section on this page.

4.4.5 BLOCK AND ADD ROOMS PANEL

Figure 2.3 Blocks

15
Figure 2.4 Block Selection

Figure 2.5 View Blocks

Figure 2.6 Add Rooms

These sections help the administrator to select the block in which the available room is and to

add rooms to it. It allows him to create blocks of the actual hostel to save on the database.

16
This also allows him to view blocks created in the database and know the status of the block

if active, available or not.

4.4.6 CHANGE PASSWORD

Figure 2.7 Change Password

This page allows one to change his or her password whether be it administrator, employee or

visitor or student. With every change of password it affects the data on the database thereby

doing a write off every time a password is changed.

4.4.7 ADD AND VIEW COURSE

Figure 2.8 Add Course

17
Figure 2.9 View Course

Add panel allows the user of the system to add courses to student details and view courses

helps one to know the courses of students in the hostel. Also helps to one where to assign

rooms to students.

4.4.8 FEES FORMS, FEE TYPE AND FEE REPORT

Figure 3.1 Fee Type

18
Figure 3.2 Fee Form

19
Figure 3.3 Fee Report

This section is all fees. It shows the fee structure, type of fees to be paid and payment history

of a student. This helps to detect and to know who is owing and who is not. It allows one to

make payment of fees. It also generates fee report of all bills paid by students in da hostel.

4.4.9 MESS PANEL

Figure 3.4 Add Mess Card

20
Figure 3.5 View Mess Card

Mess in the hostel is all about damages done in room or damages incurred whiles living in the

hostel. Hostel manager inspects rooms to get this information and adds it a student’s mess

card. It then adds up to the students total fees to be paid or can be paid separately.

4.5 DATABASE DESIGN (TABLE STRUCTURES)

Bill_id int

Reg_id int

Bill_type varchar

Paid_amt double

Paid_date date

Table 1.1 Billing

Block_id int

Block_name varchar

Gender varchar

Description text

Status varchar

Table 1.2 Blocks

21
 Allotment_id int

Block_id int

Course_id int

Status varchar

Table 1.3 Block Allotment

Course_id int

Course_name varchar

No_of_year int

Status varchar

Table 1.4 Course

Emp_id int

Block_id int

Login_id varchar

Password varchar

Emp_type varchar

Emp_name varchar

Gender varchar

DOB date

DOJ date

Table 1.5 Employee

22
 Fee_id int

Reg_id int

Fee_str_id int

Total_fees double

Status varchar

Table 1.6 Fees

Fee_str_id int

Course_id int

Fee_type varchar

Cost float

Table 1.7 Fees Structure

Messcard_id int

Reg_id int

Messcard_type varchar

Start date date

Enddate date

Status varchar

Table 1.8 Mess Card

23
 Mess_bill_id int

Reg_id int

Fee_str_id int

Date date

Mess_bill double

Status varchar

Table 1.9 Mess Bill

Visitor_id int

Stid int

Name varchar

Type varchar

Username varchar

Password varchar

Contactno varchar

Comments text

Status varchar

Table 2 Visitor

24
 Reg_id int

Stid int

Room_id int

Stud_type varchar

Start_date date

End_date date

Food_type varchar

Beverage_type varchar

Status varchar

Table 2.1 Registration

Stid int

Courseid int

Name varchar

Rollno varchar

DOB date

Father_name varchar

Mother_name varchar

Gender varchar

Contact_no varchar

Parents_no varchar

Blood_group varchar

Status varchar

Table 2.2 Student

25
 CHAPTER FIVE

IMPLEMENTATION AND TESTING

5.1 INTRODUCTION

Implementation is the stage in the project where the theoretical design is turned into a

working system and is giving confidence on the new system for the users that it will work

efficiently and effectively. It involves careful planning, investigation of the current system

and its constraints on implementation, design of methods to achieve the changeover, an

evaluation of change over methods. Apart from planning major task of preparing the

implementation are education and training of users. The implementation process begins with

preparing a plan for the implementation of the system. According to this plan, the activities

are to be carried out, discussions made regarding the equipment and resources and the

additional equipment has to be acquired to implement the new system.

In network backup system no additional resources are needed. Implementation is the final and

the most important phase. The most critical stage in achieving a successful new system is

giving the users confidence that the new system will work and be effective. The system can

be implemented only after thorough testing is done and if it is found to be working according

to the specification. This method also offers the greatest security since the old system can

take over if the errors are found or inability to handle certain type of transactions while using

the new system

26
5.2 SYSTEM TESTING

As the part of system testing we execute the program with the intent of finding errors and

missing operations and also a complete verification to determine whether the objectives are

met and the user requirements are satisfied. The ultimate aim is quality assurance.

Tests are carried out and the results are compared with the expected document. In the case of

erroneous results, debugging is done. Using detailed testing strategies a test plan is carried

out on each module. The various tests performed are unit testing, integration testing and user

acceptance testing.

5.2.1 UNIT TESTING

The software units in the system is are modules and routines that are assembled and

integrated to perform a specific function. As a part of unit testing we executed the program

for individual modules independently. This enables, to detect errors in coding and logic that

are contained within each of the three module. This testing includes entering data that is

filling forms and ascertaining if the value matches to the type and entered into the database.

The various controls are tested to ensure that each performs its action as required.

5.2.2 INTEGRATION TESTING

Data can be lost across any interface, one module can have an adverse effect on another, sub

functions when combined, may not produce the desired major functions. Integration testing is

a systematic testing to discover errors associated within the interface. The objective is to take

unit tested modules and build a program structure. All the modules are combined and tested

as a whole. Here the admin module, employee module and student module options are

integrated and tested.

This testing provides the assurance that the application is well integrated functional unit with

smooth transition of data.

27
5.2.3 USER ACCEPTANCE TESTING

User acceptance of a system is the key factor for the success of any system. The system under

consideration is tested for user acceptance by constantly keep the records of applicants and

making changes to the details and password whenever required.

5.3 SUMMARY

This project is aimed at developing a system for keeping records and showing information

about or in a hostel. This system will help the hostel officer to be able to manage the affairs

of the hostel. This system will provide full information about a student in the hostel. It will

show rooms available or not and number of people in a particular room. This will also

provide information on students who have paid in full or are still owing. This system will also

provide a report on the summary detail regarding fees and bills students are owing. Also

included is a user module for employees or the hostel officer.

5.4 CONCLUSION

To conclude the description about the project, the project, developed using PHP with My

SQL is based on the requirement specification of the user and the analysis of the existing

system, with flexibility for future enhancement.

HOSTEL MANAGEMENT SYSTEM is very useful for hostel allotment and mess fee

calculation. This hostel management software is designed for people who want to manage

various activities in the hostel. For the past few years the numbers of educational institutions

are increasing rapidly. Thereby the numbers of hostels are also increasing for the

accommodation of the students studying in this institution. And hence there is a lot of strain

on the person who are running the hostel and software’s are not usually used in this context.

28
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

system that will be compatible to the existing system with the system which is more user

friendly and more GUI oriented.

29
 REFERENCES

 "Hostel Management System." CodeCanyon, codecanyon.net/item/hostel-management-

system/22491063.

 "Hostel Management System Project in PHP." Phptpoint, www.phptpoint.com/hostel-

management-system-project-in-php/.

 "Online Hostel Management System." GitHub, github.com/billpat-uttam/Online-Hostel-

Management-System.

 "Hostel Management System Project Report." Academia,

www.academia.edu/37790427/Hostel_Management_System_Project_Report.

 "Hostel Management System Using PHP With Source Code." Source Code & Projects,

sourcecodeprojects.com/hostel-management-system-using-php-with-source-code/.

30