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

Unpaid Itinerary...again

 
Ravi Dhanum
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

In the Change Itinerary and the Pay for Itinerary use cases, the customer is allowed to select a pre-existing itinerary. I have read previous topics which say that these itineraries are unpaid. My question is: how can they be unpaid if during the Prepare Itinerary, the Pay for Itinerary use case is called? The only way I see is that if an error occurred while trying to pay it.

What do you think? I have read and reread the use cases.

Thanks in advance.
 
Ravi Dhanum
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have also seen topics state that the itineraries are unsaved. I would say that the itineraries that can be chosen for the Change Itinerary and the Pay for Itinerary should be saved and paid for.

Any comments are appreciated.

-Ravi
 
Ravi Dhanum
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Anybody?

-Ravi
 
subramanian radhakrishnan
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Ravi Dhanum:
Hello,

In the Change Itinerary and the Pay for Itinerary use cases, the customer is allowed to select a pre-existing itinerary. I have read previous topics which say that these itineraries are unpaid. My question is: how can they be unpaid if during the Prepare Itinerary, the Pay for Itinerary use case is called? The only way I see is that if an error occurred while trying to pay it.

What do you think? I have read and reread the use cases.

Thanks in advance.



Ravi,

its simple. when the usecase "pay for itinerary" is invoked - i mean when the page for the payment is requestd, ths user can very well close the browser and go. So next time, when he logs in he must be able to see those itineraries that he saved and from there he can either modify or pay for any of those itineraries.

hope this helps.
 
Ravi Dhanum
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have also seen topics state that the itineraries are unsaved. I would say that the itineraries that can be chosen for the Change Itinerary and the Pay for Itinerary should be saved and paid for.


So the only way that the itineraries are not saved and paid for is through user actions which are neither in use case basic flows nor in use case alternative flows. It seems incorrect that alternate flows within the Change Itinerary and Pay for Itinerary use cases can be achieved only through undocumented user actions.

Please comment on this.

Thank you.

-Ravi
 
Ravi Dhanum
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Oh, I just thought of a way:

The user has entered a new itinerary via the Prepare Itinerary use case.
The user submits the itinerary. Once in the Pay for Itinerary use case, the user doesn't select to pay with credit card; instead, the user selects award travel, ...

A similar scenario can exist with the Change Itinerary use case.

Hmmm...it is simple.

Thanks for the discussion.

-Ravi
 
Vinay Singh
Ranch Hand
Posts: 174
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ravi/Mahesh
Are you going to save unpaid itinerary ?
I mean imagine a user logging in and finding unpaid itineraies on
his page. Are we also going to give an option to delete itinerary also?
It does not make sense to save an itinerary when the user is not
paying for it.Also the flight is available today, it might not be
available the next time he logs in!! That seat might be full.
Or am I missing something?
Vinay
 
Vinay Singh
Ranch Hand
Posts: 174
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The requirement says that " Before teh customer can confirm the flights and save teh itinerary.." This could very well mean saving the itinerary in the session , till the user logs in and pays for it.
We need to confirm the itinerary to check if that seat has not been filled in during that interval.
Vinay
 
Rashmi Razdan
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think in terms of flight booking , its doesnt make sense to save the unpaid itinary, as availabilty of flights and fares changes with time and days is far from consideration.
It makes sense to keep the search criteria for Session duration.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic