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.
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.
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
Weeds: because mother nature refuses to be your personal bitch. But this tiny ad is willing:
a bit of art, as a gift, the permaculture playing cards