ANALYSIS (DFD, ERD DIGRAMS)

Principles Of System Analysis

1) Understand the problem before you begin to create the
analysis model.
2) Develop prototypes the enable a user to understand how
human machine interaction will occur.
3) Record the origin of and the reason for every requirement.
4) Use multiple views of requirement like building data,
function and behavioral models.
5) Work to eliminate ambiguity.

ENTITY RELATIONSHIP DIAGRAM

ER DIAGRAM
This ER-Diagram represents the model of hotel Management
System Entity. The entity relationship diagram of Hotel
management system shows all the visual instrument of
database tables and the relations between Rooms, Payment,
hotel, Customers etc. It used structure data and to define the
relationships between structured data groups of hotel
Management System functionalities. The main entities of the
Hotel Management System are Hotel, Rooms, Services,
Payments, Booking and Customers.
Hotel Managment System entities and attributes:
1) Hotel Entity: Attributes of Hotel are hotel_id, hotel _name,
hotel _type, hotel rent, hotel description, hotel address
2) Rooms Entity: Attributes of Rooms are roomie, room_
hotel_ id, room _no, room _category, room _type, room
_description
3) Services Entities: Attributes of services are service_ id,
service_ hotel_ id , service_ name, service_ type ,service_
description
4) Payments Entities: Attributes of payments are payments_
id,payments_customer_id,payments_date,payments_amoun
t,payments_description
5) Booking Entities: Attributes of booking are booking_id,
booking_ name, booking_ tittle, booking_ type, booking_
date, booking_ description
6)Customer Entity: Attributes of customer are
customer_id,customer_name,customer_mobile,customer_e
mail,customer_username,customer_password,customer_add
ress
 Description of Hotel Managment System
Database

1) The details of Hotel is store into the Hotel tables

respective with all tables.

2) Each entity (Customer, Service, Room, Booking, Hotel)

contains primary key and unique keys.

3) The entity services, Booking has binder with Hotel , Rooms

entities with foreign key.

4) There is one to one or one to many relationships available

between Booking, Payments, Customers, Hotel.
 Login_role_id
User_name
m
Login_id
User_password

Login
User_id

role_id

User_name Has
User Roles
s
role_name
User_email

role_decs
User_mobile

Manage

cus_name
hotl_name

customer permission

cus_id hotel

cus_pass per_module
cus_email has per_name

booking
per_id

book_id
d
book_desc
book_type