• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

NX: Bodgitt and Scarper unbooking contractors

 
Ranch Hand
Posts: 48
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello all,
I'm doing the design for my project, and I think I've got a good enough understanding of most of the issues (many thanks for all the info in this saloon) but there is one thing that eludes me: do the CSRs have to be able to unbook contractors?
The specification says enough about searching for and booking contractors but nothing about how a booking terminates. From the spec all I get is that the CSR find a contractor for the client and book it. When and how does that booking end and the contractor become available for another booking? Or is this not needed for this project?
My first reading was that the CSR does the booking and then I have to assume when the job is done either the client or the contractor calls in to say its all done so that the contractor's record can be made available for another client. This means a Service layer would have to have an unbook method, something I've not seen mentioned by anyone. If I stick strictly to the spec this is perhaps the only interpretation other than don't worry about ending bookings.
Another possibility is keeping track of the start date and length of the booking and then having the system update itself, but this would require an auxiliary data file of some sort and seems completely out of the scope of the project to me.
After doing a good bit of reading here, I couldn't find any references to this problem and so am wondering how others have handled this. Does anyone have any thoughts on this? This is one final piece I need to figure out so I can get down to coding.
Thanks for any help and regards,
Jay
 
Ranch Hand
Posts: 451
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jay,
There was some discussion of this in the thread : NX: Notes on a design that passed 389/400.
Its down a ways 20-some messages in that thread.
kktec
SCJP, SCWCD, SCJD
"The journey is the reward."
 
Jay Bromley
Ranch Hand
Posts: 48
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ah yes, there it was. There was so much info in that thread, I missed the answer to my question. Allowing anyone to unbook sounds good to me, and is the easiest of the options which I felt ok about. Great thread and congrats, by the way.
Regards,
Jay
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic