MEHRAN UNIVERSITY OF ENGINEERING & TECHNOLOGY

JAMSHORO
DEPARTMENT OF COMPUTER SYSTEMS ENGINEERING

DATABASE MANAGEMENT SYSTEM

“HOTEL RESERVATION
SYSTEM”
GROUP MEMBERS
• FAIZAN SHAIKH 21CS07

• Sarwaich Ahmed 21CS69

• Junaid Ahmed 21CS115

SUBMITTED TO
DR. ZARTASHA BALOCH

APRIL 2024
 Department of Computer Systems Engineering
Mehran University of Engineering and Technology, Jamshoro

Course: Database Management Systems (CS-353)

Assignment Complex Engineering
Instructor Dr. Zartasha Baloch Type Problem
Semester 5th Year 3rd
Submission Assessment
01-03-24 10
Deadline Score
Complex Engineering Problem - Characteristics
1 Depth of knowledge Required 
2 Range of Conflicting Requirements 
3 Depth of Analysis Required 
4 Infrequently Encountered Issues Involved 
5 Beyond codes/standards of practice 
6 Diverse groups of stakeholders with widely varying needs involved 
Interdependence (high-level problems including many component
7 
parts/sub-problems)
8 Have significant consequences in a range of contexts 
9 Judgment (Require judgment in decision making) 

Problem Description
Choose a real-world problem, draw the ER Diagram, apply ER-mapping rules to convert it
into the relational model, normalize the relations, and follow the application
development process. Make sure that the application should have five or more tables,
using a suitable front-end tool. Application areas may include but are not limited to;
health care, education, industry, transport, supply chain, business, human resource
management, manufacturing, etc. Marking will be done on the following parameters:
1. Problem identification
2. ER Diagram
3. ER Mapping
4. Normalization
5. Implementation
 Assessment
Unaccept Poo Acceptabl Adequat Proficient
Rubrics Marks
able (0) r e (5) e (8) (10)
(2)
R1 Identification of
constraints/requirements/dema     
nds/ research gap or challenges
well defined

R2 Engineering knowledge     
(standards)

R3 Efficiency of the solution     

R4 Technical Writing     
Total Marks

1. Problem identification

The Hotel Management System (HMS) project aims to develop a

comprehensive database management system to streamline hotel
operations, including reservation management, room allocation, billing,
and reporting. The system seeks to enhance efficiency, improve guest
experience, and facilitate better decision-making for hotel management.

2. ER Diagram
 3. Implementation
Tools:
• HTML/CSS/JS
• PHP
• SQL
• XAMPP
Queries:
-- Table structure for table `contact`

CREATE TABLE IF NOT EXISTS `contact` (

`id` int(10) unsigned NOT NULL,
`fullname` varchar(100) DEFAULT NULL,
`phoneno` int(10) DEFAULT NULL,
`email` text,
`cdate` date DEFAULT NULL,
`approval` varchar(12) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table `login`
--

CREATE TABLE IF NOT EXISTS `login` (

`id` int(10) unsigned NOT NULL,
`usname` varchar(30) DEFAULT NULL,
`pass` varchar(30) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=3 ;

--
-- Dumping data for table `login`
--

INSERT INTO `login` (`id`, `usname`, `pass`) VALUES

(1, 'Admin', '1234'),
(2, 'Prasath', '12345');

-- --------------------------------------------------------

--
-- Table structure for table `newsletterlog`
--

CREATE TABLE IF NOT EXISTS `newsletterlog` (

`id` int(10) unsigned NOT NULL,
`title` varchar(52) DEFAULT NULL,
`subject` varchar(100) DEFAULT NULL,
`news` text
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

-- --------------------------------------------------------

--
-- Table structure for table `payment`
--
-- Table structure for table `payment`
--

CREATE TABLE IF NOT EXISTS `payment` (

`id` int(11) DEFAULT NULL,
`title` varchar(5) DEFAULT NULL,
`fname` varchar(30) DEFAULT NULL,
`lname` varchar(30) DEFAULT NULL,
`troom` varchar(30) DEFAULT NULL,
`tbed` varchar(30) DEFAULT NULL,
`nroom` int(11) DEFAULT NULL,
`cin` date DEFAULT NULL,
`cout` date DEFAULT NULL,
`ttot` double(8,2) DEFAULT NULL,
`fintot` double(8,2) DEFAULT NULL,
`mepr` double(8,2) DEFAULT NULL,
`meal` varchar(30) DEFAULT NULL,
`btot` double(8,2) DEFAULT NULL,
`noofdays` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

-- --------------------------------------------------------

--
-- Table structure for table `room`
--

CREATE TABLE IF NOT EXISTS `room` (

`id` int(10) unsigned NOT NULL,
`type` varchar(15) DEFAULT NULL,
`bedding` varchar(10) DEFAULT NULL,
`place` varchar(10) DEFAULT NULL,
`cusid` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=16 ;

--
-- Dumping data for table `room`
--

INSERT INTO `room` (`id`, `type`, `bedding`, `place`, `cusid`) VALUES

(1, 'Superior Room', 'Single', 'Free', NULL),
(2, 'Superior Room', 'Double', 'Free', NULL),
(3, 'Superior Room', 'Triple', 'Free', NULL),
(4, 'Single Room', 'Quad', 'Free', NULL),
(5, 'Superior Room', 'Quad', 'Free', NULL),
(6, 'Deluxe Room', 'Single', 'Free', NULL),
(7, 'Deluxe Room', 'Double', 'Free', NULL),
(8, 'Deluxe Room', 'Triple', 'Free', NULL),
(9, 'Deluxe Room', 'Quad', 'Free', NULL),
(10, 'Guest House', 'Single', 'Free', NULL),
(10, 'Guest House', 'Single', 'Free', NULL),
(11, 'Guest House', 'Double', 'Free', NULL),
(12, 'Guest House', 'Quad', 'Free', NULL),
(13, 'Single Room', 'Single', 'Free', NULL),
(14, 'Single Room', 'Double', 'Free', NULL),
(15, 'Single Room', 'Triple', 'Free', NULL);

-- --------------------------------------------------------

--
-- Table structure for table `roombook`
--

CREATE TABLE IF NOT EXISTS `roombook` (

`id` int(10) unsigned NOT NULL,
`Title` varchar(5) DEFAULT NULL,
`FName` text,
`LName` text,
`Email` varchar(50) DEFAULT NULL,
`National` varchar(30) DEFAULT NULL,
`Country` varchar(30) DEFAULT NULL,
`Phone` text,
`TRoom` varchar(20) DEFAULT NULL,
`Bed` varchar(10) DEFAULT NULL,
`NRoom` varchar(2) DEFAULT NULL,
`Meal` varchar(15) DEFAULT NULL,
`cin` date DEFAULT NULL,
`cout` date DEFAULT NULL,
`stat` varchar(15) DEFAULT NULL,
`nodays` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

--
-- Indexes for dumped tables
--

--
-- Indexes for table `contact`
--
ALTER TABLE `contact`
ADD PRIMARY KEY (`id`);

--
-- Indexes for table `login`
--
ALTER TABLE `login`
ADD PRIMARY KEY (`id`);

--
-- Indexes for table `newsletterlog`
--
ALTER TABLE `newsletterlog`
ADD PRIMARY KEY (`id`);

--
-- Indexes for table `room`
--
ALTER TABLE `room`
ADD PRIMARY KEY (`id`);

--
-- Indexes for table `roombook`
--
ALTER TABLE `roombook`
ADD PRIMARY KEY (`id`);

--
-- AUTO_INCREMENT for dumped tables
--

--
-- AUTO_INCREMENT for table `contact`
--
ALTER TABLE `contact`
MODIFY `id` int(10) unsigned NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `login`
--
ALTER TABLE `login`
MODIFY `id` int(10) unsigned NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=3;
--
-- AUTO_INCREMENT for table `newsletterlog`
--
ALTER TABLE `newsletterlog`
MODIFY `id` int(10) unsigned NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `room`
--
ALTER TABLE `room`
MODIFY `id` int(10) unsigned NOT NULL AUTO_INCREMENT,AUTO_INCREMENT=16;
Interface:
Admin’s view:
Admin's View contains all entities, and performs all the functions like insert, update,
delete on all tables.
Features:
Key features of the Hotel Management System include:
Reservation Management: Allows staff to create, modify, and cancel
reservations.

Room Allocation: Automatically assigns rooms based on availability

and guest preferences.

Billing: Generates invoices, tracks payments, and manages accounts

receivable.

Reporting: Provides comprehensive reports on occupancy rates,

revenue, and guest demographics.

CUSTOMERS’S Interface:
 Conclusion:

In conclusion, the hotel reservation system project provides a modern solution for managing hotel

bookings efficiently. It benefits both customers and hotel administrators by simplifying the

reservation process and improving overall customer experience. The system can be further

enhanced with additional features and integrations to meet evolving industry requirements.
 Rubrics

Unacceptab Poor Acceptabl Adequate Proficient Sc

le e or
e
R1 Problem Problem Problem Problem is Problem is
Problem/Requirem not poorly is defined identified
ent Identification identified identified identified adequately. and
analyzed in
a well-
defined
manner.
Can not Has Correctly Correctly Correctly
R2 Engineering apply difficulty applies applies applies
knowledge engineering applying basic engineering engineering
(standards) knowledge mathemati sciences to fundamental specializatio
to the cs to the s to the n to the
solution. the solution solution of solution of
solution of complex complex complex
of complex engineerin engineering engineering
engineerin g problems problems.
g problems
problems
Solution A difficult A logical Solution is Solution is
R3 Efficiency of the does not and solution adequately efficient,
solution meet inefficient that is efficient. easy to
requireme solution. easy to understand
nts. follow , and
but it is maintain.
not the
most
efficient.
R4 Technical The report The report The Reports Reports
Writing is submitted requireme meets all meets all
submitted but not nts of prescribed requireme
but lacks according report requireme nts, and it
solutions to to the writing nts. is prepared
requireme are not
major in original
nts. properly
requireme addressed. and
nts. corrective
way to
engage
readers.