RESERVATION SYSTEM

Lough Uisce Lodge Reservation System

Lough Uisce Lodge Reservation System

This paper explores the concept of designing Use Case diagram, Activity, Sequence & behaviour diagram in relation to SDLC for the Lough Uisce Lodge Reservation System. Lough Uisce Lodge is a 50 bed resort hotel on the shores of Lough Uisce, in the Sierra Comeragh Mountains.

a)

The general requirements for a new customer are: in order for the customer to make a reservation they need a first and last name, valid address, credit card number, and phone number. They will be informed about the two towers we have, the different room types available, and the prices for each of the room types. Then the customer can make an informed decision in what they want. (Bennett 2005: 164-169)After the reservation is complete the hotel database will assign a customer ID number to the new customer. But as far as the customer is concerned they are simply given a confirmation number for their reservation, which they present upon arrival. If the customer is a returning guest and wants to make a reservation all their information is already in the database. Therefore, all they need to present is the arrival and departure dates and the room type they want. In return we give them the price and a confirmation number, which again they present upon arrival. (Cimino 2006: 273- 284)

Use case 1: Make a Reservation

Actor(s): Hotel Employees, Administrators

Description: Employee/Admin will be prompted with menu screen. After choosing “Employee” and “Make a Reservation”, they will enter in the Customer ID Number. (Note: If it is a new customer, they must enter in the Customer Information before making a reservation - see Use Case: Add a Customer). The screen should populate the customer's first and last name, address, phone number, and credit card information. Employee must enter in the date of arrival and departure, tower choice, and room type. The room number will be populated by availability, so they may choose any room number in the list. After clicking button “Reserve Room Now”, a confirmation number will be created. (Hogan 2006: 517-521)

Use case 2: Add a Customer

Actor(s): Hotel Employees, Administrators

Description: Employee/Admin will be prompted with menu screen. After choosing “Employee” and “Add a Customer”, they will enter in the first and last name, address, city, state, zip code, phone number, and credit card information. After clicking button “Add Customer Now”, a customer ID number will be created.

Use case 3: Cancel a Reservation

Actor(s): Hotel Employees, Administrators

Description: Employee/Admin will be prompted with menu screen. After choosing “Employee” and “Cancel a Reservation”, they will enter in the confirmation number. After clicking button “Cancel Reservation Now”, a cancellation number/date will be created.

Use case 4: Change Floor Smoking/Non Smoking Status

Actor(s): Administrators

Description: Administrators will be prompted with menu screen. After choosing “Administrators”, and “Change Floor Status”, they will select the floor to change and enter in either S or NS. After clicking button “Change Floor Status”, the floor will be changed to new ...