File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

doubt on use case Change Itinerary

 
Yiu Wing Tsang
Ranch Hand
Posts: 30
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
After reading the basic flow of the use case Change Itinerary for serveral times, I feel odd at this "In order to change, the segment is deleted and the Preare Itinerary Use Case is executed".

I feel doubt on the requirement of "delete segment", can we allow to change the itinerary but just adding new segment without deleting any existing segment in the itinerary?
 
Santiago Urrizola
Ranch Hand
Posts: 172
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i think this type of details are not an architect responsability .... this in abstract ... as an architect.... you must cocentrate your esffort in technical issues.
 
Yiu Wing Tsang
Ranch Hand
Posts: 30
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Santiago Urrizola:
i think this type of details are not an architect responsability .... this in abstract ... as an architect.... you must cocentrate your esffort in technical issues.


thanks for your quick response

This means, for this assignment, we just follow the stuff desribed in the use case requirement? Since I feel doubt the sequences/steps described in the use case, but I cannot verify the requirement anymore from the users and wanna seek more opinion here.

Back to my question, do we still need to handle the case of adding new segment(s) in use case Change Itinerary?
 
Brian Smith
Ranch Hand
Posts: 232
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Santiago Urrizola:
i think this type of details are not an architect responsability .... this in abstract ... as an architect.... you must cocentrate your esffort in technical issues.


Yiu, your concerns is more of a business decision - what the business (user) wants. However, at this point, particularly for this project, you play the role of user too, so I think you get to make this decision. So when you change the segment in the itinerary, why do want to keep the old one and add new one? After all, you are not okay what you chose and would like to change, which I think you would want to replace the old one with the new one that you are ok with. what do you think?
 
Yiu Wing Tsang
Ranch Hand
Posts: 30
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Brian,

Yes, I seem to think of the case being a user rather than architect. In fact, I think it would be enough to just implement what have been described in the use case specification, however, I am just curious if it would be a problem if the system does not support "adding new segment without deletion of existing segments in the same itinerary".

For example, the itinerary originally contains two segments: A->B, B->C
(yes, it does not have any return segment).

Now the customer wants to go from C to D as well, so he/she designs to add a new segment C->D and the itinerary would like that:
A->B, B->C, C->D

I don't know this would be valid or appropriate as I don't have much experience/knowledge on the real flight booking.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic