I feel certainly like
now. But I will not give up.
My whole understanding was:
-Itenerary has segments (1 or many).
-Each segment has flights. (1 or many)
The relationship in the BDM confused me. In BDM it says 1 segment has 1 flight. How do you fit connecting flights (London->Brussels->NewYork) in a segment.Segment should stand for the trip from London to Newyork. And under a segment you should have connecting flights, etcs. Segment should be the structure to organize these connecting flights.
So either the BDM is wrong and I have to correct it OR
I have to find an other way to organize these connecting flights...
If the latter is the way to go, then what the hell is SEGMENT for?
From your answer I got the following conclusions:
When a customer ask a flight from London to NewYork, Flight table returns a bunch of flights. Each flight might have legs. (for connecting flights)
Then Segment is synonym for the Flight. and is used to price the whole flight etc.. The data model for this suggestion would be.
Itenerary - Fligts (1 to many)
Flight - Leg (0 to many)
Segment is a logical construct formed in the OO layer.
Please give this
(man) a hand !