pricing question

[Kuan Fan]

I think the price itinerary use case is not necessary. The reason is that: we can get the coach price and first class price for a flight in the prepare itinerary use case( this use case require to display the price for the flight), then after the customer selects the seat, we can get the price for each segment( because one segment matched one flight) by simple calculation, such "coach price * number of seats"

I have no idea I'm correct or wrong. Hope somebody can help.

Thanks
Kuan

[Dhiren Joshi]

HINT; It is also also used for the change itinerary use case.
HTH
Dhiren

[Kuan Fan]

Good Point.

But the change itinerary use case will redirect to the prepare use case after the segment is deleted. The steps in prepare itinerary will be repeated.

I spent a lot of time to think about it, but still not clear now. Any other ideas?

Thanks
Kuan

[Lakshmanan Venkatachalam]

Hi,

Even i have the same doubt and i'm struck their. I started drawing prepare itinerary sequential diagram. I wonder where i can stop this because basic flow of use case covered the complete flow.

Not only the pricing the itinerary but also the payment. But we have separate usecase for prepare itinerary and pay itinerary. Can we link to these use case or we need to draw again in prepare itinerary.

Also the precondition of prepare itineary is customer must have logged in. But in real world customer should login only before confirming the tickets.

Any help on this is very much appreciated.

thanks
Lakshmanan

[Kuan Fan]

Hi Lakshmanan,

I decided to make a very simple price itinerary sequence diagram, just calculate price by number of seats multiply the coach or first class unit price and save the result somewhere.
I have also the same question for the preconditions, I think we have to make our own choice

Kuan