Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

booking clarification in URLyBird

 
Vrinda Werdel
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I am doing the URLyBird assignment. As part of the room booking
1.I am updting the 'Customer' field in the fb file.
2. In order to avoid rebooking of an already booked room, I make the the alerady booked record uneditable. In this case 'Customer' cell will not editable since it already has a value.
3.In all other cases where 'Customer' field has no values, I make the cell editable. (all the above steps also take in to consideration the 48 hour rule.).

Is this acceptable?

regards

Vrinda
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 11945
212
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Vrinda,

This sounds acceptable.

Does this imply that a user could book several rooms at once?

Regards, Andrew
 
Vrinda Werdel
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Andrew,

I hope by user you mean CSR. The CSR will be allowed to book only one room at a time. meaning only one row will be allowed to be updated from the the GUI (and all the way down to the DB layer.) I was thinking of

1. making 'Customer' the cell uneditable to prevent accidental rebookings.

2. But now I am thinking of not doing it and documenting the same by saying that the "Booking Feature(button) can be used for 'Booking', 'Unbooking' (by setting 'Customer' to blank), Rebooking (by setting the 'Customer' to a different value) a room.".

Do you think this is reasonable?

regards

Vrinda
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 11945
212
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Vrinda,

Others have passed using similar strategies, so it should be ok.

I think you need to explain clearly in your design decisions document why you are allowing unbookings / rebookings, especially since these are mentioned in the Sun instructions.

Good luck in finding the word to put on your button - perhaps "Save" or "Update"? "Book" doesnt really make sense, as you are allowing far more than just bookings.

Regards, Andrew
 
Vrinda Werdel
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Andrew. I will need come up with some other name as you rightly pointed out.

regards

Vrinda
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic