Are Leg and Segment synonyms?

[Gavin Andrews]

I'm thinking of not having Leg anywhere.... it seems to be a synonym of Segment....

Is it safe to represent only Segment?

[Frank Silbermann]

The directions are contradictory and ambiguous, so assume what you will. I'm leaning towards making a Leg an aspect of a flight, and a segment an aspect of an itinerary (a leg booked by one passenger).

[Parag Doshi]

Gavin,
There is a similar topic, meaning of "leg of flight" which discusses "flight", "leg" and "segment" in some detail.

Parag

[Gavin Andrews]

I googled and found...

Leg/Segment

A leg is that portion of the trip between consecutive flight stops. The segment can be a group of legs, because the segment is that portion of a trip from boarding point to a deplaning point.

That seems to answer my question.

[Gerald Davis]

In my model for example if a single journey needs one stopover , I just make it two flights opposed to one flight with two legs.

[Khaled Othman]

I think there is a difference between real world definitions of leg and segment and the assignment's definition.

Based on searches I've made on travel agencies' and airlines' websites:
One Leg = one or more connected flights (segments) for one origin/ destination (also Journey or trip)
Stop over = location between two or more legs (mutli-leg travel)

One segment = a flight with a number from X city to Y city
Lay Over = the transit or connection between two segments

The assignment, however, uses the term "leg" incorrectly. It uses it as a segment. This is actually to our advantage, because it reduces complexity - there is only one concept and not the two. So in the assignment there are only "segments"!

[Parag Doshi]

 

Originally posted by Khaled Othman:
I think there is a difference between real world definitions of leg and segment and the assignment's definition.

Based on searches I've made on travel agencies' and airlines' websites:
One Leg = one or more connected flights (segments) for one origin/ destination (also Journey or trip)
Stop over = location between two or more legs (mutli-leg travel)

One segment = a flight with a number from X city to Y city
Lay Over = the transit or connection between two segments

The assignment, however, uses the term "leg" incorrectly. It uses it as a segment. This is actually to our advantage, because it reduces complexity - there is only one concept and not the two. So in the assignment there are only "segments"!

Thats an assumption you have to make Khaled I, now, after lots of research into it, dont think there is a correct or wrong defintion of segment/leg. We have to just document what our definitions are and how it meets all the requirements of the system. We cant tell them, you are wrong , can we?
[ August 30, 2004: Message edited by: Parag Doshi ]

[James Wang]

Parag,

I agree with you fully, I think I need try to design it and document it in detail.

[H. Hafer]

Parag,

Originally posted by Parag Doshi:
We have to just document what our definitions are and how it meets all the requirements of the system.

... and that's the very reason i decided to base on a simple as possible business domain model - if the requirements don't state it, I simply don't adhere to it. Let's see, what happens

Cheers,
Harbo