Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Change Itinerary Use Case - deleting segments

 
jono
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi ,

The Change Itinerary use case states that the segment is deleted and the prepare itinerary use case is executed. This does not make sense to me - it means you start the prpeare itinerary use case with "a portion of" an itinerary. There is no provison for this in the prepare itinrary use case. I have therefore decide to have the user join the use case where it displays a set of priced search results and just have the flight(segment) not deleted selected. They are then free to update the itinerary an save again.

what do you think?

 
ranjeeth kumar
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi-
This is my thoughts. Take this example. I am travelling from Indiana to Lasvegas (roundtrip)

The flight details are

IND->ATLANTA-LASVEGAS (TO)
LASVEGAS->ATLANTA->IND(BACK)

For this roundtrip there is 2 segments , and each segment has multilple "legs" or layover. If you think in this way the solution can be find.

What say?

Ranjeeth
 
jono
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ranjeeth,

I have the same definition of segment as you! so at least we are starting from the ame place. However, let's say a user does the following:

- execute prepare itin use case => have prepared itin
- come back and execute the change itin use case
- this deletes say, the first segment of the round trip
- if they then go back to the start of prepare itin use case, they will be presented with a search screen and they will be starting all over again!

The solution to this that I can see is that the itinerary is stored in the session but somehow the user needs to be notified that they are not actually starting over. the only way IU can see to do this is to start them in the middle fo the prepare itin use case and have the remaining segment highlighted in the results?

do you have an alternative?
 
Josep Andreas
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Here is a useful thread where another definition of segment is used:
http://www.coderanch.com/t/152525/java-Architect-SCEA/certification/Price-Flight
 
jono
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Josef,

Thank you. that did indeed give me another perspective. Not one I like very much though!

It doesn't make sense that a Flight (ETE journey with multiple segments) coudl have non-contiguous segments (single A to B plane jounrney).

And the alternative i.e. to manage the issue of connecting up the segments (i.e. where Flight A->B->C->D and B->C is deleted) just adds unnecessary complexity.

I do not like the solution I am proposing: If user deletes Segment (ETE journey with multiple flights) then they effectively search again but with the remaining segment selected. But it strikes me as the most intuitive to the user and also the easiest to design for.

Still not very happy about this one though...
 
Ajith Kallambella
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
jono

Welcome to JavaRanch.

Unfortunately your name doesn't gel well with our naming policy. Please take a quick look at the rules and edit your profile accordingly.

Thank you!
 
Josep Andreas
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jono,

(I am also still not happy with my solution, allthough I seem to be following a different path)
Just sharing another perspective:

- Fact is that the outcome of The Change Itin is an Itinerary with a deleted segment (with a correct or incorrect price, depending on how you implement pricing, but this is another issue).
- Fact is that after Change Itin the flow is forwarded to Prepare Itin.

Wouldn't a logical consequence be:
Prepare Itin starts with creation of an empty itinerary (!)
And if prepare Itin is called from Change Itin you
set The Itin reference and skip the first step.

This way you always start Prep itin with a Itinerary reference.
(an empty or an existing itin).
At the end of Prep Itin the segments are added to either the empty or existing Itin.

J
[ February 15, 2005: Message edited by: Josep Andreas ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic