You are on page 1of 11

Hotel Management System HMS full database project using ASP.

Net C#, SQL Server Source Code with detail Database Design article and Explanation of Entity relationship diagram

This system involves the management of small and medium sized hotel properties. It will allow check-ins, check-outs, reservations, employee information handling, product and supplier information handling. A user accesses the system by entering his/her user name and password which were previously defined by the hotel owner/manager. The clerk uses the system through a Graphical User Interface (GUI).

Source Code Link here

• A computer based management system is designed to handle all the primary information required to calculate monthly statements. • Separate database is maintained to handle all the details required for the correct statement calculation and generation. • This project intends to introduce more user friendliness in the various activities such as record updation, maintenance, and searching.

4. Storing employee information. Keep track of accounts payable and receivable. 7. • The entire information has been maintained in the database and whoever wants to retrieve can’t retrieve it. Room activities. 2. Admission of a New Customer. Storing information of suppliers and products. 6. Checkout of a customer. • All the records are absolutely up-to-date.• The searching of record has been made quite simple as all the details of an employee can be obtained by simply keying in the identification of that employee. 5. • The main objective of the entire activity is to automate the process of day to day activities of Hotel like: 1. only authorized user can retrieve the necessary information which can be easily be accessible from the file. Assign a room according to customer’s demand. Some other objectives are: • No data duplication • No Paper Work Required • Time Efficient • Cost Efficient • Automatic data validation • User friendly environment • Data security and reliability • Fast data insertion & retrieval • Easy performance check . 3.

could also be provided but we are not providing this yet. The facilities such as airline booking. Find all reservations by a customer. employee details. We are also not managing restaurants in this project. rent a car. accounts payable and receivable. Employee Management Module: This module allows to manage the employee information. edit an existing room. check out a customer. we will keep track of information of employees working in the hotel. It would allow to:    password verification. add a new employee. product details. Reservation Module: This module allows the employee to manage reservations. It would allow to:    make a new reservation(check in. edit an existing employee. System Module Room management Module: This module provides the management facility of rooms. view all rooms. In this project. gift shop etc. assuming that the customer makes the reservation at the same time he checks in). It would allow to:    add a new room. .The scope of our project "Hotel Management System” is that it could be given to any small/medium sized hotel so that they can maintain their room reservations.

edit an existing employee. Product Management Module: This module keeps track of inventory. the amount receivable by accounts receivable ID. edit an existing product. Product management module and Reservation module. edit an existing supplier. edit an existing room. Users/Roles of the System Manager: The manager would have special privileges. It would allow to:     add a new supplier. the amount receivable by reservationID. edit an existing product. different views for receptionist and manager. add a new product. Accounting Module: This module keeps track of all the accounting information regarding the hotel. Receptionist: The receptionist will have access to the Room management module. He will be able to: add a new employee. It would consist of:     view the amount payable by receipt number. add a new product. view the amount payable by supplier ID number. . He will be able to perform the following operations:       add a new room.

Maintenance: The maintenance would be responsible to maintain rooms. Forms and Reports         Reservation/Check in Check out Rooms Details (add and edit) Employee Details (add and edit) Product Details (add and edit) Supplier Details (add and edit) Accounts receivable Accounts payable Entity Relationship Diagram .  check in a customer. check out a customer.

.

Data Type and Domain int (4) varchar (100) varchar (100) int(10) int(11) Null Constraint Not Null Not Null Null Null Null Key Constraint Primary Key Application based Constraint Column Name Customer ID Name Address Phone Cell Table Name: EMPLOYEE Primary Key: Employee ID Purpose: To store the employee detail. Data Type and Domain int (4) Null Constraint Not Null Key Constraint Primary Key Application based Constraint Column Name Supplier ID .Tables Description Table Name: CUSTOMER Primary Key: Customer ID Purpose: To store the customer details. Data Type and Domain int (4) varchar (100) int (4) varchar (100) int(10) Null Constraint Not Null Not Null Not Null Not Null Not Null Key Constraint Primary Key Foreign Key Application based Constraint Column Name Employee ID Name Manager ID Address Phone Table Name: SUPPLIER Primary Key: Supplier ID Purpose: To store the information of each supplier.

Data Type and Domain int (4) varchar (100) varchar (100) int(10) varchar (100) long(8) Null Constraint Not Null Not Null Not Null Not Null Null Not Null Quantity not less then 0 or greater then 100.000 Key Constraint Primary Key Foreign Key Price not less then 0 or greater then 100. Data Type and Domain int (4) int (4) int (10) int (4) Null Constraint Not Null Not Null Not Null Not Null Key Constraint Primary Key Foreign Key Application based Constraint Column Name Room ID Manager ID Price Maintenance ID Foreign Key Table Name: ROOM-TYPE Primary Key: Room ID.000 Application based Constraint Column Name Product ID Name Supplier ID Price Description Quantity Table Name: ROOM Primary Key: Room ID Purpose: To store the information of each room. Room Type .Name Address Phone varchar (100) varchar (100) int(10) Not Null Null Null Table Name: PRODUCT Primary Key: Product ID Purpose: To store the information of each product.

Data Type and Domain int (4) varchar (100) Null Constraint Not Null Not Null Key Constraint Primary Key Primary Key Application based Constraint Column Name Room ID Room Type Table Name: RESERVATION Primary Key: Customer ID.Purpose: To store the room type against each room id. Data Type and Domain int (4) int (4) int (4) Date Date int(10) Null Constraint Not Null Not Null Not Null Not Null Not Null Not Null Key Constraint Primary Key Primary Key Foreign Key Application based Constraint Column Name Customer ID Room ID Employee ID Start Date End Date Charges Date must be in DD-MM-YYYY format Date must be in DD-MM-YYYY format Charges not less then 0 Table Name: Accounts Payable Primary Key: ID Purpose: To keep a record of the accounts payable. Data Type and Domain int (4) int (10) Date int (4) Null Constraint Not Null Not Null Not Null Not Null Foreign Key Key Constraint Primary Key Application based Constraint Column Name ID Amount Date EmployeeID Amount not less than 0 Date must be in DD-MM-YYYY format . Room ID Purpose: To store the reservation information.

Data Type and Domain int (4) int (4) Null Constraint Not Null Not Null Key Constraint Primary Key Primary Key Application based Constraint Column Name Room ID Product ID . Product ID Purpose: To keep a record of which product is used in which room. Data Type and Domain int (4) int (10) Date Null Constraint Not Null Not Null Not Null Key Constraint Primary Key Application based Constraint Column Name ID Amount Date Amount not less than 0 Date must be in DD-MM-YYYY format Table Name: SUPPLIER-PRODUCT Primary Key: Transaction ID. Product ID Purpose: To keep a record of which supplier supplies a product.Table Name: Accounts Receivable Primary Key: ID Purpose: To keep a record of the accounts receivable. Data Type and Domain int (4) int (4) int (4) Date int(10) Null Constraint Not Null Not Null Not Null Not Null Not Null Key Constraint Primary Key Primary Key Foreign Key Application based Constraint Column Name Transaction ID Product ID Supplier ID Date Amount Date must be in DD-MM-YYYY format Charges not less then 0 Table Name: ROOM-PRODUCT Primary Key: Room ID.