This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Five Lines of Code and have Christian Clausen on-line!
See this thread for details.
Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!

Shabbir Kothawala

Greenhorn
+ Follow
since Jun 04, 2007
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Shabbir Kothawala

Hi,

My understanding of leg is different

As per example given at http://gennick.com/?q=flight

Plane QF1 that flies from A to B, and then on to Z.

Plane QF2 that flies from A to Z directly, and then stops.

Plane QF3 that flies from D to E to F, and finally to Z.

Each hop from one point to another is called a "leg". For example, flight QF1 consists of two legs: from A to B, and from B to Z. Flight QF2 consists of a single leg, whereas Flight QF3 consists of three legs

Segment
Here I am really confused as there are different meaning used by every airline

As per defination of Southwest airline it says "One take off and landing during air travel constitutes a segment"

This means that segment is no difference then leg.

If this is the case then how to handle the change flight as per use case. As per use case a user can select segment to change and that means if your flight from departure to arrival consist of multiple leg then you can select one of the leg and change the its flight. This I never see in any airline. The airline only allow to change the entire route i.e from departure to arrival

Any thoughts on this

Thanks,
Shabbir
Wow .. You are coding the solution..

I will use a combination of session and entity bean. There are 2 task involved

1) Getting the list of available seat so that you can give user a choice to select
2)Once the seat is selected then updating the same in your seat tables..

Thanks,
Shabbir
Hi,

I have one question on sement

My understanding is a flights from source to destination will form one segement.
It means if you are travelling from Chicago to Orlando and book ticket with layover
i.e Chicago -> Atlanta, Atlanta -> Orlando then your itinerary will have 1 segment i.e from Chicago -> Orlando and this segment consist of 2 leg

I am correct?

If segment is what I understand then in domain model segment - flight should not be 1-1 mapping.. right?

Thanks,
Shabbir
Hi,

My understanding is a flights from source to destination will form one segement.
It means if you are travelling from Chicago to Orlando and book ticket with layover
i.e Chicago -> Atlanta, Atlanta -> Orlando then your itinerary will have 1 segment i.e from Chicago -> Orlando and this segment consist of 2 leg

I am correct?

Thanks,
Shabbir
Is my assumption correct? Please help me to understand

Many confusion without BA

Thanks,
Shabbir
Hey guys can you please help me as leg/segment is confusing me a lot and whenever I start I again come back to questions related to leg/segment

Thanks,
Shabbir
Hi,

Few questions

1) Is flat price per destination. My understanding is it is combination of flight+destination. i.e for flight number xyz there is always one price from Chicago to New York and for flight abc there is another price from Chicago to New York. Is this correct?

2) If above assumption is correct then only alternate flight with lesser $ value will be applicable.. correct?


Thanks,
Shabbir
Hi,

I have one doubt. If you are travelling from Milwaukee -> Orlando and let say your flight consist of 2 leg/segment i.e from Milwaukee -> Chicago and then from Chicago -> Oralando then how you will handle this in search result scenario

1) Combine 2 leg as one selection for the user
2) Let user customize his route by selecting any flight from Milwaukee -> Chicago and then from Chicago -> Orlando

Also this will require more then a normal VO design patter as return value to the client.. as your result can be combination of multiple flights leg. What design pattern is best suited for this scenario?
I think of Value Object Assembler but just thinking how then it will be rendered on the presentation side

Thanks,
Shabbir
Well you definetly needs to save the shopping cart. Here since the price of item will not going to change hence the save shopping cart is valid till the expiry date (we need to make this as assumption) as after expiry there is no use of save cart

So if you think of save cart and order cart as 2 different entities then you will have better picture

Thanks,
Shabbir
Sorry Theodore.. I put the question in quite lengthy way

The question is related to alternate flight. The issue occur when your source to destination consist of multiple segment. The alternate flight step will give the user a choice to select the flight that is within (+)(-) 1 hr of flight departure time and in case of connected flight (-) 1 hr will give an invalid option

That is what I am trying to understand that is alternate flight should only consider (+) 1 hr

Thanks,
Shabbir
Can anyone put some ideas on this

Thanks,
Shabbir
Any comments on my thoughts ?

Thanks,
Shabbir
Hi,

If the statement says "Customer selects the departure flight (not flights) then if the departure/return flight consist of multiple leg and each leg start with new flight then during the departure/return flights list you need to club the route segments and display as single selection (same as in expedia) and when user select flight then route segment flight nos needs to be send to calculate price

The problem will occur during the change itinerary. If you select 2 segment from your departure flight to change from itinerary then you again call itinerary prepare and in alternate flight scenario you may display the flight that have departure time less then 1 segment flight arrival time which is not a valid selection for user and should not be shown

How do you handle this?

Your inputs are highly appreciated

I hope with this question I am not crossing any SCEA privacy law as this in a very generic flight reservation scenario

Thanks,
Shabbir
We can use the generic screen names in the sequence diagram but that will not give good picture to designer/developers to whom the architect is suppose to handover his garbage