A

DISSERTATION

on

Hostel management system

By

Gorav Sariya

SUBMITTED TO

INSTITUTE OF COMPUTER SCIENCE

VIKRAM UNIVERSITY, UJJAIN (M. P.)

in

Partial Fulfilment of the Requirement for the Award of the Degree

Of BCA (hons)

of

VIKRAM UNIVERSITY, UJJAIN

JUNE 2024

GUIDED By

Name of Guide Name of Co-guide

Dr.Kamal Bunkar Dr Geetika Singh

 DECLARATION

I Gorav Sariya of Institute of Computer Science declare that the project report submitted

by me is a bona fide work for the partial fulfilment of the requirement of BCA(Hons)

project work. I have incorporated all the suggestions provided my guide time to time.

I further declare that to the best of my knowledge this project contains my original work

which has been submitted for the award of any degree either in the university or in the

other university/ Deemed University /Institute etc. Without proper citation and I shall be

fully responsible for any plagiarism found at any stage.

Signature of Student
Gorav Sariya
 INSTITUTE OF COMPUTER SCIENCE

VIKRAM UNIVERSITY, UJJAIN(M.P.)

CERTIFICATE

2024

This is to certify that the dissertation title Hostel Management System by Gorav

Sariya is partial fulfilment of the requirement for the award of degree of BCA(Hons)

of Vikram University, Ujjain and is bona fide record of work done by at Institute of

Computer Science Ujjain during March’2024 to June’2024.

Name of Guide Dr. Kamal Bunkar

Dr Kamal Bunkar Director
ICS,Vikram University,Ujjain

Name of Co-guide Dr Geetika Singh

 Table Of Contents

No Title Remark

1. Overview of the Project 1

1.1 Introduction

1.2 Key features

1.3 Goals

1.4 Theoretical Background

1.5 Details of the project

1.6 Advantages

1.7 Disadvantages

2. Environment 12

2.1 Hardware

2.2 Softwares

3 Manual vs Early S/m 14

4. Current system 18

5. SDLC of the project 21

6. Code of the Project 28

7. ER-Diagram and DFD 43

8. Screenshots 51
 Chapter 1

OVERVIEW

1.1 Introduction of the Project

Hostel management system is online project that managing and organizing the operations of

hostels efficiently. These systems play a pivotal role in enhancing the overall experience of

both hostel administrators and residents by automating processes and providing real-time

information. This introduction explores the significance of hostel management projects, their

key features, benefits, and the impact they have on various stakeholders involved.

In today's fast-paced world, the demand for efficient hostel management systems has grown

significantly. These systems offer a centralized platform that simplifies the management of

hostel facilities, including room allocation, fee management, visitor tracking, and maintenance

scheduling. By automating routine tasks, such as registration processes and inventory

management, hostel management systems streamline operations, reduce administrative

burdens, and minimize errors.

In this project we use firstly the registration page. If anyone who has new in the website he/she

firstly registered him on the project and remember the password and the login id that can be

used during the registration page if someone forget their password and don’t save in a password

manager that we can give him a forget password window. In this window person easily recover

their password and login with new password in the project.

We have also the admin window who has total management of the system we firstly give the

encrypted password to the admin therefore his password can be save from the hackers when

the admin fill his name and id on the project he goes to the next targeted window that can be

the main window of the project.

1.2 Key Features of the project

Modern hostel management systems are equipped with a range of features designed to meet

the diverse needs of hostel administrators and residents. Some key features include:

1. Room Allocation and Management: Automated room assignment based on

preferences and availability, along with the ability to manage room transfers and check-

ins efficiently.

2. Fee Management: Automated fee collection, fine calculation, and payment reminders,

ensuring timely and accurate financial transactions.

3. Visitor Management: Logging visitor details, managing permissions, and ensuring

security through controlled access.

4. Inventory Management: Tracking and managing hostel supplies, such as bedding,

toiletries, and kitchen essentials, to ensure adequate stock levels.

5. Communication Tools: Integrated messaging systems for effective communication

between administrators, residents, and parents/guardians.

6. Maintenance Tracking: Scheduling and tracking of maintenance tasks, ensuring

timely repairs and upkeep of hostel facilities.

7. Reports and Analytics: Generating insightful reports on occupancy rates, financial

transactions, maintenance history, and other key metrics to facilitate data-driven

decision-making.

1.3 Goals of the Project

The goals of the project is that it is digital in nature and give us the proper bills of the

payments and also the proper name and number related to the project and also to the other

main window
1.4 Theoretical Background

A Hostel Management System (HMS) is a software application designed to streamline and

automate the management of hostels or dormitories. The theoretical background of an HMS

typically encompasses several key concepts and principles:

1. Database Management: Central to any HMS is the management of a database that

stores information about hostel residents, rooms, room allocations, fees, staff details,

and other relevant data. The theoretical foundation here includes relational database

theory, normalization techniques, and efficient querying methods to ensure data

integrity and retrieval speed.

2. User Interface Design: The design of user interfaces in an HMS is crucial for ease of

use and efficiency. Theoretical aspects include principles of human-computer

interaction (HCI), usability guidelines, and accessibility considerations to ensure that

the system is intuitive and user-friendly for administrators, hostel staff, and residents.

3. System Architecture: The HMS typically operates in a client-server architecture,

where the server manages the database and business logic, while clients (desktop, web,

or mobile) interact with the system. Theoretical aspects include distributed systems

theory, scalability considerations, and network protocols to ensure robust performance

and reliability.

4. Software Engineering Principles: HMS development follows software engineering

principles such as modularity, encapsulation, and separation of concerns. Theoretical

frameworks like object-oriented design patterns, software development life cycle

(SDLC) models, and agile methodologies guide the development process to ensure the

system meets functional and non-functional requirements effectively.

 5. Security: Security is paramount in HMS to protect sensitive information like personal

details of residents and financial transactions. Theoretical underpinnings include

cryptography, access control mechanisms, authentication protocols, and data

encryption techniques to safeguard data against unauthorized access and cyber threats.

6. Data Analytics and Reporting: Hostel administrators often require analytical insights

and comprehensive reports from the HMS. Theoretical foundations include data mining

techniques, statistical analysis methods, and reporting frameworks to derive meaningful

insights from hostel management data.

7. Regulatory Compliance: Depending on the region, hostels must adhere to certain

regulations and standards. Theoretical knowledge includes legal and regulatory

frameworks related to data protection (such as GDPR), financial regulations, and hostel

management guidelines that influence the design and implementation of the HMS.

8. Workflow Automation: The HMS automates various administrative tasks such as

room allocation, fee collection, maintenance requests, and communication with

residents. Theoretical aspects include workflow modeling, business process automation

(BPA), and decision support systems to optimize operational efficiency and reduce

manual intervention.

In summary, the theoretical background of a Hostel Management System spans various

disciplines including database management, user interface design, system architecture,

software engineering, security, data analytics, regulatory compliance, and workflow

automation. These theoretical foundations guide the development of robust, efficient, and

secure systems that cater to the specific needs of hostel management.

1.5 Details of the project

 The customer detail is the main window. The first page on the software is customer in this

page first on the top we use the one big heading for the welcome with this one heading we

use the hotel logo to demonstrate the hotel in a easy way just like the first login page we

use the form on that window that have many entries. Which is again saved in the database

with the table name. When the user give all his detail Then the user is added in the list as

a customer all the fields is necessary in the window. Again we import the message box to

demonstrate the things. Message box throws an error.

Then the user is added in the list as a customer all the fields is necessary in the window.

Again we import the message box to demonstrate the things. Message box throws an error.

When the user not give any fields message box give the message with the box that all the

fields is required in the window.

Then the user is added in the list as a customer all the fields is necessary in the window
again we import the message box to demonstrate the things message box throws an error
when the user not give any fields message box give the message with the box that all the
fields is required in the window.

1.6 Advantages of the project

1. The whole project can make the life of the customer easy because they can book

online rooms from the hostel which is easy from him

2. We use the lots of framework to design the software and this framework has lots

extensions who provide many built in methods to design a good project

3. We use the sql database which is easy to use and setup of the sql database is easy

and very good which can easy to look and save the data in the form of table
 4. A python good language for the web development and easy to use in the projects

5. A plus point of the software is fetch data on the screen is really a tough task for us

but we maintain it in a very easy way

1.7 Disadvantages of the project

1 . Not use the captcha

2. When we see the Fourth window The subtotal of rooms was not

3. 1st login window has no term and conditions

CHAPTER 2
ENVIRONMENT

2.1 Hardware
 Computers: These are essential for running the software that manages the

hostel operations, such as student registration, room allocation, billing, etc.

Computers can range from desktops to laptops, depending on the specific

needs and setup of the hostel.

 Servers: In larger hostels or systems where multiple computers need to

access and store data centrally, servers are used. These can be dedicated

physical servers or cloud-based servers depending on the scale and budget of

the project.

 Networking Equipment: This includes routers, switches, and cables

necessary to connect computers and servers within the hostel network. A

stable and secure network infrastructure is crucial for ensuring smooth

operation of the hostel management system.

 Printers/Scanners: These are used for printing invoices, reports, or any other

documents related to hostel management. Scanners can be used for digitizing

documents like student IDs or forms.

 Biometric Devices: Some hostels may use biometric devices such as

fingerprint scanners for secure access control to hostel rooms or facilities.

 Barcode/RFID Scanners: These can be used for tracking inventory (such as

hostel assets like furniture), as well as for issuing and managing student IDs

or access cards.

 Security Cameras: Surveillance cameras may be installed in common areas

or at entry points for security purposes. These cameras can sometimes be

integrated into the hostel management system for monitoring purposes.

 Uninterruptible Power Supply (UPS): To prevent data loss or system

downtime during power outages, UPS units can be used to provide temporary

power to critical systems.

 Mobile Devices: Tablets or smartphones may be used by hostel staff for

mobile access to the management system, especially for tasks that require

mobility within the hostel premises.

 Access Control Systems: These systems may include electronic locks or

key cards that integrate with the hostel management software to control access

to rooms and facilities.

2.2 Software Requirement

1. VS-code- for better management of the project we use the one famous IDE

that is vs code. In the vs code we easily save the files in the document and

easily run the project. It also offers one live server in which we can easily run

over files and project over the internet.

Note – we needed a vs code 5.1 version for better project management and

better project understanding

2. Python - We need a Python 2.9 and better version of python. It is

downloaded from the official website of the python and used in the project

we can check the installation of python in the command prompt.

3. SQL – The full form of SQL is Structure Query Language it is used to save

the database of our project in different tables we need a SQL shell and SQL

workbench for the management.

4.Fedena, OpenSIS, PowerSchool: SIS software manages student records,

academic information, attendance tracking, grades, and other educational

data. It integrates with the hostel management system to maintain accurate

student profiles and manage hostel-related information.

5. Notepad- Some software systems, including components of a hostel

management system, may require configuration files that specify settings

such as database connections, server parameters, or custom preferences.

Notepad can be used to edit these text-based configuration files.

6.Pillow - Pillow is a popular Python Imaging Library (PIL) fork used for

opening, manipulating, and saving various image file formats. It's widely used

in projects involving image processing due to its simplicity and extensive

functionality. We can download the pillow from the command using pip

install pillow we can use the pillow in our project for better management and

for better resolution of the images.

7.Tkinter- Tkinter is a standard GUI (Graphical User Interface) library for

Python, which provides a fast and easy way to create desktop applications.

For a hostel management project, you can use Tkinter to build a user-friendly

interface that allows administrators to manage rooms, tenants, billing, and

other aspects of hostel management

 Chapter 3

MANUAL SYSTEM VS EARLIER SYSTEM

When evaluating a manual system versus an earlier digital system for hostel management,

several factors come into play, including efficiency, accuracy, data security, and ease of

use. Here’s a comparison of both systems based on these aspects:

Manual System

A manual system relies on physical records and manual processes for managing hostel

operations.

Advantages

1. Low Initial Cost: No need for expensive software or hardware.

2. Simple to Understand: Anyone can understand and use paper records without technical

training.

Disadvantages

1. Time-Consuming: Processes like check-in/check-out, billing, and reporting take longer.

2. Error-Prone: Higher likelihood of human errors in data entry and calculations.

3. Limited Accessibility: Records are only accessible at the physical location where they

are stored.

4. Difficult to Maintain: Paper records can be easily lost, damaged, or misplaced.

5. Lack of Integration: Manual systems cannot easily integrate with other systems (e.g.,

payment gateways, email systems).

6. Inefficiency: Managing a large volume of data manually is inefficient and cumbersome.

Earlier Digital System

An earlier digital system involves basic computer software for managing hostel operations,

which might include simple databases, spreadsheets, or early-generation management

software.
Advantages

1. Increased Efficiency: Faster processing of tasks like check-in/check-out, billing, and

reporting.

2. Reduced Errors: Automated calculations reduce human errors.

3. Improved Data Storage: Digital records are easier to store, search, and retrieve.

4. Enhanced Reporting: Easier generation of reports and analytics.

5. Better Accessibility: Digital records can be accessed from multiple locations if

networked.

Disadvantages

1. Initial Setup Cost: Requires investment in software and possibly hardware.

2. Technical Skills Required: Staff may need training to use the system effectively.

3. Maintenance: Regular maintenance and updates are required to keep the system running

smoothly.

4. Data Security Concerns: Digital data can be vulnerable to hacking, data breaches, and

technical failures if not properly secured.

Comparison

Aspect Manual System Earlier Digital System

Efficiency Low Higher

Accuracy Error-prone Reduced errors

Improved, especially if
Accessibility Limited
networked
Aspect Manual System Earlier Digital System

Data
Difficult Easier
Maintenance

Cost Low initial cost Higher initial setup cost

Training Minimal Technical skills required

Susceptible to physical
Security Susceptible to cyber threats
damage

Reporting Time-consuming Efficient and automated

Scalability Limited Better scalability

Integration None Possible with other systems

Conclusion

The earlier digital system clearly offers several improvements over a manual system in

terms of efficiency, accuracy, and ease of data management. However, it also comes with

its own set of challenges, such as higher initial costs and the need for technical skills. The

choice between a manual and an earlier digital system would depend on the specific needs,

resources, and capabilities of the hostel management.

Moving to a more advanced digital system (like the one you might develop using Tkinter

or web-based solutions) would further enhance these advantages by offering even greater

efficiency, better integration, and enhanced user experience .

Chapter 4

CURRENT SYSTEM
The current systems for hostel management leverage modern technology to provide

comprehensive solutions that streamline operations, improve efficiency, and enhance user

experience. These systems often feature cloud-based platforms, mobile applications, and

advanced data analytics to cater to the diverse needs of hostel management. Below are

some key aspects and features of current hostel management systems:

Key Features of Modern Hostel Management Systems

1. Room and Bed Management

 Real-Time Availability: Track room and bed availability in real-time.

 Booking and Allocation: Efficient room and bed allocation with options for single or

group bookings.

 Check-In/Check-Out: Streamlined processes for check-in and check-out, often with

mobile or self-service options.

2. Tenant Management

 Profile Management: Maintain detailed profiles for each tenant, including personal

information, stay history, and preferences.

 Communication: Built-in messaging systems for communicating with tenants via email

or SMS.

3. Billing and Payments

 Automated Billing: Generate and send invoices automatically.

 Payment Processing: Integrate with payment gateways to handle online payments,

including credit/debit cards and digital wallets.

 Accounting Integration: Integrate with accounting software for financial management.

4. Inventory and Maintenance Management

 Inventory Tracking: Manage inventory of hostel supplies and equipment.

 Maintenance Requests: Log and track maintenance requests, assign tasks to staff, and

monitor completion.

5. Security and Access Control

 Access Management: Use of key cards, biometrics, or mobile apps for secure access to

rooms and common areas.

 Surveillance Integration: Integration with CCTV and other security systems.

6. Reporting and Analytics

 Occupancy Reports: Generate reports on occupancy rates and trends.

 Financial Reports: Detailed financial reports for revenue, expenses, and profitability.

 Custom Analytics: Use analytics to gain insights into operational efficiency and tenant

satisfaction.

7. Mobile Access

 Mobile Apps: Allow staff and tenants to access system features through mobile

applications

Chapter 5

SYSTEM DEVELOPMENT LIFE CYCLE

The System Development Life Cycle (SDLC) for a hostel management

system involves several stages from initial planning through to deployment

and maintenance. In our code we use the software development life cycle for

a better management of project. Here is a detailed outline of each phase in the

SDLC for developing a hostel management system for students:

1. Planning

Objectives:

 Define the scope and objectives of the hostel management system.

 Identify stakeholders and gather initial requirements.

 Conduct feasibility analysis (technical, operational, economic).

Activities:

 Requirement Gathering: Interview stakeholders (administrators, students,

staff) to understand needs.

 Feasibility Study: Assess the viability of the project.

 Project Plan: Develop a project plan including timelines, resources, and

budget.

Deliverables:

 Project Charter

 Feasibility Report

 Initial Project Plan

2. System Analysis

Objectives:

 Define detailed system requirements.

 Develop detailed functional and non-functional requirements.

Activities:

 Requirement Analysis: Create detailed requirement specifications.

 System Models: Develop use case diagrams, data flow diagrams, and

entity-relationship diagrams.

 Validation: Validate requirements with stakeholders.

Deliverables:

 System Requirements Specification (SRS)

 Use Case Diagrams

 Data Flow Diagrams (DFD)

 Entity-Relationship Diagrams (ERD)

3. System Design

Objectives:

 Design the architecture of the system.

 Define the overall system architecture and data architecture.

Activities:

 High-Level Design: Define system architecture, components, modules,

and data flow.

 Low-Level Design: Detailed design of each component, including user

interfaces, database schemas, and API specifications.

 Prototyping: Create prototypes of key components to validate design

choices.

Deliverables:

 High-Level Design (HLD) Document

 Low-Level Design (LLD) Document

 Prototypes

4. Development

Objectives:

 Develop the system based on the design specifications.

 Implement all features and functionalities.

Activities:

 Coding: Write code for each component and module.

 Integration: Integrate various modules to form the complete system.

 Version Control: Use version control systems (e.g., Git) to manage code.
Deliverables:

 Source Code

 Integrated System

5. Testing

Objectives:

 Ensure the system meets the specified requirements.

 Identify and fix bugs and issues.

Activities:

 Unit Testing: Test individual components for functionality.

 Integration Testing: Test the integration of components to ensure they work

together.

 System Testing: Test the entire system for defects and performance issues.

 User Acceptance Testing (UAT): Conduct testing with actual users to

validate the system meets their needs.

Deliverables:

 Test Plans and Test Cases

 Test Reports

 Bug Reports
6. Deployment

Objectives:

 Deploy the system to the production environment.

 Ensure the system is operational and accessible to users.

Activities:

 Deployment Planning: Plan the deployment process, including data

migration and user training.

 Environment Setup: Set up the production environment.

 System Deployment: Deploy the system to the production environment.

 User Training: Train users on how to use the system.

Deliverables:

 Deployment Plan

 Deployed System

 Training Materials

7. Maintenance

Objectives:

 Ensure the system continues to operate smoothly.

 Implement updates and improvements as needed.

 Activities:

 Monitoring: Monitor system performance and user feedback.

 Bug Fixing: Address and fix any issues that arise.

 Updates and Upgrades: Implement system updates and new features.

 Support: Provide ongoing support to users.

Deliverables:

 Maintenance Logs

 Update/Upgrade Reports

 User Support Documentation

Chapter 6

CODE OF THE PROJECT

<?php
session_start();
include('includes/config.php');
date_default_timezone_set('Asia/Kolkata');
include('includes/checklogin.php');
check_login();
$aid=$_SESSION['id'];

if(isset($_POST['submit']))
{
// Posted Values
$acceswardent=$_POST['acceswardent'];
$accesmember=$_POST['accesmember'];
$redproblem=$_POST['redproblem'];
$Room=$_POST['Room'];
$Mess=$_POST['Mess'];
$hstelsor=$_POST['hstelsor'];
$overall=$_POST['overall'];
$feedback=$_POST['feedback'];

// Query for insertion data into database

$query="insert
into feedback(AccessibilityWarden,AccessibilityMember,Redress
alProblem,Room,Mess,HostelSurroundings,OverallRating,FeedbackM
essage,userId) values(?,?,?,?,?,?,?,?,?)";
$stmt = $mysqli->prepare($query);
$rc=$stmt-
>bind_param('ssssssssi',$acceswardent,$accesmember,$redproblem
,$Room,$Mess,$hstelsor,$overall,$feedback,$aid);
$stmt->execute();

echo "<script>alert('Feedback registered

succesfully');</script>";
echo "<script type='text/javascript'> document.location =
'feedback.php'; </script>";
}
?>

<!doctype html>
<html lang="en" class="no-js">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1, minimum-scale=1, maximum-scale=1">
<meta name="description" content="">
<meta name="author" content="">
<meta name="theme-color" content="#3e454c">
<title>Feedback Registration</title>
<link rel="stylesheet" href="css/font-awesome.min.css">
<link rel="stylesheet" href="css/bootstrap.min.css">
<link rel="stylesheet"
href="css/dataTables.bootstrap.min.css">>
<link rel="stylesheet" href="css/bootstrap-social.css">
<link rel="stylesheet" href="css/bootstrap-select.css">
<link rel="stylesheet" href="css/fileinput.min.css">
<link rel="stylesheet" href="css/awesome-bootstrap-
checkbox.css">
<link rel="stylesheet" href="css/style.css">
<script type="text/javascript" src="js/jquery-1.11.3-
jquery.min.js"></script>
<script type="text/javascript"
src="js/validation.min.js"></script>
<script type="text/javascript"
src="http://code.jquery.com/jquery.min.js"></script>

</head>
<body>
<?php include('includes/header.php');?>
<div class="ts-main-content">
<?php include('includes/sidebar.php');?>
<div class="content-wrapper"
<div class="container-fluid">

<div class="row">
<div class="col-md-12"
<h2 class="page-title">Feedback </h2>
<div class="row">
<div class="col-md-12">
<div class="panel panel-primary">
<div class="panel-body">
<?php
$uid=$_SESSION['login'];
$stmt=$mysqli->prepare("SELECT emailid FROM registration WHERE
emailid=? || regno=? ");
$stmt->bind_param('ss',$uid,$uid);
$stmt->execute();
$stmt -> bind_result($email);
$rs=$stmt->fetch();
$stmt->close();
if($rs)
{

$ret=$mysqli->prepare("SELECT id FROM feedback WHERE userId=?

");
$ret->bind_param('i',$aid);
$ret->execute();
$ret->bind_result($count);
$ret->fetch();

if($count>0)
{
$ret="SELECT * FROM feedback WHERE userId=? ";
$stmt= $mysqli->prepare($ret);
$stmt->bind_param('i',$aid);
$stmt->execute() ;
$res=$stmt->get_result();
$cnt=1;
while($row=$res->fetch_object())
{ ?>

<table id="zctb" class="table table-bordered "

cellspacing="0" width="100%" border="1">

<tr>
<td colspan="6" style="text-align:center;
color:blue"><h4>Feedback Details</h4></td>
</tr>
<tr>
<th>Feedback Registration Date</th>
<td><?php echo $row->postinDate;?></td>
</tr>
<tr>
<th>Accessibility to Warden </th>
<td><?php echo $row->AccessibilityWarden;?></td>
</tr>

<tr>
<th>Accessibility to Hostel Committee members </th>
<td><?php echo $row->AccessibilityMember;?></td>
</tr>

<tr>
<th>Redressal of Problem </th>
<td><?php echo $row->RedressalProblem;?></td>
</tr>

<tr>
<th>Room </th>
<td><?php echo $row->Room;?></td>
</tr>

<tr>
<th>Mess </th>
<td><?php echo $row->Mess;?></td>
</tr>

<tr>
<th>Hostel Surroundings (eg Lawn etc.) </th>
<td><?php echo $row->HostelSurroundings;?></td>
</tr>

<tr>
<th>Overall Rating </th>
<td><?php echo $row->OverallRating;?></td>
</tr>

<tr>
<th>Feedback Message</th>
<td><?php echo $row->FeedbackMessage;?></td>
</tr>

</table>

<?php }
} else {
?>
<form method="post" action="" name="complaint" class="form-
horizontal" enctype="multipart/form-data">

<div class="form-group">
<label class="col-sm-4 control-label">Accessibility to Warden
</label>
<div class="col-sm-8">
<input type="radio" name="acceswardent" value="Excellent"
required>Excellent
<input type="radio" name="acceswardent" value="Very Good"
required>Very Good
<input type="radio" name="acceswardent" value="Good"
required>Good
<input type="radio" name="acceswardent" value="Average"
required>Average
<input type="radio" name="acceswardent" value="Below Average"
required>Below Average
</div>
</div>
<div class="form-group">
<label class="col-sm-4 control-label">Accessibility to Hostel
Committee members</label>
<div class="col-sm-8">
<input type="radio" name="accesmember" value="Excellent"
required>Excellent
<input type="radio" name="accesmember" value="Very Good"
required>Very Good
<input type="radio" name="accesmember" value="Good"
required>Good
<input type="radio" name="accesmember" value="Average"
required>Average
<input type="radio" name="accesmember" value="Below Average"
required>Below Average
</div>
</div>
<div class="form-group">
<label class="col-sm-4 control-label">Redressal of
Problems</label>
<div class="col-sm-8">
<input type="radio" name="redproblem" value="Excellent"
required>Excellent
<input type="radio" name="redproblem" value="Very Good"
required>Very Good
<input type="radio" name="redproblem" value="Good"
required>Good
<input type="radio" name="redproblem" value="Average"
required>Average
<input type="radio" name="redproblem" value="Below Average"
required>Below Average
</div>
</div>
<div class="form-group">
<label class="col-sm-4 control-label">Room</label>
<div class="col-sm-8">
<input type="radio" name="Room" value="Excellent"
required>Excellent
<input type="radio" name="Room" value="Very Good" required>Very
Good
<input type="radio" name="Room" value="Good" required>Good
<input type="radio" name="Room" value="Average"
required>Average
<input type="radio" name="Room" value="Below Average"
required>Below Average
</div>
</div>
<div class="form-group">
<label class="col-sm-4 control-label">Mess</label>
<div class="col-sm-8">
<input type="radio" name="Mess" value="Excellent"
required>Excellent
<input type="radio" name="Mess" value="Very Good" required>Very
Good
<input type="radio" name="Mess" value="Good" required>Good
<input type="radio" name="Mess" value="Average"
required>Average
<input type="radio" name="Mess" value="Below Average"
required>Below Average
</div>
</div>
<div class="form-group">
<label class="col-sm-4 control-label">Hostel Surroundings (eg
Lawn etc.) </label>
<div class="col-sm-8">
<input type="radio" name="hstelsor" value="Excellent"
required>Excellent
<input type="radio" name="hstelsor" value="Very Good"
required>Very Good
<input type="radio" name="hstelsor" value="Good" required>Good
<input type="radio" name="hstelsor" value="Average"
required>Average
<input type="radio" name="hstelsor" value="Below Average"
required>Below Average
</div>
</div>
<div class="form-group">
<label class="col-sm-4 control-label">Overall Rating</label>
<div class="col-sm-8">
<input type="radio" name="overall" value="Excellent"
required>Excellent
<input type="radio" name="overall" value="Very Good"
required>Very Good
<input type="radio" name="overall" value="Good" required>Good
<input type="radio" name="overall" value="Average"
required>Average
<input type="radio" name="overall" value="Below Average"
required>Below Average
</div>
</div>
<div class="form-group">
<label class="col-sm-4 control-label">Feedback Message (if
any)</label>
<div class="col-sm-8">
<textarea name="feedback" id="feedback" class="form-
control"></textarea>
</div>
</div>
<div class="col-sm-6 col-sm-offset-4">
<input type="submit" name="submit" Value="Submit" class="btn
btn-primary">
</div>
</form>
<?php }} else {?>
div>You are not eligible for Feedback. Once you book the hostel,
you will be eligible for feedback.</div>
<?php
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
 </div>
<script src="js/jquery.min.js"></script>
<script src="js/bootstrap-select.min.js"></script>
<script src="js/bootstrap.min.js"></script>
<script src="js/jquery.dataTables.min.js"></script>
<script src="js/dataTables.bootstrap.min.js"></script>
<script src="js/Chart.min.js"></script>
<script src="js/fileinput.js"></script>
<script src="js/chartData.js"></script>
<script src="js/main.js"></script>
</body>
</html>

<?php
session_start();
include('includes/config.php');
include('includes/checklogin.php');
check_login();
?>
<!doctype html>
<html lang="en" class="no-js">

<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-
scale=1, minimum-scale=1, maximum-scale=1">
<meta name="description" content="">
<meta name="author" content="">
<meta name="theme-color" content="#3e454c">
<title>Complaint Details</title>
<link rel="stylesheet" href="css/font-awesome.min.css">
<link rel="stylesheet" href="css/bootstrap.min.css">
<link rel="stylesheet" href="css/dataTables.bootstrap.min.css">
link rel="stylesheet" href="css/bootstrap-social.css">
<link rel="stylesheet" href="css/bootstrap-select.css">
<link rel="stylesheet" href="css/fileinput.min.css">
<link rel="stylesheet" href="css/awesome-bootstrap-
checkbox.css">
<link rel="stylesheet" href="css/style.css">
<link rel="stylesheet" href="css/font-awesome.min.css">

<script language="javascript" type="text/javascript">

var popUpWin=0;
function popUpWindow(URLStr, left, top, width, height)
{
if(popUpWin)
{
if(!popUpWin.closed) popUpWin.close();
}
popUpWin = open(URLStr,'popUpWin',
'toolbar=no,location=no,directories=no,status=no,menubar=no,sc
rollbars=yes,resizable=no,copyhistory=yes,width='+510+',height
='+430+',left='+left+',
top='+top+',screenX='+left+',screenY='+top+'');
}

</script>

</head>

<body>
<?php include('includes/header.php');?>

<div class="ts-main-content">
<?php include('includes/sidebar.php');?>
<div class="content-wrapper">
 <div class="container-fluid">
<div class="row" id="print">

<?php
$aid=$_SESSION['id'];
$cid=$_GET['cid'];
$ret="select * from complaints where (id=? and userId=?)";
$stmt= $mysqli->prepare($ret) ;
$stmt->bind_param('is',$cid,$aid);
$stmt->execute() ;
$res=$stmt->get_result();
$cnt=1;
while($row=$res->fetch_object())
{
?><div class="col-md-12">
<h2 class="page-title" style="margin-top:3%">#<?php echo
$row>ComplainNumber;?> Details</ <div class="panel panel-
default <div class="panel-heading">#<?php echo $row-
>ComplainNumber;?> Details</div>
<div class="panel-bo<table id="zctb" class="table table-
bordered " cellspacing="0" width="100%" border="1">

<span style="float:left" ><i class="fa fa-print fa-2x" aria-

hidden="true"OnClick="CallPrint(this.value)"
style="cursor:pointer"title="Printthe
Report"></i></span> <tbody>

<tr>
<tdcolspan="6"style="text-align:center;
color:blue"><h4>Complaint Realted Info</h4></td>
</tr>
<tr>
<th>Complaint Number </th>
<td><?php echo $row->ComplainNumber;?></td>
<th>RegistrationDate</th>
<td><?php echo $row->registrationDate;?></td>
</tr>

<tr>
<th>Complaint Type </th>
<td><?php echo $row->complaintType;?></td>
<th>File (if any)</th>
<td><?php $cdoc=$row->complaintDoc;
if($cdoc==''):
echo "NA";
else: ?>
<a href="comnplaintdoc/<?php echo $cdoc;?>"
target="blank">File</a>

<?php endif;
?></td>

</tr>

<tr>
<th>Complaint Details</th>
<td colspan="3"><?php echo $row->complaintDetails;?></td>

</tr>

<tr>
<th>Complaint Status </th>
<td colspan="3"><?php $cstatus=$row->complaintStatus;
if($cstatus==''):
 echo "New";
else:
echo $cstatus;
endif;

?></td>
</tr>

<?php
$cnt=$cnt+1;
} ?>
</tbody>
</table>
<?php $query="select * from complainthistory where
(complaintid=?)";
$stmt1= $mysqli->prepare($query) ;
$stmt1->bind_param('i',$cid);
$stmt1->execute() ;
$res1=$stmt1->get_result();

?>
<table id="zctb" class="table table-bordered " cellspacing="0"
width="100%" border="1">

<tr>
<th colspan="3" style="color:blue; font-size:18px; text-
align:center">Complaint History</th>
</tr>
<tr>
<th>Complaint Remark</th>
<th>Complaint Status</th>
<th>Posting Date</th>
</tr>
<?php
while($row1=$res1->fetch_object())
{ ?>
<tr>

<td><?php echo $row1->complaintRemark;?></td>

<td><?php echo $row1->compalintStatus;?></td>
<td><?php echo $row1->postingDate;?></td>
</tr>
<?php } ?>
</table>

</div>
</div>
</div>
</div>
</div>
</div>
</div>

<!-- Loading Scripts -->

<script src="js/jquery.min.js"></script>
<script src="js/bootstrap-select.min.js"></script>
<script src="js/bootstrap.min.js"></script>
<script src="js/jquery.dataTables.min.js"></script>
<script src="js/dataTables.bootstrap.min.js"></script>
<script src="js/Chart.min.js"></script>
<script src="js/fileinput.js"></script>
<script src="js/chartData.js"></script>
<script src="js/main.js"></script>
<script>
$(function () {
$("[data-toggle=tooltip]").tooltip();
 });
function CallPrint(strid) {
var prtContent = document.getElementById("print");
var WinPrint = window.open('', '',
'left=0,top=0,width=800,height=900,toolbar=0,scrollbars=0,stat
us=0');
WinPrint.document.write(prtContent.innerHTML);
WinPrint.document.close();
WinPrint.focus();
WinPrint.print();
}
</script>
</body>

</html>
 Chapter 7
ER DIAGRAMS AND DATA FLOW DIAGRAMS

1.First page of ER Diagram(Registration)

START

ENTER ALL
FIELDS

IF ANY
FIELD
NULL

ERROR
RIGHT

SUCCESS

2 Page of ER-Diagram(Login)

START
 ENTER NAME
AND PWD
FIELDS

IF
NULL

ERROR
RIGHT

SUCCESS

3RD Page of ER-Diagram

 START

ENTER NAME
AND PWD
FIELDS

IF
FALSE

ERROR FORGET
THAT

LOGIN WITH NEW PWD

4th ER-Diagram(add the customer)

 START

ENTER ALL
FIELD

IF
NULL

ERROR
IF RIGHT

CUSTOMER ADD

1ST DATA FLOW DIAGRAMS

FIRST WINDOW
 LOGIN
REGISTRATION
FORGET

REGISTER
LOGIN

RESET

2ND DATA FLOW DIAGRAM

 CUST WINDOW ROOM

BOOK
ROOM LOGOUT
DETAILS
ACCESS

UPDATE
ADD RESET DEL

Chapter 8
SCREENSHOTS OF THE PROJECT