Happy To HRLP

AURO UNIVERSITY, SURAT.
A
PROJECT REPORT
ON
H2H (HAPPY 2 HELP)
GUJARAT JHM HOTELS LTD.

PROJECT REPORT SUBMITTED IN THE
PARTIAL FULFILLMENT FOR THE
DEGREE OF
BACHELOR OF SCIENCE
IN
INFORMATION TECHNOLOGY
SUBMITTED
BY
ALVIN BHAMANI (212015002)
TEAM MEMBERS: SUBMITTED TO:
HARSHIL VANANI (212015024) Dr. SHARAD RAGHUVANSH
MRUGESH GANDHI (212015021)
MAYANK AMIN (212015004)
BATCH 2015 –‘18
AURO UNIVERSITY
SURAT
ACADEMIC YEAR – 2018-‘19
BSc. IT SEMESTER VI PROJECT REPORT

AURO UNIVERSITY, SURAT. 2
A
PROJECT REPORT
ON
H2H (HAPPY 2 HELP)

DEGREE OF
BACHELOR OF SCIENCE
IN
SUBMITTED
BY
HARSHIL VANANI (212015014)
MRUGESH GANDHI (212015021) Dr. SHARAD RAGHUVANSH
BATCH 2015 –‘18
AURO UNIVERSITY
SURAT

A
PROJECT REPORT
ON
H2H (HAPPY 2 HELP)

DEGREE OF
BACHELOR OF SCIENCE
IN
SUBMITTED
BY
MAYANK AMIN (212015004) Dr. SHARAD RAGHUVANSH
BATCH 2015 –‘18
AURO UNIVERSITY
SURAT

A
PROJECT REPORT
ON
H2H (HAPPY 2 HELP)

DEGREE OF
BACHELOR OF SCIENCE
IN
SUBMITTED
BY
ALVIN BHAMANI (212015002) Dr. SHARAD RAGHUVANSH
BATCH 2015 –‘18
AURO UNIVERSITY
SURAT

CERTIFICATE OF UNDERTAKING
I, Harshil Vanani hereby declare that project entitled H 2 H

( H a p p y 2 H e l p ) Undertaken at School of Information
T echnology by Harshil Vanani (212015014) in the partial
fulfillment of B.Sc.IT degree. Semester Examination, is my
original work and the Project has nor formed the basis for the
award of any o t h e r degree, associate ship, fellowship or
any other similar titles, either in AURO University or any
other University of India.
HARSHIL VANANI
(212015014)

SCHOOL OF INFORMATION TECHNOLOGY

CERTIFICATE
This is to certify that the project entitled H2H (Happy 2 Help) has
been carried out by the student under my guidance in the partial
fulfilment of the Degree of Bachelor of Science in Information
Technology of AURO University, Surat during the academic year 2018-
‘19 (Semester-VI).
Team Members:
1. Avin Bhamani
2. Harshil Vanani
3. Mrugesh Ganghi
4. Mayank Amin
Date: 8th May, 2018
Place: Surat
(Dr. Sharad Raghuvansh)

Supervisor Head, School of IT

ACKNOWLEDGEMENTS
This project consumed huge amount of work, research and dedication.

Still, implementation would not have been possible if we did not have a
support of many individuals and organization. Therefore, we would like
to extend our sincere gratitude to all of them.
We take this opportunity to express a deep sense of gratitude to The Taj
Gateway, Courtyard By Marriot and AURO University for their cordial
support, valuable information and guidance, which helped us in
completing this task through various stages.
We take this opportunity to express our profound gratitude and deep
regards to our mentor Mr. Rajiv Katare for his exemplary guidance,
monitoring and constant encouragement throughout the course of this
project. The blessing, help and guidance given by him time to time shall
carry us a long way in the journey of life on which we are about to
embark.
We thank our leader Mr. Suraj Bhan for providing us with this amazing
live project which helped us learning the various aspects in actual
industry and it has also given us valuable insights which will help us in
our future. I hope we have fulfilled all the requirements as specified by
them and provided them with software which will help them to ease their
day-to-day operations.
We are obliged to all members of The Taj Gateway and Courtyard By
Marriot, for the valuable information provided by them in their respective
fields. We are grateful for their cooperation during the period of our
project.
Lastly, we thank almighty, our parents, brothers, sisters and friends for
their constant encouragement without which this project would not be
possible.

CONTENTS
Sr. No. Particulars Page No.
1. Introduction of Project 1
2. Requirement Specifications:
2.1 Business Requirement Specifications 2–5
2.2 System Requirement Specifications
3. Objective of the Software 6
4. Software Model 7
5. System Design:
5.1 Flow Chart 8 – 26
5.2 Data Flow Diagram
5.3 Entity–Relationship Diagram
6. Design:
6.1 Front-End Screenshots 27 – 57
6.2 List of Database Tables
6.3 Back-End Screenshots
7. Source Code 58 – 96
8. Testing and Implementation 97 – 106
9. Limitations and Future Enhancements 107
10. Conclusion 108
11. Bibliography 109
12. Learning Outcomes 110 – 111

INTRODUCTION OF PROJECT
Our software H2H i.e. Happy 2 Help is communication software mainly

for hospitality industry which helps in fulfilling the guest requests and
which also facilitates inter-department communication which is must for
any industry.
As we also know, that communication is necessary and vital source for
smooth functioning of hotel and even for smooth transition of work
within and between the departments.
Our software is segmented into two main parts:
- AYS (At Your Service)
- IDC (Inter-Department Communication).
AYS is guest request handling system which is operated by an operator
who will send request to the particular department by feeding in the
required details. Then the concerned department will get notification on
android device then handle the request and update status of the same.
IDC will help in communication between departments where a
department having any query can fill a query from and send it to
concerned department and that department will handle the query and
update the status of the same accordingly
So, through this software we have tried to fulfil all the requirements
specified by our client and we have done our best to give them with user
friendly software which will not only ease their day-to-day operations, it
will also help them in generating meaningful and understandable reports
according to their and higher authorities requirements.
The scope of this report is to provide a brief, although hopefully useful,
guide to architectural documentation.

REQUIREMENT SPECIFICATIONS
2.1 BUSINESS REQUIREMENT SPECIFICATION (BRS)

A hotel is an establishment that provides lodging paid on a short-term
basis. Facilities provided by hotel are being provided by the departments
working in the hotel. These all departments are connected internally. So,
these departments are:-
1) Front Office
2) Housekeeping
3) Food and Beverages (I) Production
(II) Service
4) Sales and Marketing
5) Engineering
6) IT
7) Security
8) HR
9) Finance
10) Purchases and Stores
11) Spa and Gym
1) FRONT OFFICE
- All the reservations, check-in, check-out procedures and
customer/guest details are feed in FIDELIO (PMS software) at
front office.
- Front office is connected with housekeeping, food and beverages
(service), engineering, IT, security, HR, finance, purchases and
stores, spa and gym and travel desk (part of front office).
2) HOUSEKEEPING
- Housekeeping helps in cleaning the hotel and also takes care of
laundry of guest and staff.
- Housekeeping is connected with front office (AYS also), food and
beverages (service), engineering, HR, IT, security and purchases
and stores.

3) FOOD AND BEVERAGES

(I) PRODUCTION
- The production department of food and beverages produces all the
edible items for guest and staff.
- Production is connected with food and beverages (service),
engineering, HR and purchases and stores.
(II) SERVICE
- The service department of food and beverages provides all the
services to guest in restaurant and they are the one who are
presented in front of guest.
- Service is connected with food and beverages (production),
housekeeping, front office, engineering, HR, IT and security.
4) SALES AND MARKETING

- Sales and marketing people do all the promotions and are
responsible for bringing in guest and do promotional in-house
events.
- Sales and marketing is connected with engineering, finance, HR
and spa and gym.
5) ENGINEERING
- Engineering department maintains all the electrical equipments,
plants and machinery in hotel.
- Engineering is connected with front office (AYS also),
housekeeping, food and beverages (production and service), sales
and marketing, IT, HR, security, finance, purchases and stores and
spa and gym.
6) IT
- IT department is responsible for all the hardware and software
installation, updation and maintenance. They have all the admin
rights of all the software.
- IT is connected with front office (AYS also), housekeeping, food
and beverages (service), HR, security, finance and purchases and
stores.

7) SECURITY
- Security is done in three-tier i.e. at entry level, check-in and
luggage. They also keep an eye on people whom they find
suspicious.
- Security is connected with front office (AYS also), housekeeping,
food and beverages (service), engineering, HR and IT.
8) HR
- HR handles recruitment of all the departments and also manages
payroll management.
- HR is connected with front office, housekeeping, food and
beverages (production and service), sales and marketing,
engineering, IT, security and finance.
9) FINANCE
- Finance handles all the monetary transactions. It handles all the
income and expenditure of the hotel.
- Finance is connected with front office, sales and marketing,
engineering, IT, HR and purchases and stores.
10) PURCHASES AND STORES

- Purchases and stores buy all the requirements which department
needs and gives them.
- Purchases and stores is connected with front office, housekeeping,
food and beverages (production), engineering, IT and finance.
11) SPA AND GYM

- Spa and gym provides the beautification and fitness facilities to
guest.
- Spa and gym is connected with front office, engineering and sales
and marketing.

2.2 SYSTEM REQUIREMENT SPECIFICATION (SRS)
FINDINGS
- Traditional File System (Manual entries)
- Time Consuming
- Data Redundancy
- Ineffective Storage
- Complexity in Accessing Information
- Challenge in Report Generation
- Communication Gap among Departments
SOLUTIONS
- Facilitates automation in day-to-day operations.
- Ease in communication with departments.
- Technology leads to reduce in time consumption.
- Generating meaningful and understandable reports for Hotel
Management.
- Information required can be found easily.

OBJECTIVE OF SOFTWARE
The main objective of this document is to illustrate the requirements of

the project H2H. The document gives detailed description of both
functional and non-functional requirements proposed by client.
The purpose of this project is to provide friendly environment and also to
see to it that the communication is being done properly and all complains
are handled on time and departments operations are performed smoothly.
The main purpose of this project is to maintain easy communication and
request handling system using computers and to provide different reports
for evaluation.
This can be achieved as technology has come into the picture and it will
not only lead to faster handling of requests but, also in effective and
efficient request handling with minimal time consumption.
As now all the data will be stored at one place so authorities will able to
get the required data easily and will also able to use the data as per their
requirements.
Authorities can also generate meaningful and understandable reports as
per their requirements. They can filter the data of reports according to
specifications and even for the purpose of evaluation. They will be
provided by daily reports of completed requests for their daily meetings
to give them the insights that guest requests are handled properly.
The idea of this software is to minimalize the communication gap
between departments by providing them with the inter-department
communication system where any department can send their query to
concerned department and solve their queries.
We have tried to overcome all the challenges they were facing since years
by providing them with the best possible solutions and user friendly
software which will ease out their daily operations.
So, through this project report we are trying to give you the insight of the
whole software by providing the system designs, designs and software
architecture of the software.

SOFTWARE MODEL
AGILE MODEL
- Firstly, we gathered new system requirements from product owner
and define the requirements in User story.
- Then created a quick preliminary design and worked upon it.
- Built a prototype for new system, constructed from preliminary

design and tried to make it as per client’s requirements.
- The clients evaluate the first prototype provided by us, while

evaluation strengths, weaknesses, additions and subtractions are
noted. The developer analyses and collects remarks from clients.
- Initial prototype is modified based on evaluation done by clients

and then the new prototype is designed.
- Again prototype is designed and evaluated and given for evaluation

to clients.
- So, till the final product is not achieved the same steps are repeated
- After the product is achieved it is tested and implemented in the

industry.

SYSTEM DESIGN
5.1 FLOW CHART

DESCRIPTION
STEP 1: START
STEP 2: Admin Login.
STEP 3: Admin Dashboard.
STEP 4: Admin will register property.
STEP 5: Property Registration Condition.
If yes, then he can register rooms and department.
Else, he will go back to property registration.
STEP 6: Department Registration Condition.
If yes, then he can register associates, frequent requests and
locations
Else, he will go back to department registration.
STEP 7: Login of Operator, Manager, Associate,General Manager and
Management.
Login Condition
a. If login data matches with the operator, operator panel will
be opened.
b. Else if login data matches with the manager, manager panel
will be opened.
c. Else if login data matches with the associate, associate panel
will be opened.
d. Else if login data matches with the general manager, general
manager panel will be opened.
e.Else if login data matches with the management, management
panel will be opened.

d. Else no data matches, Invalid user.

Condition- (a) If Operator (AYS) details are matched.
STEP 8: Operator Dashboard.
STEP 9: Request Form.(Manager of the particular department is notified)
STEP 10: Request Logs (New, Work in progress, Pending,Escalated)
STEP 11: Assign Request.(Associate of the particular department is
notified)
STEP 12: Updates Request Status.
STEP 13: Request Reports with different filters.
STEP 14: END
IDC
STEP 9: Query Form.
STEP 10: Assign Query.
STEP 11: Query Log.
STEP 12: Query Report with different filters.
STEP 13: END
Condition- (b) Else if Manager details are matched.
STEP 8: Manager Dashboard.
AYS
STEP 9: Request Log.
STEP 10: Assign Request.(Associate of the particular department is
notified)
STEP 11: Updates Request Status.
STEP 12: Request Report of particular department with different filters.
STEP 13: END
IDC
STEP 9: Query Form.

STEP 10: Query Log.

STEP 11: Assign Query.(Associate of the particular department is
notified)
STEP 12: Update Query Status.
STEP 13: Query Report of particular department with different filters.
STEP 14: END
Condition- (c) Else if Associate details are matched.
STEP 8: Associate Dashboard.
AYS
STEP 9: Request Log
STEP 10: Update Request Status.
STEP 12: END
IDC
STEP 9: Query Form.
STEP 10: Query Log.
STEP 11: Update Query Status.
STEP 13: END
Condition- (d) Else if General Manager details are matched.
STEP 8: General Manager Dashboard.
AYS
STEP 9: View Request Log
STEP 12: END
IDC
STEP 9: Query Form.

STEP 10: View Query Log.

STEP 12: END
Condition- (e) Else if Management details are matched.
STEP 8: Management Dashboard.
STEP 9: Select Property
AYS
STEP 10: Query Form.
STEP 11: View Request Log
STEP 13: END
IDC
STEP 10: View Query Log.
STEP 12: END


5.2 DATA FLOW DIAGRAM (DFD)

0-LEVEL
DESCRIPTION
The four main entities in our software i.e. AYS & IDC are:
- ADMIN
- OPERATOR
- MANAGER
- ASSOCIATE
- GENERAL MANAGER
- MANAGEMENT
So, in 1-level DFD we elaborate all the entities through processes, input
flow and output flow.

1-LEVEL
DESCRIPTION
Processes:
PROCESS 1.0 ADMIN LOGIN –
Admin enters username and password, verifies through TBL_ADMIN.
PROCESS 2.0 PROPERTY REGISTRATION–
Admin can register a new property here, the details are saved to
TBL_PROPERTY.
PROCESS 3.0 ROOM REGISTRATION –
Admin can register a new room here, the details are saved to
TBL_ROOM.
PROCESS 4.0 DEPARTMENT REGISTRATION –
Admin can register a new department here, the details are saved to
TBL_DEPARTMENT.
PROCESS 5.0 LOCATION REGISTRATION –
Admin can register a new location here, the details are saved to
TBL_LOCATION
PROCESS 6.0 ASSOCIATE REGISTRATION –
Admin can register a new associate here, the details are saved to
TBL_USER.
PROCESS 7.0 FREQUENT REQUEST REGISTRATION –
Admin can register a new frequently used request here, the details are
saved to TBL_FREQUENT_REQUEST.
PROCESS 8.0 LOGIN –
Users enters username and password, verifies through TBL_USER.
AYS:
PROCESS 9.0 REQUEST REGISTRATION –
Operator feeds in the details of the request from the guests and associates
and saves details in TBL_REQUEST_AYS. After saving, manager of the
concerned department is notified.

PROCESS 10.0 MANAGE REQUEST –

Users can assign the request and update the current status over here and
saves details in TBL_REQUEST_AYS. After assigning the request,
associates of the concerned department are notified.
PROCESS 11.0 REQUEST REPORTS GENERATION –

Users can view and extract reports from TBL_REQUEST_AYS.
IDC:
PROCESS 12.0 QUERY REGISTRATION –
Users can feeds in the details of the query in order to communicate with
other departments and saves details in TBL_REQUEST_IDC. After
saving, manager of the concerned department is notified.
PROCESS 13.0 MANAGE QUERY –
Users can assign the query and update the current status over here and
saves details in TBL_REQUEST_IDC. After assigning the query,
associates of the concerned department are notified.
PROCESS 14.0 QUERY REPORTS GENERATION –
Users can view and extract reports from TBL_REQUEST_IDC.
PROCESS 15.0 CHANGE PASSWORD –
Users can change password and saves details in TBL_USER.


2-LEVEL OF PROPERTY REGISTRATION (PROCESS 2.0)

DESCRIPTION
PROCESS 2.1 ADD –
Admin adds details of those property who are going to use this software
and saves the details in TBL_PROPERTY .
PROCESS 2.2 EDIT –
Admin can edit the details of property with enabling the disabled property
and saves the details in TBL_PROPERTY.
PROCESS 2.3 DISABLE–
Admin can disable the property under certain circumstances and saves
the details in TBL_PROPERTY
2-LEVEL OF ROOM REGISTRATION (PROCESS 3.0)

DESCRIPTION
PROCESS 3.1 ADD –
Admin adds details of those rooms of those property using this software
and saves the details in TBL_ROOM .
PROCESS 3.2 EDIT–
Admin can edit the details of rooms with enabling the disabled rooms and
saves the details in TBL_ROOM.


Admin can disable the rooms under certain circumstances and saves the
details in TBL_ROOM.
2-LEVEL OF DEPARTMENT REGISTRATION (PROCESS

4.0)
DESCRIPTION
PROCESS 4.1 ADD –
Admin adds details of department of those property using this software
and saves the details in TBL_DEPARTMENT.
PROCESS 4.2 EDIT–
Admin can edit the details of department with enabling the disabled
department and saves the details in TBL_DEPARTMENT.

2-LEVEL OF LOCATION REGISTRATION (PROCESS 5.0)

DESCRIPTION
PROCESS 5.1 ADD –
Admin adds details of location of departments registered and saves the
details in TBL_LOCATION .
Admin can edit the details of location and saves the details in
TBL_LOCATION.

2-LEVEL OF ASSOCIATE REGISTRATION (PROCESS 6.0)

DESCRIPTION
PROCESS 6.1 ADD –
Admin adds details of those associates of those property using this
software and saves the details in TBL_USER .
PROCESS 6.2 EDIT–
Admin can edit the details of associates with enabling the disabled
associates and saves the details in TBL_USER.
Admin can disable the associates under certain circumstances and saves
the details in TBL_USER.

2-LEVEL OF FREQUENT REQUEST REGISTRATION

(PROCESS 7.0)
DESCRIPTION
PROCESS 7.1 ADD –
Admin adds details of frequently used request of those departments
registered and saves the details in TBL_FREQUENT_REQUEST .
Admin can edit the details of frequently used request and saves the details
in TBL_FREQUENT_REQUEST.

2-LEVEL OF MANAGE REQUEST (AYS) (PROCESS 10.0)

DESCRIPTION
PROCESS 10.1 ASSIGN –
Operator and manager can assign the request to the associates and saves
the details to TBL_REQUEST_AYS. After assigning the request, the
associates will be notified.
PROCESS 10.2 UPDATE –
Operator, manager and associate can update the status of the current
status and saves the details to TBL_REQUEST_AYS.
PROCESS 10.3 ESCALATED ASSIGN –
Manager can reassign the escalated request to the associates and saves the
details to TBL_REQUEST_AYS and TBL_ESCALATION_AYS. After
assigning the request, the associates will be notified.

2-LEVEL OF MANAGE QUERY (IDC) (PROCESS 13.0)

DESCRIPTION
PROCESS 10.1 ASSIGN – Users can assign the query to the manager of
the concerned department and saves the details to TBL_REQUEST_IDC.
After assigning the query, the manager will be notified.
PROCESS 10.2 UPDATE – Users can update the status of the current
status and saves the details to TBL_REQUEST_IDC.


DESCRIPTION
PROCESS 10.1.1 OPERATOR ASSIGN –
Operator can assign the request to the associates of the concerned
department and saves the details to TBL_REQUEST_AYS. After
assigning the request, the associate will be notified.
PROCESS 10.1.2 MANAGER ASSIGN –
Operator can assign the request to the associates of the concerned
department and saves the details to TBL_REQUEST_AYS. After
assigning the request, the associate will be notified.


DESCRIPTION
PROCESS 10.1.1 OPERATOR UPDATE –
Operator can update the status of the current status and saves the details
to TBL_REQUEST_AYS.
PROCESS 10.1.2 MANAGER UPDATE –
Manager can update the status of the current status and saves the details
to TBL_REQUEST_AYS.


DESCRIPTION
PROCESS 13.1.1 OPERATOR ASSIGN –
Operator can assign the query to the manager of the concerned
department and saves the details to TBL_REQUEST_IDC. After
assigning the query, the associate will be notified.
PROCESS 13.1.2 MANAGER ASSIGN –
Operator can assign the query to the associates of the concerned
PROCESS 13.1.3 MANAGEMENT ASSIGN –
PROCESS 13.1.4 GENERAL MANAGER ASSIGN –


DESCRIPTION
PROCESS 13.1.1 OPERATOR UPDATE –
Operator can update the status of the current status and saves the details
to TBL_REQUEST_IDC.
PROCESS 13.1.2 MANAGER UPDATE –
Manager can update the status of the current status and saves the details
to TBL_REQUEST_IDC.
PROCESS 13.1.3 MANAGEMENT UPDATE –
Management can update the status of the current status and saves the
details to TBL_REQUEST_IDC.
PROCESS 13.1.4 GENERAL MANAGER UPDATE –
General Manager can update the status of the current status and saves the
details to TBL_REQUEST_IDC.


5.3 ENTITY-RELATIONSHIP DIAGRAM

TBL_ADMIN
Admin_ID(Primary Key), Username, Password, Created_Date,
Disable_Date, Visibility.
TBL_DEPARTMENT
Dept_ID (Primary Key), P_ID(Foreign Key – References to tbl_property
to P_ID), Admin_ID(Foreign Key – References to tbl_admin to
Admin_ID),Dept_Name,Short_Name,Created_Date,Modified_Date,Disa
ble_Date,Visibility.
TBL_ESCALATION_AYS
Escalation_ID(Primary Key),P_ID(Foreign Key – References to
tbl_property to P_ID),Req_ID(Foreign Key – References to
tbl_request_ays to Req_ID), Assigned_To_AUID, MID, GMID, Status,
Start_Time, End_Time, Visibility.
TBL_FREQUENT_REQUEST
FR_ID(Primary Key),P_ID(Foreign Key – References to tbl_property to

P_ID),Dept_ID(Foreign Key – References to tbl_department to
Dept_ID),Admin_ID(Foreign Key – References to tbl_admin to
Admin_ID),Request_Name,Priority_Time,Created_Date,Modified_Date,
Disable_Date,Visibility.
TBL_LOCATION
Location_ID(Primary Key),Admin_ID(Foreign Key – References to
tbl_admin to Admin_ID),P_ID(Foreign Key – References to tbl_property
to P_ID),Dept_ID(Foreign Key – References to tbl_department to
Dept_ID),Location_Name,Created_Date,Modified_Date,Disable_Date,Vi
sibility.
TBL_NOTIFICATION
Noti_ID(Primary Key), User_ID(Foreign Key – References to tbl_user to
User_ID),Token,device_ID.
TBL_PROPERTY

P_ID(Primary Key),Admin_ID(Foreign Key – References to tbl_admin to

Admin_ID),Property_Name,Location,City,State,No_of_Rooms,No_of_O
utlets,Date_of_Inception,Colour,Property_Code,Created_Date,Modified_
Date,Disable_Date,Visibility.
TBL_REQUEST_AYS
Req_ID(Primary Key),FR_ID(Foreign Key – References to
tbl_frequent_request to FR_ID),Dept_ID(Foreign Key – References to
tbl_department to Dept_ID),P_ID(Foreign Key – References to
tbl_property to P_ID),User_ID(Foreign Key – References to tbl_user to
User_ID),Room_ID(Foreign Key – References to tbl_room to
Room_ID),Guest_Name,Associate_Name,Associate_Department,Check_
In,Check_Out,Start_Time,Priority_Time,Status,Remarks,Details,Request
_By,Completed_Time,End_Time,Call_Duration,Assigned_To_AUID,As
signed_MID,Escalation_Count,Visibility.
TBL_REQUEST_IDC
Idc_Req_ID(Primary Key),User_ID(Foreign Key – References to
tbl_user to User_ID),Dept_ID(Foreign Key – References to
tbl_department to Dept_ID),P_ID(Foreign Key – References to
tbl_property to P_ID),Location_ID(Foreign Key – References to
tbl_location to
Location_ID),Idc_Req_Name,Start_Time,Completed_Time,Status,Idc_R
eq_Details,Remarks,Assigned_To_UID,Assigned_By,Request_By_Dept.
TBL_ROLES
Role_ID(Primary Key),Role_Name.
TBL_ROOM
Room_ID(Primary Key),Admin_ID(Foreign Key – References to
to
P_ID),Room_No,Room_Type,Floor_No,Visibility,Reason,Created_Date,
Modified_Date,Disable_Date.

TBL_USER
User_ID(Primary Key),Admin_ID(Foreign Key – References to
to P_ID),Dept_ID(Foreign Key – References to tbl_department to
Dept_ID),Role_ID(Foreign Key – References to tbl_roles to
Role_ID),Name,Username,Password,Employee_Code,Floor_No,Mobile_
No,Created_Date,Modified_Date,Disable_Date,Visibility,Email.
CARDINALITY RATIO



DESIGN
6.1 FRONT-END SCREENSHOTS

LOGIN PAGE
EXPLAINATION
- This is the login page for all users for our software.
- For admin’s login username and password will be provided by
developers and admin have to check on admin’s checkbox.
- And for other users username and password will be provided by
admin.
Fig (I)

ADMIN PANEL
ADMIN DASHBOARD
EXPLAINATION
- Admin will able to see details of the property.
Fig (II)
VIEW REGISTERED PROPERTY

EXPLAINATION
- Admin will able to view, update and disable property that admin
has already registered.
Fig (III)

PROPERTY REGISTRATION
EXPLAINATION
- Admin will able to register a new property here by adding a
property details and submitting it.
Fig (IV)
UPDATE REGISTERED PROPERTY

EXPLAINATION
- Admin can able to update number of rooms, outlets, and property
code.

Fig (V)
VIEW REGISTERED ROOM

EXPLAINATION
- Admin will able to view and edit rooms that admin has already
registered.
Fig (VI)
ROOM REGISTRATION
EXPLAINATION
- Admin will able to register a new room here by adding room
details and submitting it.

Fig (VII)
UPDATE REGISTERED ROOM
EXPLAINATION
- Admin can able to update status of room and room category.
- If admin wants to disable room then reason is mandatory.
Fig (VIII)
VIEW REGISTERED DEPARTMENT

EXPLAINATION
- Admin will able to view, update and disable department that admin

Fig (IX)
DEPARTMENT REGISTRATION
EXPLAINATION
- Admin will able to register a new department here by adding
department details and submitting it.
Fig (X)
UPDATE REGISTERED DEPARTMENT

EXPLAINATION
- Admin can able to update name and short name of department.

Fig (XI)
VIEW REGISTERED LOCATION

EXPLAINATION
- Admin will able to view and update location that admin has already
registered.
Fig (XII)
LOCATION REGISTRATION
EXPLAINATION

- Admin will able to register a new location here by adding a

location details department wise and submitting it.
Fig (XIII)
UPDATE REGISTERED LOCATION
EXPLAINATION
- Admin can able to update status of location and change name of
location.
Fig (XIV)
VIEW REGISTERED FREQUENT REQUEST

EXPLAINATION

- Admin will able to view and update frequent request that admin
Fig (XV)
FREQUENT REQUEST REGISTRATION
EXPLAINATION
- Admin will able to register a new frequent request according to
department and submitting it.
Fig (XVI)
UPDATE REGISTERED FREQUENT REQUEST

EXPLAINATION

- Admin can able to update name of request and priority time.
Fig (XVII)
VIEW REGISTERED ASSOCIATE

EXPLAINATION
- Admin will able to view and update associate that admin has
already registered.
Fig (XVIII)
ASSOCIATE REGISTRATION

EXPLAINATION
- Admin will able to register a new associate by add associate details
and submitting it.
- If admin wants to give permission manager to access multi-
property then admin has to tick on property’s name.
- And for housekeeping associate admin has to assign floor number.
Fig (XIX)
UPDATE REGISTERED ASSOCIATE

EXPLAINATION
- Admin can able to update associate details and can also disable
associate from property.

Fig (XX)
OPERATOR PANEL
OPERATOR DASHBOARD
EXPLAINATION
- Operator can see the number of New, Work in progress, Pending
and Completed request on his dashboard.
Fig (XXI)
WEB NOTIFICATION
EXPLAINATION
- Operator will receive notification whenever status of request is
new.

Fig (XXII)
REQUEST REGISTRATION FORM - AYS (BY GUEST)

EXPLAINATION
- Operator fills the form according to request done by the guest
directly.
- On submitting it is directly sent to concerned department.
Fig (XXIII)
REQUEST REGISTRATION FORM (BY ASSOCIATE)

EXPLAINATION

- Operator fills the form according to request done by associate.

- On submitting it is directly sent to concerned department.
Fig (XXIV)
REQUEST STATUS(NEW)
EXPLAINATION
- Here, operator will able to see and can even assign the status of
request according to the actual status.

Fig (XXV)
ASSIGN STATUS
EXPLAINATION
- Here, operator can assign the status of request by assigning to
associate of concern department.
Fig (XXVI)
REQUEST STATUS (WORK IN PROGRESS, PENDING)

EXPLAINATION
- Here, operator can update the status of request according to the
actual status.
- Request in red are escalated request.

Fig (XXVII)
UPDATE STATUS
EXPLAINATION
- Here, operator updates the status of request by updating status and
remark in case of pending.

Fig (XXVIII)
REQUEST STATUS (ESCALATION)

EXPLAINATION
- Operator will able to see all escalated request and can even
Re-assign the status of request.
Fig (XXIX)

REQUEST REPORTS
- Operator will able to generated reports by selecting date range.
- Operator can even filter the reports as per the requirement of higher
authorities.
- Operator can also extract into excel and pdf.
Fig (XXX)
QUERY FORM - IDC

EXPLAINATION
- Operator can fill the query form whenever operator has a query for
any department and send it to the concerned department.

Fig (XXXI)
QUERY STATUS – IDC (NEW)

EXPLAINATION
- Operator can assign the status of the query according to its physical
status.
Fig (XXXII)
ASSIGN QUERY - IDC

EXPLAINATION

- Operator will able to assign employee and update status for query
registered.
Fig (XXXIII)
QUERY STATUS–IDC
(WORKING IN PROGRESS, PENDING)
EXPLAINATION
- Operator can update the status of the query according to its
physical status.

Fig (XXXIV)
UPDATE QUERY - IDC

EXPLAINATION
- Operator will able to update employee and update status for query
registered.
Fig (XXXV)
QUERY REPORTS - IDC

- Operator will able to generated reports by selecting date range.
- Operator can even filter the reports as per the requirement of higher
authorities.

- Operator can also extract into excel and pdf.
Fig (XXXVI)
MANAGER PANEL
MANAGER DASHBOARD
EXPLAINATION
- Manager can see the number of New, Work in progress, Pending
and Completed request on his dashboard.

Fig (XXXVII)
REQUEST STATUS (NEW)
EXPLAINATION
- Here, manager will able to see and can even assign the status of
request according to the actual status.
Fig (XXXVIII)
ASSIGN STATUS
EXPLAINATION
- Here, manager can assign the status of request by assigning to
associate of concern department.

Fig (XXXIX)
REQUEST STATUS (WORK IN PROGRESS, PENDING)

EXPLAINATION
- Here, manager can update the status of request according to the
actual status.
- Request in red are escalated request.
Fig (XL)
UPDATE STATUS

EXPLAINATION
- Here, manager updates the status of request by updating status and
Fig (XLI)
REQUEST STATUS (ESCALATION)

EXPLAINATION
- Manager will able to see all escalated request of their department
and can even Re-assign the status of request.
Fig (XLII)

REQUEST REPORTS
- Manager will able to generated reports by selecting date range.
- Manager can even filter the reports as per the requirement of higher
authorities.
- Manager can also extract into excel and pdf.
Fig (XLIII)
QUERY FORM - IDC

EXPLAINATION
- Manager can fill the query form whenever operator has a query for

Fig (XLIV)
EXPLAINATION
- Manager can assign the status of the query according to its physical
status.
Fig (XLV)
ASSIGN QUERY - IDC

EXPLAINATION
- Manager will able to assign employee and update status for query
registered.

Fig (XLVI)
QUERY STATUS–IDC
EXPLAINATION
- Manager can update the status of the query according to its
physical status.

Fig (XLVII)
UPDATE QUERY - IDC

EXPLAINATION
- Manager will able to update employee and update status for query
registered.
Fig (XLVIII)
QUERY REPORTS - IDC

- Manager will able to generated reports by selecting date range.
- Manager can even filter the reports as per the requirement of higher
authorities.

- Manager can also extract into excel and pdf.
Fig (XLIX)
USER PANEL
USER DASHBOARD
EXPLAINATION
- Associate can see the number of New, Pending and Completed
request on his dashboard.
Fig (L)

REQUEST STATUS (NEW)

EXPLAINATION
- Associate can see and update the status of request according to
their physical status.
Fig (LI)
REQUEST STATUS (PENDING)

EXPLAINATION
- Here, associate can update the status of request according to the
actual status.

Fig (LII)
UPDATE STATUS
EXPLAINATION
- Here, associate updates the status of request by updating status and
Fig (LIII)
REQUEST REPORTS
- Associate will able to generated reports by selecting date range.

- Associate can even filter the reports as per the requirement of

higher authorities.
- Associate can only get report of requests which is assigned to
them.
- Associate can also extract into excel and pdf.
Fig (LIV)
QUERY FORM - IDC

EXPLAINATION
- Associate can fill the query form whenever operator has a query for

Fig (LV)
QUERY STATUS–IDC (NEW, PENDING)

EXPLAINATION
- Associate can update the status of the query according to its
physical status.

Fig (LVI)
UPDATE QUERY - IDC

EXPLAINATION
- Associate will able to update status for query registered.
Fig (LVII)
QUERY REPORTS - IDC

- Associate will able to generated reports by selecting date range.
- Associate can even filter the reports as per the requirement of
higher authorities.

- Associate can also extract into excel and pdf.
Fig (LVIII)
GENERAL MANAGER PANEL

GENERAL MANAGER DASHBOARD
EXPLAINATION
- General manager can see the number of New, Work in progress,
Pending and Completed request on his dashboard.

Fig (LIX)
REQUEST STATUS - IDC

EXPLAINATION
- Here, general manager will able to see status of all request of
concern property.


Fig (LX)
REQUEST REPORTS
EXPLAINATION
- General manager will able to generated reports by selecting date
range.
- General manager can even filter the reports as per the requirement
of higher authorities.
- General manager can also extract into excel and pdf.
Fig (LXI)
QUERY FORM - IDC
EXPLAINATION
- General manager can fill the query form whenever general
manager has a query for any department and send it to the
concerned department.

Fig (LXII)

EXPLAINATION
- General manager can assign the status of the query according to its
physical status.
Fig (LXIII)
ASSIGN QUERY - IDC
EXPLAINATION
- General manager will able to assign employee and update status for
query registered.

Fig (LXIV)
QUERY STATUS–IDC
EXPLAINATION
- General manager can update the status of the query according to its
physical status.

Fig (LXV)
UPDATE QUERY - IDC

EXPLAINATION
- General manager will able to update employee and update status
for query registered.
Fig (LXVI)
QUERY REPORTS - IDC

- General manager will able to generated reports by selecting date
range.
- General manager can even filter the reports as per the requirement.

- General manager can also extract into excel and pdf.
Fig (LXVII)
MANAGEMENT PANEL
MANAGEMENT DASHBOARD
EXPLAINATION
- Management can see the number of New, Work in progress,
Pending and Completed request on his dashboard.
- Management can able to select any property and view status of all
request.
Fig (LXVIII)

REQUEST STATUS - IDC

EXPLAINATION
- Here, management will able to see status of all request of selected
property.

Fig (LXIX)
REQUEST REPORTS
EXPLAINATION
- Management will able to generated reports by selecting date range.
- Management can even filter the reports as per the requirement.
- Management can also extract into excel and pdf.

Fig (LXX)
QUERY FORM - IDC

EXPLAINATION
- Management can fill the query form whenever general manager has
a query for any department and send it to the concerned
department.
Fig (LXXI)


EXPLAINATION
- Management can assign the status of the query according to its
physical status.
Fig (LXXII)
ASSIGN QUERY - IDC

EXPLAINATION
- Management will able to assign employee and update status for
query registered.
Fig (LXXIII)

QUERY STATUS–IDC
EXPLAINATION
- Management can update the status of the query according to its
physical status.
Fig (LXXIV)
UPDATE QUERY - IDC

EXPLAINATION
- Management will able to update employee and update status for
query registered.

Fig (LXXV)
QUERY REPORTS – IDC

EXPLAINATION
- Management will able to generated reports by selecting date range.
- Management can even filter the reports as per the requirement.
Management can also extract into excel and pdf.
Fig (LXXVI)

6.2 LIST OF DATABASE TABLES



6.3 BACK-END SCREENSHOTS

tbl_admin
EXPLAINATION
- Admin’s username and password is matched from the tbl_admin
table, as referred from fig ().
Fig ()

tbl_department
EXPLAINATION
- Admin can add new department through department registration as
referred from fig (III) and the details are saved in tbl_department
table.
Fig ()
tbl_escalation_ays
EXPLAINATION
- Whenever request is escalated, the details of that request are
inserted here.
Fig ()
tbl_frequent_request
EXPLAINATION
- Admin registers complain for drop down as referred in fig () and
stores all details in tbl_frequent_request.

Fig ()
tbl_location
EXPLAINATION
- Admin can add new location through location registration as
referred from fig () and the details are saved in tbl_location.
tbl_notification
EXPLAINATION
- whenever user install application and login to system the details
are saved in tbl_notification.
tbl_request_ays
EXPLAINATION
- When operator fills the request form as referred in fig () all the
details are stored in tbl_request_ays.

Fig ()
tbl_request_idc
EXPLAINATION
- When any user fills a query form all the details are stored in
tbl_request_idc.
Fig ()
tbl_roles
EXPLAINATION
- Admin can add new room through room registration as referred
from fig () and the details are saved in tbl_roles table.
Fig ()

tbl_user
EXPLAINATION
- Admin can add new associate through associate registration as
referred from fig () and the details are saved in tbl_user table.
Fig ()

SOURCE CODE
ADMIN
ROOM REGISTRATION
<!DOCTYPE html>
<html>
<?php
session_start();
include './databaseconnection.php';
if (empty($_SESSION['type'])) {
header('Location:index.php');
}
?>
<?php include './temp/left-side.php'; ?>
<?php include './temp/Header.php'; ?>

<?php
function load_propt()
{include './databaseconnection.php';
$output="";
$sql="select * FROM tbl_property where visibility = 1";

$result= mysqli_query($con, $sql);

while($row= mysqli_fetch_array($result))
{
$output.= '<option
value="'.$row['P_ID'].'">'.$row['Property_Name'].'</option>';
}
return $output;
}
?>
<script language="Javascript" type="text/javascript">
function onlyAlphabets(e, t) {
try {
if (window.event) {
var charCode = window.event.keyCode;
} else if (e) {
var charCode = e.which;
} else {
return true;
}
if ((charCode > 64 && charCode < 91) || (charCode > 96 &&
charCode < 123) || (charCode > 31 && charCode < 33 ) )
return true;
else
return false;
} catch (err) {
alert(err.Description);

}
}
function isNumber(evt) {
evt = (evt) ? evt : window.event;
var charCode = (evt.which) ? evt.which : evt.keyCode;
if (charCode > 31 && (charCode < 48 || charCode > 57)) {
return false;
}
return true;
}
</script>
<body class="with-side-menu ">
<div class="page-content">
<div class="container-fluid">
<?php if (isset($_GET['err']) && $_GET['err'] == 1) { ?>
<div class="alert alert-danger alert-no-border alert-txt-
colored alert-close alert-dismissible fade show" role="alert">
<button type="button" class="close" data-dismiss="alert"
aria-label="Close">
<span aria-hidden="true">×</span>
</button>
<strong>Error!</strong> Priority must be greater than 5
minutes

</div>
<?php
}
?>
<div align="right">
<button class="btn btn-inline btn-primary"
data-toggle="modal"
data-target=".bd-example-modal-lg">Add New
Request</button>
</div>
<div class="modal fade bd-example-modal-lg"

tabindex="-1"
role="dialog"
aria-labelledby="myLargeModalLabel"
aria-hidden="true">
<div class="modal-dialog modal-lg">
<form id="Rooms_reg" onsubmit="return myFunction()"
action="Req_Reg.php" name="form-signup_v1" method="POST">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="modal-close" data-
dismiss="modal" aria-label="Close">
<i class="font-icon-close-2"></i>
</button>
<h4 class="modal-title"
id="myModalLabel">Request Registration</h4>

</div>
<div class="modal-body">
<div class="form-group">
<label class="form-label"
for="P_ID">Property</label>
<div class="form-control-wrapper">
<select id="P_ID"
data-validation =[NOTEMPTY]
data-validation-message="Please Select
Property"
name="P_ID"
class="form-control">
<option value="">Select</option>
<?php echo load_propt();
?>
</select>
</div>
</div>
for="department">Department</label>
<select id="department"
name="Department"
class="form-control"

data-validation-message="Please Select
Department"
>
<option value="">Select</option>
</select>
</div>
</div>
for="rcat">Request</label>
<input id="rcat"
type="text"
name="Requestname"
onkeypress="return onlyAlphabets(event,
this);"
data-validation-message="Please Enter
Room Categoty"
>
</div>
</div>
<label class="form-label" for="Priority">Set
Priority Time(In Min)</label>
<input id="Priority"

type="text"
name="Priority"
onkeypress="return isNumber(event)"
data-validation ="[L<3]"
oninput="check(this)"
data-validation-message="Please Enter
Floor & less than 3 digits"
>
<div id="demo"></div>
</div>
</div>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-rounded btn-
default" data-dismiss="modal">Close</button>
<button type="submit" class="btn btn-rounded btn-
primary">Submit</button>
</div>
</div>
</form>
</div>
</div>
<?php
$query = "SELECT * FROM tbl_frequent_request WHERE Visibility =
1 ";

$result = mysqli_query($con, $query);

?>
<section class="card">
<div class="card-block">
<form method="post" name="myform"
id="myform">
<table width="100%" class=table table-responsive
table-bordered id="rooms">
<thead class=bg-blue>
<tr>
<th># No</th>
<th>Request</th>
<th>Priority Time</th>
<th>Department</th>
<th>Property</th>
<th>Action</th>
</tr>
</thead>
<?php
$count=1;
while ($row = mysqli_fetch_array($result)) {
?>
<tr>
<td><?php echo $count;$count++; ?></td>
<td><?php echo $row["Request_Name"]?></td>
<td><?php echo $row["Priority_Time"]?></td>

<td><?php $Dept_ID = $row["Dept_ID"];

$sqli= "Select Dept_Name FROM tbl_department WHERE
Dept_ID = $Dept_ID ";
$Result= mysqli_query($con, $sqli);
while($row1= mysqli_fetch_assoc($Result)){
echo $row1['Dept_Name'];
}
?></td>
<td><?php $pid= $row['P_ID'];
$sql =
"Select Property_Name from tbl_property where P_ID=".$pid ;
$res =
mysqli_query($con,$sql);
while($r
ow1 = mysqli_fetch_assoc($res)){
echo
$row1['Property_Name'];
}
?></td>
<td>
<a href="Req_Update.php?id=<?php echo $row["FR_ID"] ?>"
class="button button1">Update</a><br>
</td>
</tr>
<?php

}
?>
</table>
</form>
</div>
</section>
</div>
</div>
<?php include './temp/autoload-last.php'; ?>

<?php include './temp/autoload-lastcss.php'; ?>
<script>
function myFunction() {
var text;
xs = document.getElementById("Priority").value;
var x = document.forms["Room_reg"]["Priority"].value;
if (x < 5) {
alert("Input not valid");
return false;
} else {
alert("Input OK");
return false;

}
}
</script>
<script>
$(function () {
$('#Rooms_reg').validate({
submit: {
settings: {
inputContainer: '.form-group',
errorListClass: 'form-tooltip-error'
}
}
});
});
$('.flatpickr').flatpickr();
</script>
<script>
$(function () {
$('#rooms').DataTable({
responsive: true,
dom: 'Bfrtip',
buttons: [
{

extend: 'excelHtml5',
title: 'Request',
customize: function( xlsx ) {
var sheet = xlsx.xl.worksheets['sheet1.xml'];
$('row c[r^="A"]', sheet).attr( 's', '2' );

}
},
{
extend: 'pdfHtml5',
title: 'Request',
orientation: 'landscape',
pageSize: 'LEGAL',
messageTop: 'List of Property',
}
]
});
});
</script>
<script>
$(document).ready(function () {
$('#P_ID').change(function () {
var pid = $(this).val();
$.ajax({
url: "fetch.php",

method: "POST",
data: {pid: pid},
dataType: "text",
success: function (data)
{
$('#department').html(data);
}
});
});
})
</script>
</body>
</html>

OPERATOR
OPERATOR REQUEST STATUS
<!DOCTYPE html>
<html>
<?php
session_start();
}
?>

<script type="text/javascript" src="jquery-latest.pack.js"

language="javascript"></script>
<script type="text/javascript" language="javascript">
$(document).ready(function(){
setInterval(function(){

var postData = ''; // you can send any data to ajax file.
$.ajax( {
url : 'operator_cntajax.php',
type : 'post',
data : postData,
success : function( resp ) {
$('#new1').html($('#new' , resp).html());
$('#wip1').html($('#wip' , resp).html());
$('#pen1').html($('#pen' , resp).html());
$('#esc1').html($('#esc' , resp).html());
}
});
return false;
}, 2000);
});
</script>

<section class="tabs-section">
<div class="tabs-section-nav">

<div class="tbl">
<ul class="nav" role="tablist">
<li class="nav-item">
<a class="nav-link active" href="#tabs-2-
tab-1" role="tab" data-toggle="tab">
<span class="nav-link-in">
NEW
<span class="label label-pill label-
success"><div id=new1></div></span>
</span>
</a>
</li>
<a class="nav-link" href="#tabs-2-tab-2"
role="tab" data-toggle="tab">
WORK-IN-PROGRESS
warning"><div id=wip1></div></span>
</span>
</a>
</li>

PENDING
danger"><div id=pen1></div></span>
</span>
</a>
</li>
ESCALATION
info"><div id=esc1></div></span>
</span>
</a>
</li>
</ul>
</div>
</div>
<div class="tab-content">
<div role="tabpanel" class="tab-pane fade in
active show" id="tabs-2-tab-1">
<section class="card card-green mb-3">
<header class="card-header">

<h3 align="center"> New Request</h3>
</header>
<script>
$.ajax({
url:"operator_new.php",
method:"POST",
dataType:"text",
success:function(data)
{
$('#new').html(data);
}
})
});
</script>
<table class="table table-bordered table-

hover table-sm">
<thead>

<tr>
<th width="100">ROOM
NO</th>
<th>DEPARTMENT</th>
<th>REQUEST</th>
<th >PRIORTY</th>
<th>
ACTION
</th>
</tr>
</thead>
<tbody id="new">
</tbody>
</table>
<script>
$.ajax({
url:"operator_new.php",
method:"POST",
dataType:"text",
{

}
})
},3000);
</script>
</div>
</section>
</div>
<div role="tabpanel" class="tab-pane fade"
id="tabs-2-tab-2">
<section class="card card-orange mb-3">
<h3 align="center"> Work in progress
Request</h3>
</header>
<script>
$.ajax({

url:"operator_working.php",
method:"POST",
dataType:"text",
{
$('#wip').html(data);
}
})
});
</script>
<table class="table table-bordered table-

hover table-sm">
<thead>
<tr>
<th width="100">ROOM
NO</th>
<th>DEPARTMENT</th>
<th>REQUEST</th>
<th width="120">PRIORTY</th>
<th>ASSIGNED TO</th>
<th>

ACTION
</th>
</tr>
</thead>
<tbody id="wip">
</tbody>
</table>
<script>
$.ajax({
url:"operator_working.php",
method:"POST",
dataType:"text",
{
}
})
},3000);
</script>
</div>

</section>
id="tabs-2-tab-3">
<section class="card card-red mb-3">
<h3 align="center"> Pending
Request</h3>
</header>
<script>
$.ajax({
url:"operator_pending.php",
method:"POST",
dataType:"text",
{
$('#pending').html(data);
}

})
});
</script>
<table id="table-sm" class="table table-

bordered table-hover table-sm">
<thead class="bg-red">
<tr>
<th width="100">ROOM NO</th>
<th>DEPARTMENT</th>
<th>REQUEST</th>
<th>PRIORITY</th>
<th>ASSIGNED TO</th>
<th>ACTION</th>
</tr>
</thead>
<tbody id="pending">
</tbody>
</table>
<script>
$.ajax({

url:"operator_pending.php",
method:"POST",
dataType:"text",
{
}
})
},3000);
</script>
</div>
</section>
id="tabs-2-tab-4">
<section class="card card-purple mb-3">
<h3 align="center"> Escalated
Request</h3>
</header>

<script>
$.ajax({
url:"operator_escalation_new.php",
method:"POST",
dataType:"text",
{
$('#esc').html(data);
}
})
});
</script>
<table id="table-sm" class="table table-

bordered table-hover table-sm">
<thead>
<tr>
<th>DEPARTMENT</th>

<th>REQUEST</th>
<th>END TIME</th>
<th>ACTION</th>
</tr>
</thead>
<tbody id="esc">
</tbody>
</table>
<script>
$.ajax({
method:"POST",
dataType:"text",
{
}
})
},3000);
</script>


<div id="screen"></div>
</div>
</section>
</div>
</section>
</body>

<?php
include './temp/autoload-lastcss.php'; ?>
</html>

MANAGER
NEW_REQUES_DISPLAY (ANDROID)
package com.h2h.fragments;
import android.app.ProgressDialog;
import android.graphics.Color;
import android.os.Bundle;
import android.support.annotation.Nullable;
import android.support.v4.app.Fragment;
import android.support.v4.widget.SwipeRefreshLayout;
import android.support.v7.widget.CardView;
import android.support.v7.widget.LinearLayoutManager;
import android.support.v7.widget.RecyclerView;
import android.util.Log;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;
import android.widget.TextView;
import android.widget.Toast;
import com.android.volley.AuthFailureError;
import com.android.volley.Request;
import com.android.volley.RequestQueue;
import com.android.volley.Response;
import com.android.volley.VolleyError;
import com.android.volley.toolbox.JsonArrayRequest;
import com.android.volley.toolbox.JsonObjectRequest;
import com.android.volley.toolbox.StringRequest;
import com.h2h.Adapter.NewARequestAdapter;
import com.h2h.Adapter.NewHKRequestAdapter;
import com.h2h.Adapter.NewRequestAdapter;
import com.h2h.GeneralManagerAdapters.NewGRequestAdapter;
import com.h2h.R;
import com.h2h.model.RequestModel;
import com.h2h.util.SharedPreferanceManager;
import com.h2h.util.SingleTonNetworkReq;
import com.h2h.util.StatusCallBack;
import org.json.JSONArray;
import org.json.JSONObject;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.Map;
import static com.h2h.util.AppConstants.ANEW_URL;

import static com.h2h.util.AppConstants.APP_URL;
import static com.h2h.util.AppConstants.APP_URL1;
import static com.h2h.util.AppConstants.GM_NEW_REQUEST;
import static com.h2h.util.AppConstants.HK_NEW_URL;
import static com.h2h.util.AppConstants.WORK_URL;
import static com.h2h.util.AppConstants.WOR_URL;
public class NewRequest extends Fragment {
public static final String TAG = NewRequest.class.getSimpleName();

public NewRequestAdapter mAdapter;
public NewARequestAdapter mmAdapter;
public NewGRequestAdapter mmmAdapter;
public NewHKRequestAdapter mmmmAdapter;
SwipeRefreshLayout swipeRefresh;
TextView txtnodata;
RecyclerView recyclerView;

CardView cardView;
private SharedPreferanceManager preferanceManager;
private ArrayList<RequestModel> requestModels;
private ProgressDialog progressDialog;
public NewRequest() {
}
@Override
public void onCreate(@Nullable Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
}
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container,
Bundle savedInstanceState) {
View rootView = inflater.inflate(R.layout.newrequest, container,

false);
// swipeRefresh = rootView.findViewById(R.id.swipeRefresh);
recyclerView = rootView.findViewById(R.id.recycle);
cardView = rootView.findViewById(R.id.cardview1);
txtnodata = (TextView) rootView.findViewById(R.id.txtnodata);
recyclerView.setLayoutManager(new
LinearLayoutManager(getActivity()));
requestModels = new ArrayList<>();
preferanceManager = new SharedPreferanceManager(getActivity());
final String rolename = preferanceManager.getKeyRoleId(); //here you
are saving role as id and compare with name so its alwys wrong so
final String dept = preferanceManager.getKeyDeptName();
final String manager = "Manager";
final String associate = "Associate";
final String gm = "General Manager";
final String manage = "Management";
final String department = "Housekeeping";
// JSON data web call function call from here.
if (rolename.equals(manager)) {
getrequests();
}
if (rolename.equals(associate)) {
getassociaterequests();
}
if (rolename.equals(gm)) {
getgeneralrequests();
}
if (rolename.equals(manage)) {
getgeneralrequests();
}
if (rolename.equals(associate) && dept.equals(department)) {
gethkrequests();
}
return rootView;
}
private void getrequests() {

JSONObject params = null;
try {
// if (!swipeRefresh.isRefreshing()) {
progressDialog = new ProgressDialog(getActivity());
progressDialog.setMessage("" +
"Fetching New Tasks....");
progressDialog.show();
// }
params = new JSONObject();
SharedPreferanceManager preferanceManager = new
SharedPreferanceManager(getActivity());

Log.e("In NewRequest", "Params PId : " +

preferanceManager.getKeyPId() + " AId : "
+ preferanceManager.getKeyUserId());
params.put("p_ID", preferanceManager.getKeyPId());
params.put("a_id", preferanceManager.getKeyUserId());
} catch (Exception e) {
e.printStackTrace();
}
final JsonObjectRequest stringRequest = new
JsonObjectRequest(Request.Method.POST, APP_URL + WOR_URL, params,
new Response.Listener<JSONObject>() {
@Override
public void onResponse(JSONObject response) {
try {
// if (progressDialog != null)
progressDialog.dismiss();
if (response.length() > 0) {
if (txtnodata.isShown()) {
txtnodata.setVisibility(View.VISIBLE);
}
JSONArray jsonArray =
response.getJSONArray("AYS");
Log.e("In NewRequest", "Response length : "
+ jsonArray.length());
for (int i = 0; i < jsonArray.length(); i++)
{
JSONObject object =
jsonArray.getJSONObject(i);
RequestModel details = new
RequestModel();
details.setReq_ID(object.getString("req_ID"));
details.setRoom_no(object.getString("room_no"));
details.setStatus(object.getString("status"));
Log.e("In NewRequest", "Request name : "
+ object.getString("requestname"));
details.setRequest_name(object.getString("requestname"));
/*details.setAssigned(object.getString("assigned"));*/
details.setDtls(object.getString("dtls"));
details.setDept_name(object.getString("dept_name"));
details.setPriority_time(object.getString("priority_time"));
//details.setIs_read(object.getString("is_read"));
/* if (details.getIs_read().equals(204)){
cardView.setCardBackgroundColor(Color.GREEN);
}*/
requestModels.add(details);
}
if (requestModels.size() > 0) {
mAdapter = new
NewRequestAdapter(getActivity(), requestModels, new StatusCallBack() {
@Override
public void OnStatusUpdate(String
req_ID) {
/*statusUpdate(req_ID);*/
}
});

recyclerView.setAdapter(mAdapter);
mAdapter.notifyDataSetChanged();
} else {
recyclerView.setVisibility(View.GONE);
}
} else {
}
Log.e("In NewRequest", "Excp Msg : " +
e.getMessage());
}
}
},
new Response.ErrorListener() {
@Override
public void onErrorResponse(VolleyError error) {
Log.d(TAG, "onErrorResponse: saveTransaction :" +
error.getMessage());
}
}) {
@Override
protected VolleyError parseNetworkError(VolleyError volleyError)
{
if (volleyError.networkResponse != null &&
volleyError.networkResponse.data != null) {
volleyError = new VolleyError(new
String(volleyError.networkResponse.data));
}
return volleyError;
}
@Override
public Map<String, String> getHeaders() throws AuthFailureError
{
HashMap<String, String> headers = new HashMap<>();
// headers.put("Content-Type", "application/json");
return headers;
}
};
SingleTonNetworkReq.getInstance(getActivity()).addToRequestQueue(stringReque
st.setTag(TAG));
}
/*ASSOCIATE NEW REQUESTS DISPLAY FUNCTION*/

private void getassociaterequests() {
try {
"Fetching Data...");
String pid = preferanceManager.getKeyPId();
//Toast.makeText(getActivity(), pid, Toast.LENGTH_SHORT).show();

}
JsonObjectRequest(Request.Method.POST, APP_URL + ANEW_URL, params,
@Override
try {
}
{
JSONObject object =
RequestModel();
details.setRequest_name(object.getString("request_name"));
details.setAssigned(object.getString("assigned"));
}
mmAdapter = new
NewARequestAdapter(getActivity(), requestModels, new StatusCallBack() {
@Override
req_ID) {
}
});
recyclerView.setAdapter(mmAdapter);
mmAdapter.notifyDataSetChanged();
} else {
}
} else {
}
}

}
},
@Override
}
}) {
@Override
{
}
return volleyError;
}
@Override
{
return headers;
}
};
st.setTag(TAG));
}
private void getgeneralrequests() {

try {
}
JsonObjectRequest(Request.Method.POST, APP_URL + GM_NEW_REQUEST, params,
@Override
try {

}
{
JSONObject object =
RequestModel();
}
mmmAdapter = new
NewGRequestAdapter(getActivity(), requestModels, new StatusCallBack() {
@Override
req_ID) {
}
});
recyclerView.setAdapter(mmmAdapter);
mmmAdapter.notifyDataSetChanged();
} else {
}
} else {
}
}
}
},
@Override
}
}) {
@Override
{


}
return volleyError;
}
@Override
{
return headers;
}
};
st.setTag(TAG));
}
private void gethkrequests() {

try {
}
JsonObjectRequest(Request.Method.POST, APP_URL + HK_NEW_URL, params,
@Override
try {
}
{
JSONObject object =
RequestModel();

}
mAdapter = new
NewRequestAdapter(getActivity(), requestModels, new StatusCallBack() {
@Override
req_ID) {
}
});
recyclerView.setAdapter(mAdapter);
mAdapter.notifyDataSetChanged();
} else {
}
} else {
}
}
}
},
@Override
}
}) {
@Override
{
}
return volleyError;
}
@Override
{
return headers;
}
};

st.setTag(TAG));
}
}
MANAGER QUERY
<!DOCTYPE html>
<?php
session_start();
?>

<html>
<?php
function load_dept()
{
include 'databaseconnection.php';
$output="";
$sql="select * FROM tbl_department WHERE
P_ID=".$_SESSION['P_ID']."";
{
$output.= '<option
value="'.$row['Dept_ID'].'">'.$row['Dept_Name'].'</option>';
}

return $output;
}
?>
<div class="tbl">
<div class="tbl-row">
<div class="tbl-cell">
<h3>
<div style="background:#7ac0c9" class="card-
block">
<br>
<h5><center><b>REQUEST
FORM</b></center></h5>
</div>
</section>
</h3>

</div>
</div>
</div>
<form id="operator_request_form"
action="manager_insertquery.php" name="form-signup_v1"
method="POST">
<div class="row">
<div class="col-md-4">
</div>
for="Department_name">Department name</label>
<select id="Department_name"
name="department"
data-validation =[NOTEMPTY]>
<option value="">Select Department</option>

<?php echo load_dept(); ?>
</select>
</div>
</div>

for="location">Location</label>
<select id="location"
name="location"
data-validation="[NOTEMPTY]">
<option value="">Select </option>
<?php
if($stmt=$con->query("select * from tbl_location where
P_ID=".$_SESSION['P_ID']." AND Dept_ID In (SELECT Dept_ID
from tbl_user where User_ID=".$_SESSION['username']." AND
P_ID=".$_SESSION['P_ID']." )"))
{
while($r=$stmt->fetch_array(MYSQLI_ASSOC))
{
?>
<option value="<?php echo $r['Location_ID']?>"><?php echo
$r['Location_Name']?></option>
<?php } } ?>
</select>
</div>
</div>

for="query">Query</label>
<input id="query"
name="query"
type="text"
data-validation="[NOTEMPTY]"
data-validation-message="Please fill Lead
Time ">
</div>
</div>
for="Details">Details</label>
<textarea id="Details"
name="details"
data-validation="[]"
data-validation-message="$"></textarea>
</div>
</div>

</div>
</div>
<div class="row">
<center>
<button type="submit" class="btn">Submit</button>
</center>
</div>
</div>
</div>
</form>
<?php include './temp/autoloadlast.php'; ?>

<script>
$(function () {
$('#operator_request_form').validate({
submit: {
settings: {
}
}
});
});
</script>
</body>
</html>

ASSOCIATE
USER HKREQUEST STATUS(HOUSEKEEPING USER)
<!DOCTYPE html>
<html>
<?php
session_start();
}
?>

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

var postData = ''; // you can send any data to ajax file.
$.ajax( {
url : 'user_hkcntajax.php',
type : 'post',
data : postData,
success : function( resp ) {

$('#new1').html($('#new' , resp).html());
$('#wip1').html($('#wip' , resp).html());
$('#pen1').html($('#pen' , resp).html());
}
});
return false;
}, 2000);
});
</script>

aria-label="Close">
</button>
<strong>Error!</strong> Data not inserted.
</div>
<?php
}
?>


aria-label="Close">
</button>
<strong>Error!</strong> enter remarks.
</div>
<?php }?>
<section class="tabs-section">
<div class="tabs-section-nav">
<div class="tbl">
<ul class="nav" role="tablist">
<a class="nav-link active" href="#tabs-2-tab-1"
NEW
success"><div id=new1></div></span>
</span>
</a>
</li>
WORK-IN-PROGRESS
warning"><div id=wip1></div></span>

</span>
</a>
</li>
PENDING
danger"><div id=pen1></div></span>
</span>
</a>
</li>
ESCALATION
info"></span>
</span>
</a>
</li>
</ul>
</div>
</div>

<div class="tab-content">
<div role="tabpanel" class="tab-pane fade in active show"
id="tabs-2-tab-1">
<section class="card card-green mb-3">
<h3 align="center"> New Request</h3>
</header>
<script>
$.ajax({
url:"userhk_new.php",
method:"POST",
dataType:"text",
{
}
})
});
</script>

<table class="table table-bordered table-hover

table-sm">
<thead>
<tr>
<th>REQUEST</th>
<th >PRIORTY</th>
<th>
ACTION
</th>
</tr>
</thead>
<tbody id="new">
</tbody>
</table>
<script>
$.ajax({
url:"userhk_new.php",
method:"POST",
dataType:"text",
{

}
})
},1000);
</script>
</div>
</section>
<div role="tabpanel" class="tab-pane fade" id="tabs-2-
tab-2">
<section class="card card-orange mb-3">
<h3 align="center"> Work in progress
Request</h3>
</header>
<script>
$.ajax({
url:"userhk_working.php",
method:"POST",

dataType:"text",
{
}
})
});
</script>
<table class="table table-bordered table-hover

table-sm">
<thead>
<tr>
<th>ROOM NO</th>
<th>REQUEST</th>
<th >PRIORTY</th>
<th>
ACTION
</th>
</tr>
</thead>
<tbody id="wip">

</tbody>
</table>
<script>
$.ajax({
url:"userhk_working.php",
method:"POST",
dataType:"text",
{
}
})
},3000);
</script>
</div>
</section>
tab-3">
<section class="card card-red mb-3">
<h3 align="center"> Pending Request</h3>

</header>
<script>
$.ajax({
url:"userhk_pending.php",
method:"POST",
dataType:"text",
{
}
})
});
</script>
<table id="table-sm" class="table table-bordered

table-hover table-sm">
<thead class="bg-red">
<tr>
<th>ROOM NO</th>
<th>REQUEST</th>
<th>PRIORITY</th>

<th>REMARKS</th>
<th>ACTION</th>
</tr>
</thead>
<tbody id="pending">
</tbody>
</table>
<script>
$.ajax({
url:"userhk_pending.php",
method:"POST",
dataType:"text",
{
}
})
},3000);
</script>
</div>
</section>


tab-4">
<section class="card card-purple mb-3">
<h3 align="center"> Escalated Request</h3>
</header>
<script>
$.ajax({
method:"POST",
dataType:"text",
{
}
})
});
</script>

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

table-hover table-sm">
<thead>
<tr>
<th>ROOM NO</th>
<th>DEPARTMENT</th>
<th>REQUEST</th>
<th>END TIME</th>
<th>ACTION</th>
</tr>
</thead>
<tbody id="esc">
</tbody>
</table>
<script>
$.ajax({
method:"POST",
dataType:"text",
{
}
})

},3000);
</script>
</div>
</section>
</div>
</section>
</body>
</html>

GENERAL MANAGER
GENERALMANAGER QUERY
<!DOCTYPE html>
<?php
session_start();
?>

<html>
<?php
function load_dept()
{
include 'databaseconnection.php';
$output="";
$sql="select * FROM tbl_department WHERE
P_ID=".$_SESSION['P_ID']."";
{
$output.= '<option
value="'.$row['Dept_ID'].'">'.$row['Dept_Name'].'</option>';
}
return $output;
}

?>
<div class="tbl">
<div class="tbl-row">
<div class="tbl-cell">
<h3>
<div style="background:#7ac0c9" class="card-
block">
<br>
<h5><center><b>REQUEST
FORM</b></center></h5>
</div>
</section>
</h3>
</div>
</div>
</div>

<form id="generalmanager_request_form"
action="generalmanager_insertquery.php" name="form-signup_v1"
method="POST">
<div class="row">
</div>
for="Department_name">Department name</label>
<select id="Department_name"
name="department"
data-validation =[NOTEMPTY]>
<option value="">Select Department</option>

<?php echo load_dept(); ?>
</select>
</div>
</div>
for="location">Location</label>
<select id="location"

name="location"
data-validation="[NOTEMPTY]">
<option value="">Select </option>
<?php
if($stmt=$con->query("select * from tbl_location where
P_ID=".$_SESSION['P_ID']." AND Dept_ID In (SELECT Dept_ID
from tbl_user where User_ID=".$_SESSION['username']." AND
P_ID=".$_SESSION['P_ID']." )"))
{
while($r=$stmt->fetch_array(MYSQLI_ASSOC))
{
?>
<option value="<?php echo $r['Location_ID']?>"><?php echo
$r['Location_Name']?></option>
<?php } } ?>
</select>
</div>
</div>
for="query">Query</label>
<input id="query"
name="query"
type="text"
data-validation="[NOTEMPTY]"

data-validation-message="Please fill Lead

Time ">
</div>
</div>
for="Details">Details</label>
<textarea id="Details"
name="details"
data-validation="[]"
data-validation-message="$"></textarea>
</div>
</div>
</div>
</div>
<div class="row">
<center>
<button type="submit" class="btn">Submit</button>
</center>
</div>

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

<script>
$(function () {
$('#generalmanager_request_form').validate({
submit: {
settings: {
}
}
});
});
</script>
</body>
</html>

MANAGEMENT
Management Dashboard
<!DOCTYPE html>
<html>
<?php
session_start();
}
?>

<script
type="text/javascript" language="javascript">
var
postData = ''; // you can send any data to ajax file.
$.ajax( {
url
: 'management_cntajax.php',

type :
'post',
data :
postData,
success :
function( resp ) {
$('#new')
.html($('#new' , resp).html());
$('#wip').
html($('#wip' , resp).html());
$('#pen').
html($('#pen' , resp).html());
$('#don').
html($('#don' , resp).html());
});
return
false;

},
2000);
});
</script>
<div
class="page-content">
<div
class="container-fluid">
<h1>Das
hboard</h1>
<div class="row">
<div class="col-xl-6">
<div class="row">
<div class="col-sm-6">
<article class="statistic-box green">

<div>
<div class="number"><div id="new"></div></div>
<div class="caption"><div>New Request</div></div>
</div>
</article>
</div>

<article class="statistic-box yellow">
<div>
<div class="number"><div id="wip"></div></div>
<div class="caption"><div>Work In Progress</div></div>

</div>
</article>
</div>
<article class="statistic-box red">
<div>
<div class="number"><div id="pen"></div></div>
<div class="caption"><div>Pending</div></div>
</div>
</article>
</div>

<article class="statistic-box purple">
<div>
<div class="number"><div id="don"></div></div>
<div class="caption"><div>Completed</div></div>
</div>
</article>
</div>
</div>
</div>

<div class="col-xl-6 ">
<div id="pie-chart"></div>
</div>
</section>
</div>
</div>
</div>


</div>
</div><!
--.page-content-->
<?php
include './temp/autoload-last.php'; ?>
<?php
include './temp/autoload-lastcss.php'; ?>
</body>
</html>

TESTING AND IMPLEMENTATION
Testing is the main phase while developing a software because it will

help you to find bugs, errors improvements required by clients, additions,
subtractions if any and it checks the security of software whether the data
is protected or not.
Testing also helps in giving the picture of software in real environment as
it will take real data and test the software in live which will help the
testers know whether the software will able to handle load, is it reliable
and is it providing us with the performance client is expecting.
Some of the important tests that all the testers always use to test any
software are alpha testing, beta testing, unit testing, integration testing,
system testing, load testing and many more. These are the basic tests
which testers generally do while testing the software.
We have also used these test to test our software and make it as user
efficient and friendly as possible. We have done several tests in our
software which has helped us in testing each and every unit and module
of the software.
We have tested each unit and module individually to make sure that the
software is user friendly and it is giving desired outputs. So, we have
provided a example for each test we have performed from our side. We
are satisfied by the outputs and testing we have done.
As we are satisfied from our side now we have given our software to the
hotel management system and asked them to perform tests from their side
in live environment. This will not only help clients to know their solution
but it will also help developers to know their flaws.
So, now our software is under testing at The Taj Gateway. After all the
requirements are specified and users are satisfied by the end result it will
be implemented in The Taj Gateway and Courtyard By Marriot.

UNIT TESTING
Unit testing is testing of individual software components or modules.
TITLE: Admin Login Page – Authenticates admin successfully. (Fig (I))

DESCRIPTION: Admin should able to login successfully and access
admin panel.
PRE-CONDITION: Admin should have a valid username and password
provided by developers.
ASSUMPTION: A supported browser is being used.
TEST STEPS:
1) Navigate to www.h2htech.in/index.php.
1) In the field of username enter the valid username provided by
developers.
2) In the field of password enter the valid password provided by
developers.
3) Click submit button.
EXPECTED RESULTS: If username and password are correct then
admin will be redirected to admin dashboard from where he will able to
perform all the operations.
TITLE: Operator Request Form – Sends Request to manager
successfully. (Fig (I))
DESCRIPTION: After login operator can fill the form and send the
guests request to the concerned department.
PRE-CONDITION: Operator should enter the room-no, request of guest
and other details.
TEST STEPS:
1)Navigate to www.h2htech.in/operator_requestform.php
2)In the field enter the details required and click on submit button.
EXPECTED RESULTS: If all the details are proper and is validated then
the form is submitted and the request is notified to the concerned
department through mobile application.

TITLE: Manager Assign Form –Assigns request to the Associate. (Fig

(I))
DESCRIPTION: After login manager can access the functionality. From
request status he can view the new requests and can assign it to the
associate.
PRE-CONDITION: Manager should select the associate to whom the
request is to be assigned and the status of the request.
TEST STEPS:
1)Navigate to www.h2htech.in/manager _request_status.php
2)In the request status manager can view all the requests so he can click
on the assign button of the request that he wants to assign.
3)Redirected to the assign form.
4)Select the associate and the status of the request.
5)Click on Submit Button.
EXPECTED RESULTS: If the associate and status of request is selected
then the form is submitted and it is notified to the assigned associate
through mobile application.
TITLE: Manager Request Status –Displays all Request to the manager of

his department. (Fig (I))
DESCRIPTION: From request status he can view all the requests and can
assign and update the request. If the request is not complete in the priority
time then the request is escalated and is notified to the manager and if it is
escalated two or more times than it is notified to the manager and general
manager.
PRE-CONDITION: Manager should assign and update the request within
priority time.
TEST STEPS:
1)Navigate to www.h2htech.in/manager _request_status.php

2)In the request status manager can view all the requests if he wants to
assign he can click on assign button and if the wants to update he can
click on update button.
3)Assign or Update the request
4)Click on Submit Button.
EXPECTED RESULTS: If the request is assigned and updated and is

completed within the priority time then it is not escalated but if it is not
completed than it is escalated and is being notified to the manager.
So, we have performed unit testing for all the modules like admin login
fig (I), login of operator, manager and user fig (XI, XX,XXXIII)
respectively, guest complain form fig (XIII), associate complain form
fig (XIV) and many more.
Basically, we have tested each and every unit of our software to make it
efficient.

INTEGRATION TESTING
Testing of integrated modules to verify combined functionality after
integration.
TITLE: Login Page – Authenticates operator, manager associate, general

manager, management. (Fig (XI, XX, XXXIII))
DESCRIPTION: As we have integrated operator, manager and user
which can be accessed from a single login page.
PRE-CONDITION: Operator, manager and user have a valid username
and password provided by admin.
ASSUMPATION: A supported browser is being used.
TEST STEPS:
1) Navigate to www.h2htech.in.
2) In the field of username enter valid username provided by admin.
3) In the field of password enter valid password provided by admin.
EXPECTED RESULT: If username and password of operator are
matched operator panel is opened. If username and password of manager
are matched then manager panel is opened. If username and password of
user are matched then associate panel is opened.
TITLE: – Authenticates operator, manager associate, general manager,

management. (Fig (XI, XX, XXXIII))
DESCRIPTION: As we have integrated operator, manager and user
which can be accessed from a single login page.
PRE-CONDITION: Operator, manager and user have a valid username
and password provided by admin.
ASSUMPATION: A supported browser is being used.
TEST STEPS:
3) In the field of username enter valid username provided by admin.
4) In the field of password enter valid password provided by admin.

EXPECTED RESULT: If username and password of operator are

matched operator panel is opened. If username and password of manager
are matched then manager panel is opened. If username and password of
user are matched then user panel is opened.
We have integrated our whole software with help of login form through
which operator panel, manager panel and user panel can be accessed as in
fig (XII, XXI, XXXIV) respectively.
Integration testing helps in binding whole software and even giving ease
of access to users.
We have also integrated all the forms and logs with each other to give
user a user friendly system.
He can access anything through navigation bar which is always there on
left side and will able to do his task quickly.

FUNCTIONAL TESTING
Functional testing focuses on the output i.e. it checks whether the output
is as per requirement or not. This testing ignores the internal parts.
This is a black box type testing geared to functional requirements of
software.
TITLE: Request Form – Operator fills the form. (Fig (XIII))

DESCRIPTION: Here, operator fills request form whenever request
comes from guest and request needs to handled.
PRE-CONDITION: It’s must that operator has received a call from guest
or from associate.
ASSUMPTION: Operator is already login.
TEST STEPS:
1) Select request form from navigation bar.
2) Fill all the required details according to specifications.
EXPECTED RESULT: Request is being notified to the manager of the

concerned department and the manager has to assign and update the
status and has to complete the request within the priority time.
TITLE: Query Form – Operator, Manager, Associate, General Manager,

and Management fills the form. (Fig (XIII))
DESCRIPTION: Here, all the users can fill the form whenever they want
send a query to other department.
PRE-CONDITION: It’s must that they have a query for another
department.
ASSUMPTION: All users are already login.
TEST STEPS:
1) Select query form from navigation bar.
2) Fill all the required details according to specifications.

EXPECTED RESULT: Query is being notified to the manager of the

concerned department and the manager has to assign and update the
status of the query.
So, functional testing is tested upon request from fig (XIII), assign form
fig (XIII), update form fig (XIII), query form fig (XXVII) and many
more.

SYSTEM TESTING
Entire system is tested as per the requirements. This type of testing is
based on overall requirements specifications and covers all combined
parts of a system.
TITLE: Whole software – All the modules of the system are being tested.
DESCRIPTION: Tester tests the whole system to check bugs and errors
in the system which can be solved to prevent mishaps.
PRE-CONDITION: System must be fully integrated and connected.
ASSUMPTION: A supported browser must be used.
TEST STEPS:
2) Login to any of the user account i.e. operator, manager, associate,
general manager, or management.
3) Can view the dashboard of their respective panels
4) Can perform any of the operations from navigation bar.
EXPECTED RESULT: There will be output for every input in the system
and it can be in operator, manager, associate, general manager, or
management.
In system testing, the whole system is tested as a whole rather than the
individual units. System testing is done only after whole system is
integrated.
This testing will provide us with the bugs and errors of the system rather
than the error we get while coding.
System testing also helps in checking how secure the software is and
whether the data entered is encrypted or protected or not.

END- TO-END TESTING

This testing involves testing of complete software in a situation that
mimics real-world use.
It involves interaction with database, using network communications,
interactions with hardware, etc.
TITLE: Complete software – Software as whole is tested.

DESCRIPTION: Here, the software is tested in real world with real
entities and database.
PRE-CONDITION: The software should be hosted in live environment.
ASSUMPTION: A supported browser must be used.
TEST STEPS:
1) Host the web application.
2) Test whole application in various aspects by one being admin,
other being operator, third person being manager, fourth being
associate, fifth being general manager, and sixth being
management.
EXPECTED RESULT: The application must be easy to use and perform
all the functions as specified.
End-to-end testing is testing of software in live environment which will

help in giving us insights of how the software works in real environment
and it also helps in knowing the changes which is required by user who
are going to use it.
This testing helps in finding bugs and error in real environment which
may damage the system in long term.
So, after hosting the application this test is done for improvements and is
also made ready for implementation.

ACCEPTANCE TESTING
Acceptance testing is done to verify if system meets the customer
specified requirements.
Clients do this testing to determine whether to accept software or not.
TITLE: Whole software.

DESCRIPTION: The client will test the whole software.
PRE-CONDITION: The software must specify all the requirements of
client.
ASSUMPTION: A supported browser to run the software.
TEST STEPS:
1) Clients will understand the whole software.
2) Then they will see a demo of software.
3) They will see whether the requirements they specified are fulfilled
or not.
EXPPECTED RESULT: The client accepts the software and asks for
some changes and agrees for implementation.
Acceptance testing helps the client to know whether the stated

requirements are fulfilled or not. It also helps the developer to know if he
clients require any changes before actual implementation.
In this testing the developer needs to give client the knowledge of whole
software in simpler terms. They also need to make them understand all
the features of software.
This test is very crucial because it will only lead in implementation if the
client is satisfied with software.

LOAD TESTING
Load testing comes under performance testing to check system behaviour
under load.
Testing the software under heavy loads, such as testing of a website under
a range of loads to determine at what point the system’s response time
fails.
STRESS TESTING
System is stressed beyond it’s specification to check how and when it
fails.
Performed under heavy load like putting large number beyond storage
capacity, complex database queries, continuous input to system and
database load.
PERFORMANCE TESTING
Term often used interchangeably with stress and load testing.
To check whether system meets performance requirements by using
different performance and load tools.
USABILITY TESTING
Whether the software is user-friendly or not is checked here.
Application flow is tested, can new user understand the application easily,
proper help documented whenever user is stuck at any point.
Basically, system navigation is checked here.
UI TESTING
UI testing involves testing the GUI of software.
UI testing ensures that the GUI functions according to the requirements
and are tested in terms of colour, alignment, size and other properties.

SECURITY TESTING
Can system be penetrated by any hacking now. Testing how well the
system protects against unauthorised internal or external access.
Check if system database is safe or not.
COMPATIBILITY TESTING
Testing how well software performs in particular hardware, software
operating system, network environment and different combinations.
ALPHA TESTING
In house virtual user environment can be created for this type of testing.
Testing is done at the end of development. Still minor design changes
may be made as a result of such testing.
BETA TESTING
Testing typically done by end-users or others.
Final testing before releasing application for commercial purpose.

LIMITATIONS AND FUTURE ENHANCEMENTS
LIMITATIONS
- Internet connection is must for working on this software.
- MySql is necessary for managing the big data and as we will

receive minimum 50-100 requests daily it will be a necessity to
have a big data.
- Our software is not connected to opera so, operator will have to fill
more field manually.
- Guests cannot able to register request by themselves, they have to

call AYS.
- Guests cannot see status of their request. Guests has call at AYS to
check status.
- This web application requires smartphone only. It can’t work on

black and white phones.
- Manager has to select property every time to change property.

FUTURE ENHANCEMENTS
- An interface with PMS (Property Management Software) to get the
details of guest directly into the system.
- Create API that can able to fetch information of guest from opera.
- Create Application that can run on (tizen os) hospitality TV. So,
that guest can register request and also check status of request from
TV.
- By getting location of device, by default manager is redirected to

that property.

CONCLUSION
Hotel Management System is an industry which is the significant industry

since several decades. We tried to ease their work by providing them with
the software of communication system.
The communication software we provided them may ease their work out
and also help in effective completion of request by guest. We also hope
that through this the communication gap between departments also
reduces.
We have tried to fulfil all the requirements of the client and provide them
with the best possible solutions for their challenges they are facing since
many years.
It is totally dynamic software which will provide them with many
benefits which they were not able to get before in their traditional file
maintaining system.
We have provided them with facilities like notifications for quick access
to complains, shortcuts for quick navigation, diagrammatical
representation of completed complains, checking of logs, status update,
assigning the requests and query to particular employee, priority of
complains with escalation when the time completes, generation of
meaningful and understandable reports, extraction of reports, and many
more.
So, we hope that we have provided them with all the facilities as per their
requirements and have provided them with the best possible software and
it might help in making their day-to-day transitions easily.
Documenting software is extremely important. We can use
documentation to communicate with stakeholders about an evolving
system.
Documentation is also useful for enabling new team members to get on
board quickly, because they can use the architecture perspectives as a
contextual and bounding premise while implementing a solution.

BIBLIOGRAPHY
http://stackoverflow.com/questions/7005808/set-session-expiration-time-
11manually-codeigniter
https://github.com/ronan-gloo/codeigniter-highcharts-
library/blob/master/controllers/charts.php
https://forums.phpfreaks.com/topic/268967-getting-the-current-date-and-
time-in-php /
https://www.tutorialspoint.com/codeigniter/working_with_database.htm
https://www.formget.com/codeigniter-tutorial/
https://www.formget.com/pagination-in-php /
http://stackoverflow.com/questions/21389164/how-can-i-get-radio-
button-values-from-php -form-into-controller
http://stackoverflow.com/questions/3041616/creating-foreach-loops-
using-php -controller-and-view
https://www.tutorialspoint.com/php/
http://stackoverflow.com/questions/21389164/generate-random-
passowordr
https://forums.phpfreaks.com/topic/268967-getting-the-current-date-and-
time-in-php/
https://www.tutorialspoint.com/codeigniter/working_with_database.htm
https://stackoverflow.com/questions/1658443/can-php-scripts-continue-
to-run-even-if-the-user-closed-the-browser
http://programmerblog.net/jquery-ajax-get-example-php-mysql/

LEARNING OUTCOMES
- I learnt how to communicate with clients and know their requirements.
- I learnt how to filter out the requirements of clients and focus on the
main requirement and provide the solution of same to them.
- I learnt how to get ideas through brain storming session and choose
the best one to work upon.
- I also learnt how to work in team and reduce the communication gap
among team members.
- I learnt how to complete the daily tasks given by mentor and report to
mentor about same.
- I learnt how to present the software to client and make them

understand the significance about the same.
- Our group tried to create a benchmark for juniors so that they can
follow our steps and make an efficient project of their own.
- I learnt to create requirement specification study and accordingly work

upon it.
- Even learnt how to make significant system design which will help in
designing our software.
- I learnt how to change the system design according to the changes in

software
- I learnt and did lot of research on php for the software.
- As the deadlines were specified an insight on how to meet them and

complete the assigned task on time.
- I learnt how to debug and solve the errors in our project to make it
efficient.

- The application is made attractive and as per the requirements of

professionals.
- Code ignite was selected because it is secured and all the data is
passed in encrypted form.
- I also learnt how to host the web application by getting a domain.
- The web application is made platform independent to give user ease in

access.
- As a team we tried to divide our software in small modules and

divided them amongst ourselves.
- As a group we worked together efficiently and made our software

user-friendly.
- Learnt how to integrate all the modules as one and make one system
out of it.
- I learnt to help our team members when needed and always be

together in any circumstances and faced all the challenges and
overcome them.
- The software was tested in various circumstances and solved all the
bugs and errors which came while testing.
- The software was tested in live environment with live data to get the
insight of working of software in this environment.
- I learnt how to convince and make client understand the significance

of software.

Happy To HRLP

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Happy To HRLP

Uploaded by

Copyright:

Available Formats

AURO UNIVERSITY, SURAT.

GUJARAT JHM HOTELS LTD.

BATCH 2015 –‘18

BSc. IT SEMESTER VI PROJECT REPORT

GUJARAT JHM HOTELS LTD.

BATCH 2015 –‘18

BSc. IT SEMESTER VI PROJECT REPORT

GUJARAT JHM HOTELS LTD.

BATCH 2015 –‘18

BSc. IT SEMESTER VI PROJECT REPORT

GUJARAT JHM HOTELS LTD.

BATCH 2015 –‘18

BSc. IT SEMESTER VI PROJECT REPORT

I, Harshil Vanani hereby declare that project entitled H 2 H

BSc. IT SEMESTER VI PROJECT REPORT

SCHOOL OF INFORMATION TECHNOLOGY

Date: 8th May, 2018

(Dr. Sharad Raghuvansh)

BSc. IT SEMESTER VI PROJECT REPORT

This project consumed huge amount of work, research and dedication.

BSc. IT SEMESTER VI PROJECT REPORT

Sr. No. Particulars Page No.

3. Objective of the Software 6

8. Testing and Implementation 97 – 106

9. Limitations and Future Enhancements 107

10. Conclusion 108

11. Bibliography 109

12. Learning Outcomes 110 – 111

BSc. IT SEMESTER VI PROJECT REPORT

Our software H2H i.e. Happy 2 Help is communication software mainly

BSc. IT SEMESTER VI PROJECT REPORT

2.1 BUSINESS REQUIREMENT SPECIFICATION (BRS)

BSc. IT SEMESTER VI PROJECT REPORT

3) FOOD AND BEVERAGES

4) SALES AND MARKETING

BSc. IT SEMESTER VI PROJECT REPORT

10) PURCHASES AND STORES

11) SPA AND GYM

BSc. IT SEMESTER VI PROJECT REPORT

2.2 SYSTEM REQUIREMENT SPECIFICATION (SRS)

BSc. IT SEMESTER VI PROJECT REPORT

The main objective of this document is to illustrate the requirements of

BSc. IT SEMESTER VI PROJECT REPORT

- Then created a quick preliminary design and worked upon it.

- Built a prototype for new system, constructed from preliminary

- The clients evaluate the first prototype provided by us, while

- Initial prototype is modified based on evaluation done by clients

- Again prototype is designed and evaluated and given for evaluation

- After the product is achieved it is tested and implemented in the

BSc. IT SEMESTER VI PROJECT REPORT

5.1 FLOW CHART

BSc. IT SEMESTER VI PROJECT REPORT

d. Else no data matches, Invalid user.

BSc. IT SEMESTER VI PROJECT REPORT

STEP 10: Query Log.

BSc. IT SEMESTER VI PROJECT REPORT

STEP 10: View Query Log.

BSc. IT SEMESTER VI PROJECT REPORT

BSc. IT SEMESTER VI PROJECT REPORT

5.2 DATA FLOW DIAGRAM (DFD)

BSc. IT SEMESTER VI PROJECT REPORT

BSc. IT SEMESTER VI PROJECT REPORT

PROCESS 10.0 MANAGE REQUEST –