Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Part II: reserved seat taken?

 
Annie Zhang
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am wondering if this occurs to you if the reserved seat in the unpaid itinerary is taken when the customer tries to pay for it.

Do we need to consider this or it is beyond the requirement?

Thanks,
Annie
 
Parag Doshi
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Annie Zhang:
Hi,

I am wondering if this occurs to you if the reserved seat in the unpaid itinerary is taken when the customer tries to pay for it.

Do we need to consider this or it is beyond the requirement?

Thanks,
Annie


Annie,
Thats implementation issue. It all depends on whether you are considering unpaid reservations vc paid ones, while doing seat selections. And also if you are persisting unpaid itineraries or not.If you look at travel websites, they allow you to reserve seats for unpaid itineraries, but also add a disclaimer that seats wont be guranteed unless paid for..so, you can choose an implementation path and add it to your assumptions.

Parag
 
Annie Zhang
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Parag!

If I choose not to persist the unpaid itinerary, in the sequence diagram, the "reserve seat", "pay" and "save the itinerary" should be all shown in the same transaction. Normally we will also show if the "pay" successes or not to decide either commit or rollback the transaction. In this case, should we also check if "reserve seat" sucesses or not?

Or Is the transaction shown in the sequence diagram is implementation-oriented? Should we avoid it?

Thanks,
Annie
 
Parag Doshi
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Annie Zhang:
Thanks Parag!

If I choose not to persist the unpaid itinerary, in the sequence diagram, the "reserve seat", "pay" and "save the itinerary" should be all shown in the same transaction. Normally we will also show if the "pay" successes or not to decide either commit or rollback the transaction. In this case, should we also check if "reserve seat" sucesses or not?

Or Is the transaction shown in the sequence diagram is implementation-oriented? Should we avoid it?

Thanks,
Annie


Annie,
I showed the sequence of create itinerary, seat reservation and sending email in the sequence diagram and added a note that it will execute in a transaction with commit or abort being the final state. I didnt show failed transactions etc, it would just complicate the diagram.
I put these "steps" inside a block (like an open rectangle with the messages in it) structure to indicate that they are executed as one logical unit of work if the credit card authorization succeeds. And my else block just had one message of an email being sent for failed credit card authorization.

parag
[ October 08, 2004: Message edited by: Parag Doshi ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic