Hi guys,

I have to design a EERD for a Airline Reservation System for a single airline.I have completed my EERD so long and would like to have some input from you guys as my DB experience is not so vast(but getting there)

Attached is the EERD and the specs.

Much Appreciated guys for the input
Sebastian

i had a really good chuckle as the first three entities i saw on your diagram were customer, seat, leg -- you're booking each customer leg separately from his seat? LOL

A Customer can only book one seat and a leg_instance is a instance of a flight leg...thats how i understood it from the attached specs.any advice?

what i've done to check the validity of my data model is to take a highlighter and highlight each line of text in the specs and then colour in the entities/attributes/relationships that support the spec

sometimes i use more than one colour

if there's anything left over on either side at the end, then i've obvioulsy overlooked something

have i overlooked something?

i dunno

when you coloured your diagram, was any spec left over?

none was left, as far as i know all the entities i have are the complete ones

Hi guys please help us, we need good advice on whether our entities and relationships are correct and if there must be any more additional entities. The whole flight leg and leg instance thing is screwing with us...please help.

we? there's more than one of you?

please explain what part of "the whole flight leg and leg instance thing" you're having trouble with

be specific

We are a group of 3 working on a project and I would like for you to just take a look at the EERD and give us some feedback if we are on the right track.

Thanks

yes, you are on the right track

Ok thank you.