Forums Register Login

Pricing..again

+Pie Number of slices to send: Send
Can somebody explain the logic behind the alternative flow 'price itinerary'.
Why only calculate the additional payment for the segment?

Can't you just calculate the total cost of the itinerary again and then calculate difference. You won't need an alternative flow this way...

Or is this a case of 'Just follow the requirements'?
===================
In the use case description of "change itinerary" I can see no reference to Price Itinerary! But in the diagram it says that Change Itin includes 'Price Itin'.

I think it is also strange that the outcome of the first flow is a changed itinerary and the outcome of the second flow is only a Payment difference.

When is the actual Price of the changed Itinerary changed?
Should the deletion of a segment and the update of the Price not be in one transaction?
(Will your data not be corrupted if you do otherwise?)

I think the best place to change the actual Price is at the end of Change Itinerary? But you will also have to call Price Itin then? This is not in the use case description. However, The Diagram Prepare Itin does include Price Itin. So you have some arguments to do this?

An other argument to back this up: what happens if the user only deletes a segment and does not select a new one?
When the customer goes to Pay Itin Use case, surely the Price of the Itin must already be changed, as Pay Itin does not include Price Itin.


[ January 31, 2005: Message edited by: Josep Andreas ]
+Pie Number of slices to send: Send
Let me re-phrase:
Assume that the alternative Flow of price Itin is called from
Change Itin
I think there are two options:
1. Only calculate Price of deleted segment (and forward to Prepare Itin).
2. Include 'Prepare Itin' in 'Change Itin' and let it return the changed Itin. Then calculate price difference between new and old Itin...
(and only delete segment after a new one (or none) is selected)

When you select option 2; you will have to add an alternative flow for calculate price in 'Prepare Itin..'

anyone..?
[ January 31, 2005: Message edited by: Josep Andreas ]
+Pie Number of slices to send: Send
Josep,

I am going with option 1.

I think the Change Itinerary behavior depends a lot on how you define your segments.

regards,
Deepak
+Pie Number of slices to send: Send
Josep,
If u just follow the use case ..it goes into prep itinerary and that is where the price and "pay for.." is executed.
Keeping it simple if u simply do the change itinerary impl without looking at the other chnages and let prep itinerary handle it as a itinerary creation would work.

I had asked this question sometime ago from a SCEA.
SCEA Post referred


Priya Patel
greenhorn
Member # 65779
posted March 18, 2004 06:47 AM
--------------------------------------------------------------------------------


quote:
--------------------------------------------------------------------------------

Dhiren Joshi Wrote :-
Congratulations Priya ,
Could you give some hint as to what you did for the change itinerary use case. I think the use case is a overkill when it says to go back to prepare itinerary. Any suggestions.. .. I cant figure out why removing a segment would necessitate the entire itinerary preparation called all over again.
Thanks
Dhiren



--------------------------------------------------------------------------------



Hint The reason why the Prepare Itinerary needs to be executed is because you need to re-price your itinerary. Your repricing logic and steps to get to that stage should be in your Prepare Itinerary use case...




Thanks
Dhiren

[ February 01, 2005: Message edited by: Dhiren Joshi ]
[ February 01, 2005: Message edited by: Dhiren Joshi ]
+Pie Number of slices to send: Send
Dhiren,
Do you add an alternative flow to the Prepare Itin or just follow the flow as is?
Thanks
J
+Pie Number of slices to send: Send
Josep,
Just follow the flow as is .
HTH
Dhiren
+Pie Number of slices to send: Send
Alt Price Use case is not in main flow of Prepare itin in my design?
Is this the key? At this moment I cannot see any use for it in there?
+Pie Number of slices to send: Send
 


Why only calculate the additional payment for the segment?

Can't you just calculate the total cost of the itinerary again and then calculate difference. You won't need an alternative flow this way...



It sounds like its just normal practice in e-commerce. The reason is that in most airlines, prices change all the time and so you only pay again for the segment you are changing.

It doesn't seem to matter for FBN because prices are fixed but they might decide to change that in future. They would want your system to handle that without re-developing the booking system.
+Pie Number of slices to send: Send
Some more input...
I have no problem with change itin and the fact that it just calls prep itin.

But consider the scenario:

1. User deletes segment
2. User selects alternative segment
3. System (re)prices itin.

If the customer just deletes the segment and does not proceed with step 2/3.
and then goes to payment...
Isn't the itinerary being priced incorrect?
J
[ February 09, 2005: Message edited by: Josep Andreas ]
+Pie Number of slices to send: Send
 

Originally posted by Josep Andreas:
If the customer just deletes the segment and does not proceed with step 2/3.
and then goes to payment...
Isn't the itinerary being priced incorrect?
J



Josep,

Just state one simple assumption that Delete Segment function will authomatically negate the price portion of the Itinerary.

Deepak
+Pie Number of slices to send: Send
mmm...
I've letting this rest for a while. still not sure.
What if you just want to delete a segment, without selecting a new one.
Could happen. maybe you decided to take train back or stay there ( ).

I really do think that deleting a segment and changing the price should be done in one transction..
(in the end price itin UC IS included in Change Itin UC....)

I think, this is not something that you can leave for detailed design or implementation. this has to do with logical flow of app.


J
[ February 20, 2005: Message edited by: Josep Andreas ]
If you open the box, you will find Heisenberg strangling Shrodenger's cat. And waving this tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com


reply
reply
This thread has been viewed 799 times.
Similar Threads
PrepareItinerary
Change Itinerary Use Case - deleting segments
price itinerary(SCEA old)
price itinerary use case
Question on pricing
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 29, 2024 05:50:07.