• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

change itinerary confusion

 
abd hassan
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think this has to do with how you define your segment/Flight associations.
If a Customer deletes a segment, then quite possibly it will render the rest of the segments invalid.
For example, in a journey from A to B, we can have segments A to C and then C to B. If A to C is changed to let's say A to D instead, then C to B becomes invalid. Any thoughts ?
 
Siddhartha Bhattacharya
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Not really. It really depends on what all scenarios you want to address. If you looking at a pricing point of view, you can price all the segments independently and then have a reduced rate if there are connections.
You can always change your itin to A-D and still have C-B valid with the 'arrival' to C unknown (in other words the passenger walked, drove, flew some other airline) from D to C.
Consider a real life example of inter-island flights or changing between LGA, JFK, EWR gateways.
 
abd hassan
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks. I see. That takes me to another question. When a customer can change an itinerary (ie. a segment in the itinerary), they wouldn't be interested in the connecting flight information. Generally, they would change either the departing or return flight. I wonder if thats what meant by changing a segment.
 
Siddhartha Bhattacharya
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
He can change any segment in his itin. Even connecting flights (Ex he wants to add another stop between his outbound connecting flight). There are just too many scenarios that are possible in a real-world application. I guess from the exam perspective, keep it simple. Let him change whatever he wants and assume your pricing routine takes care of validity, discounts, condition types etc..

Good luck
 
Theodore Casser
Ranch Hand
Posts: 1902
Hibernate Netbeans IDE PHP
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm inclined to agree with Siddhartha - keep it as simple as possible. It's far too easy to make this a more complicated problem than it really is.

That being said, whatever you decide on, don't forget to document your assumption since that's going to change how you handle the procedure.
 
Lucy Hummel
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Hassan,

I totally agree with Theodore. Keep it as simple as possible and mention all your assumptions.

I do not take care which segment my customer deletes. That is his/her problem. Not mine

Lucy
 
Kate Young
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think it's a design decision based on what your definition of segement is.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic