• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

book/release dilema - please help.

 
Mihai Radulescu
Ranch Hand
Posts: 918
IntelliJ IDE Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, Guys

I have a question about book/release mechanism.

In my specs I have something like :

CSRs know their customer ids. The system you are writing does not interact with these numbers, rather it simply records them. If this field is all blanks, t
he record is available for sale


I interpret this like book & release alters the owner field.
I must change the date field according to the release date ?

Regards M
 
Peter MacMillan
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why would the date the hotel room is available change when someone books or unbooks a room? The requirement is simply to put the customer number that the CSR provides into the owner field. An empty field means that the room is not booked and the customer numbers are just numbers.
 
Mihai Radulescu
Ranch Hand
Posts: 918
IntelliJ IDE Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, Peter

Thanx for your interest.

Let's consider the follow steps :
1.I book a record, so the owner field get changed here - the date can remains the same.
2.I release the record (now) -> becomes available from now ->the date field must get the date from now. Otherwise the date will remains always the old one a
d the record can be booked only with dates from the past.

Regards, Mihai
 
Peter MacMillan
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mihai Radulescu:

I release the record (now) -> becomes available from now ->the date field must get the date from now. Otherwise the date will remains always the old one and the record can be booked only with dates from the past.


Why would the date change because someone decided to cancel? What has led you to this non-sensical assumption?

If I book a room and then cancel, the date that the room is now available is the same date as it was before. If I were to book a seat on an airplane and then cancel, would the date of the flight change? no.

In any case, I don't think that cancellation is necessarily a use-case that you must implement.
 
Mihai Radulescu
Ranch Hand
Posts: 918
IntelliJ IDE Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, Peter

Is like this :
1.the client books the room (on 2001/01/02) uses the room until it goes(2001/01/10).
2.After this the room is available(we are on 2001/01/10) so the CRS will release the room.
3.Now the room is available(from 2001/01/10)

On the other side in my specs is nothing about the date for released record.
This mean that the "release" a booked record has only a cancel function for booking.

Regards, Mihai
 
Peter MacMillan
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator


1.the client books the room (on 2001/01/02) uses the room until it goes(2001/01/10).



If you got that from your spec, then we are working on completly different urlybird assignments.

The date, in the specs I recieved, is the single night that the room is available. The date represents the date that the room is available.



2.After this the room is available(we are on 2001/01/10) so the CRS will release the room.
3.Now the room is available(from 2001/01/10)



According to my specs this is irrelivant. The booking is for a specific date and is not a recurring use item (ie. we have no knowledge of the room's availability before or after the specified date).

But you'll need to make a judgement on your own because what you are describing is totally out of line with the specs that I have.
 
Mihai Radulescu
Ranch Hand
Posts: 918
IntelliJ IDE Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have also the single night stuff :

The single night to which this record relates, format is yyyy/mm/dd.


and


URLyBird is a broker of discount hotel rooms. They sell accomodations for business and pleasure travellers at short notice, helping hotels to fill rooms that would otherwise be left empty. They take bookings only within 48 hours of the start of room occupancy. Curently, URLyBird sells the rooms over the phone using a team of customer service representatives (CSRs). The CSRs interact with an aging custom-written application that has been drawing increasing criticism from the CSRs.


I think that we have similar assgnments.
I am confuse.
Correct my if I am wrong.
A room is available if : it has no owner and the its date falls in within the 48 H interval. Thas make the room available for two days.
So if I have an aviable room for date(yyyy/mm/dd) 2001/01/01 the room is aviable for the interval 2001/01/01-2001/01/03.
It does not meter how log the room remain booked.

Am I wrong ?

Thanks Mihai.
 
Peter MacMillan
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

A room is available if : it has no owner and the its date falls in within the 48 H interval.


yes


Thas make the room available for two days.


Where is this "two days" constraint coming from? My assignment says "The single night to which this record relates" so my assumption is that the date is fixed by the hotel. The 48 hour constraint applies to how much time before the date the person can book (ie. they can't book a room 2 weeks before it's available - the booking has to be made at most 48 hours before the date on the record).


So if I have an aviable room for date(yyyy/mm/dd) 2001/01/01 the room is aviable for the interval 2001/01/01-2001/01/03.
It does not meter how log the room remain booked.


Well, if you're assuming 2 days, then yes that would be correct.

If today is 2000/12/30 and I book that room and then on 2000/12/31, I call and cancel, the room is still only available on 2001/01/01 - the date does not change.

If today is 2001/01/10, then that room can't be booked under that record because the date has passed. We don't know if it's available. If it becomes available, I assume a new record with a future date will be created.

Hope that helps.
[ June 26, 2006: Message edited by: Peter MacMillan ]
 
Mihai Radulescu
Ranch Hand
Posts: 918
IntelliJ IDE Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Now I get it, at least I hope.

A record gets aviable on a certain date

The single night to which this record relates, ....

and the booking can be maked with 48 hours (or two days) before this date.
If the 48 H interval is out the room is can not be booked (anymore).

I am right now ?

Regards M.
[ June 26, 2006: Message edited by: Mihai Radulescu ]
 
Peter MacMillan
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Mihai Radulescu:

A record gets aviable on a certain date

and the booking can be maked with 48 hours (or two days) before this date.
If the 48 H interval is out the room is can not be booked.


That sounds good.

Originally posted by Mihai Radulescu:
I am right now ?


I would say so, based on my own assumptions of the requirements. Remember that some parts are intentionally vague in order to get you to make design decisions for yourself.
 
Mihai Radulescu
Ranch Hand
Posts: 918
IntelliJ IDE Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This I must admit :


some parts are intentionally vague ....


but at least I got it.

Thanks a lot.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic