Prepared by :-

1. Mohammed Ishan
2. Anita Bepari

Under the Guidance of :-

Ms. Sipra Singh
(Guide)
 The existing hostel management system is being
used:
 to store the hosteller’s details like name, branch
etc.
 to calculate and generate daily and monthly mess
bill and its relevant transactions.
 It also stores the details related to voucher and
stipend.
 The existing system:
 Need to be converted from a standalone application to a simple
client server system( According to clients requirement)
 Labels are not properly defined
 Fields need to be added.
 Does not include modules for stock, accounts, room allocation,
attendance and hostel leaving details
 Existing Modules are not divided properly.
 Does not store the details of no dues clearance and refunding of
caution fee.
 Does not have the provision of adding new item to the present list
of items
 It is a new approach of the earlier developed Hostel Management
System .

 Could be used to maintain the Hostel student’s related information

along with mess bills information, stipend details of the students,
account details, stock information of the hostel materials and
maintaining MAN DAYS record for each of the student etc.

 Will have all the features which are missing in the existing
system.
 All the details related to a hosteller could be find in one place like
the admission details, fees details, room details , attendance ,mess
details, stipend details etc.
 Will make the monitoring of student moment and stock details
easy.
 The same application could be used by both the account section
and the hostel management for their specific needs and
purposes.
 Software Interfaces
The software will be developed in PHP as front-end
using Dream weaver software along with the
database PHPMyAdmin as back-end.
 Operating system: Windows XP (any of versions of
Microsoft Windows)
 Applications: iExplorer (6.0 or above), PHPMyAdmin,
Dreamweaver(Adobe/Macromedia), Apache Triad
The http communication standard will be used.
 The document explains all the functionality,
different actions by users, input and output
covered in detail. Also includes all the software
and hardware requirement, assumptions and
dependencies. Different interfaces external or
internal required to operate the application. Also
include project goal and performance definition
with safety measures. SRS
 Option of adding a limited user (for students) so
that they can view there particular mess bills.