Monday, February 6, 2012

Make Hotel System With MS Access

  1. Intoduction hotel system.
  2. Creating a database. Construct a database that cor-responds to the data model behind the design. The user will only see the database indirectly - through the screens we construct.
  3. Access-based user interfaces. Construct the screens and menus that the user will see. We follow the pa-per-based mockup designed in User Interface De-sign. You can use the result as a tool-based mockup.
  4. Queries - computed tables. Connect the screens to the database, usually by means of queries - com-puted data tables. The result will be a partially functional prototype.
  5. Access through Visual Basic. Program what the buttons and menus will do when the user activates them. The result will be a fully functional prototype and later the final system to be delivered to the customer. The first part of the chapter is tutorial - mandatory reading if you want to work with Visual Basic and Access. The rest of the chapter is for looking up various subjects. We assume you know a bit of programming already.
  6. Visual Basic reference. A reference guide to the Visual Basic language for Applications (VBA).
  7. Access and SQL. An overview of the remaining parts of SQL, for instance how to update the database through SQL. We also explain how to generate matrices of data with dynamically chan-ging headings.


Step 1 Intoduction hotel system. 


In this section we illustrate MS-Access by means of asystem for supporting a hotel reception. The system is used as the main example in User Interface Design - a Software Engineering Perspective, by SorenLauesen.

Find guest.
The Find guest screen allows the recep-tionist to find a guest or a booking in the database. The receptionist may enter part of the guest name and click the Find guest button. The system then updates the lower part of the screen to show the guests or bookings that match. The receptionist may also find the guest by his phone number, room number, or stay number (also called booking number).
The receptionist can select the guest from the list and click the buttons to see details of the booking or create a new booking for the guest.
Room Selection.
The Room Selection screen gives an overview of available rooms in a certain period. Avail-ability is shown as IN when the room is occupied, BOO when it is booked, etc. The receptionist may specify the period of interest and the type of room, then click the Find room button. The system updates the ta-ble at the bottom of the screen to show the rooms of interest. The receptionist can then choose a room and book it for the guest – or check a guest into the room. 

Stay.
The Stay screen shows all the details of a book-ing, for instance the guest and his address, the rooms he has booked and the prices. When the guest is checked in, the Stay screen also shows breakfast and other services he has received. The system shows these details on the Services tab. Here the receptionist can record services that the guest has received. The system uses the term Stay to mean a booking or a guest who has checked in. 

Breakfast list.
The Breakfast screen shows the break-fast servings for a specific date. It handles just two kinds of breakfast: self-service breakfast in the restau-rant (buffet) and breakfast served in the room. The waiter in the restaurant has a paper copy of the list and records the servings here. Later the receptionist enters the data through the Breakfast screen. 

Service list.
The Service list shows the price for each kind of service. Hotel management uses this list to change service prices or add new kinds of service. 

Database
The system uses a database with several tables.
tblGuest has a record for each guest with his address and phone number.
tblStay has a record for each stay (booking or checked in) with a booking number (stay number) and the pay method.
tblRoom has a record for each room in the hotel.
tblRoomState has a record for each date where a room is occupied. It connects to the room occupied and the stay that occupies it. If the room is occupied for repair, it doesn’t connect to a stay.
tblRoomType has a record for each type of room (room class) with a short description of the room type, the number of beds, and the prices.
tblService has a record for each type of service with its name and price per unit.
tblServiceReceived has a record for each delivery of service to a guest. It connects to the type of service and to the stay where the service is charged (there is an in-voice for each stay). 

No comments:

Post a Comment