I am little confused about the logic here -
In Prepare Itinerary use case, after seats is confirmed, an itinerary is created. By end of the use case, the itinerary is persistent in the database. Which is fine.
In Change Itinerary use case, customer selects a segment to change. The segment is deleted and Prepare Itinerary use case is execute. I presume system will take departure city and destination city from the deleted segment and send to Prepare Itinerary use case to search the list of flight, then eventually the system will create another new itierary to replace the deleted segment.
It's kind of funny. After you change an itinerary, it breaks into two itineraries.
Any comments...
