But connecting to the FFM db directly is not a correct approach since you are violating the requirement given by the assignment.
Hi Joe,
I think your definition of the segment is definitely CORRECT.
You will need to take a few steps backwards ( to understand the Forest and Trees ) To solve the problem that you are facing with your interpretation of the usecase : "I can only select A segment to change".
Nowhere it says that users CANNOT iterate this usecase to mean "User Select SEGMENTS to change" applying this usecase iteratively if it needs.
Whether the change is applied to a single segment or a bunch of them, The user would anyways be changing it one by one...That is how I have interpreted "Select A SEGMENT to change"
How about an Itinerary can only have 1 (one-way) or 2 (return) segments, with each segment consisting of 1 flight? Any other journey combination (A->B->C) would have to be set up as a series of iterations?
This would simplify the 'Change Itinerary'.
I think that if you have an Itenerary like A-->X, X-->Y, Y-->C and you decide to change the segment X-->Y, the Segment X->Y is deleted and another segment is created Z-->T for example, and the iteneray become A-->Z-->T-->C.
then you can not change the trip A-->C, but you can change A-->X-->C, A-->Y-->C.