Wk 3(after pract)

Our user interface was completed over the weekend... showed in to Mr.chew... Seems like we have progressed.. BUT... in the wrong direction... the UI is more to the web-design based... however we were suppose to do it the client-server way...We're not so sure about the client-server but we are looking into it this week....


Improvements suggested
1. make full use of the page/templete
2.Admin cus- to add No.of guest field
3.Syncronise the buttons(to make it look more client-server)
4.Link up wanni's application to my application(thana)
- being able to check room properties while being in the reserve room
- being able to reserve room from the administrate room
5.make full use of the UI objects in eclipse
6.try to avoid paging style
7.Reserve room
- add credit card update
- add type of reservation(fax,call)
8.Check In/Check Out
- add check out charges
- itemise checking out
- billing info


New task
-To start on Use Case description
-To draw out the use case diagram
-To write the basic flow and alternate flow



-Documented by Thana-

26 April 2008

Joseph - completed the UI for checkIn, checkOut, checkInConfirmation & checkOutConfirmation

thana will be doing the linking up of all from the main window =]

Zhng Your AdminCustomer

AdminCustomer v1.0:

-Currently have five pages: MainCust, CreateCust, UpdateCust, HistoryCust, ResortPass.

MainCust:

-3 buttons: CreateCust button, UpdateCust button, Home button.

CreateCust:

-Consists of salutation, first name, last name, Gender, email, passport ID, country, phone, address, postal code, VIP code, credit card brand, credit card number, credit card expiry date.

-3 buttons: Submit button, Reset button, MainCust button.

-Once information submitted successfully, ResortPass window pops up.

UpdateCust:

-Consists of salutation, first name, last name, Gender, email, passport ID, country, phone, address, postal code, VIP code, credit card brand, credit card number, credit card expiry date, resort pass.

-3 buttons: History button, Get button, MainCust button.

-History button links to HistoryCust which shows customer's past reservations.

-Get button to retrieve data from the database with resort pass as primary key.

HistoryCust:

-Shows a table that has data about customer's past reservations.

-A Back button that takes user back to UpdateCust.

ResortPass:

-Displays the resort pass which is randomly generated and unique for every customer.

-A OK button that takes user to the Homepage.

I make this like dota map log lol. Anyway, for the HistoryCust table, its not completed yet cos i not sure how to do.

WANNI!!

wanni - add in more things like number of extra beds, special request, flight information and payment mode .. flight information is bcoz i believe that seldom got locals wanna book the hotel in their own country, only when like got fireworks to see and stuff then people will book the hotel for a night..so i feel that most ppl who booked/stayed in the hotel are from overseas.. they can book the room themselves or their friends book for them or perhaps those local tour grp book the rooms for their customers.

flight information - collect the flight number(arrival or departure) and the time of the flight(arrival or departure) as the customer confirm the booking with us, we will send our ppl over to the airport to pick them up when they reach sg, we will also send them off to the airport when they are leaving sg..
this flight information don't need to key in the date of arrival n leaving bcoz i assume tat the customer is staying wif us once they reach sg till they are leaving sg..

payment mode is only for credit card bcoz for nets n cash we don need their records..

thats all.. will elaborate more when i see you ppl in sch... if theres anything you all don uds, feel free to give me a call and ask.. =)

cheers, wanni

24 April 2008

Wanni:
Reservation Room
- check out others online hotel reservation format / layout.
- is my current layout enough??