Few quries. A requirement is that customer selects seats. My question is
a) does this mean he selects which seats he wants..? This does not happen usually.
b) If yes, do we assume that the seats remain same for all legs/segment and even for return flights ?
c) Do wee need to lock the records when cutomer is selecting seats as some other consurent user might block that seat. Also hwne the payment is through, that seat might have already been booked by some other passenger?
I am a little confused with this aspect of requirement.
Please read the scenario below:
A flight (UA 147) has the route A-->B-->C-->D, a customer books the segemnt
B-->D. I define a leg as a flight between two contiguous airports.
Usually, airlines manage seat allocation in a seat inventory, they track seat usage per LEG.Seats are allocated to each leg of the flight.
My question: Do you think that i should represent this seat tracking mechanism accurately in the class diagram or let it as an implementation details and write on some assumptions, in this case seats allocation will be modeled at the flight level and not at the leg level ?
can you please elaborate on how you managed the session for web and rich clients. Also your approach to constructing component diagrams.
Congratulations with a phantastic score.
Can you share us your notes.
About component diagram.
How detailed your component Diagram was?
Have you showm the all the JSP like Cades diagram or just a single component with Note showing JSP names.
Is your component diagram was more like a deployment diagram with Nodes.Or just showing the component intraction like in Cades Book
Did you have shown patterns in Component Diagram.