Hi all, I was wondering if anybody considered the fact we might not have flights formed of more than one segment..
Just bare with my judgment for a moment.. : 1) The Prepare Itinerary doesn't mention anything about intermediary flights 2) The Change Itinerary use case would become suddenly clearer: after removing one segment it's very simple to go to Prepare Itinerary again (cause basically, by removing a segment you actually remove an entire one-way flight) 3) The company is a commuter airline.. who would travel more than 1-2 hours daily ? (this would be the usual time for a flight consisting of more than 2 segments) (I hope I understood exactly the term of commuter) 4) The CEO is not mentioning anything about more than one segment in a flight. The only things that might make us think we deal with 1 or more than one segment in a flight are the following:
In the BDM, an Itinerary has 1..* segments (and of course, an itinerary could have 2 segments, in case we consider the A->B and B->A; but it would be only 1..2, not 1..*)
All the examples in real-life provide at least one segment per flight.
Hopefully this question was not asked before (I wasn�t able to find it, if it was)
I failed the exam but I think to have the solution : the segment represent a dynamic table (because it is linked to a customer). the flight entity is better used to register a single flight. so you need another entity in order to configure the multilay flght that the company offers.
I have added a route [city-city] entity (that could have 1-n flight). By this way the searchFlight use the route entity and shows one or more flight (lay over), at the same time it simplify adding new flight to the most popular route. You will have a segment linked to many flight. And each flight (statically) willl be inside a route
Paolo Righetti Graduate in Informatic, SCJP,SCBCD-88%,SCEA-1�81%,2�59%