Design/normalisation

[debbieb]

I hope someone can help please - I have tried to design and normalise a customer complaint database for a department store but I am struggling to add the product number if there is one associated with the complaint, ie, could be product problem or something else such as rude staff etc so there may or may not be a product number. please see design below - apologises now if it is totally wrong but would really appreciate some guidence and help. Please see attached

 

[plog]

I am assuming the fields list under '3NF' are your tables--which brings up another issue, I see no table names, so its hard for me to reference them as such.

With that said, ProductID should be in the top most table. Unless of course you can have multiple ProductID's per complaint, in which case they should be in their own table along with the ComplaintID.

One last note, the store information seems to be on its own island--its not linked anywhere.

 

[jdraw]

I recommend you read and work through this tutorial.

You really have to get your tables and relations sorted out before you start programming.

Good luck

 

[ButtonMoon]

No one can say for sure what is normalized or not because you haven't specified the dependencies you are supposed to be modelling. All we can do is make some guesses and assumptions based on attribute names. I expect this is homework so the important thing is that you know and can justify your own decisions.

Identify the dependencies and if it's for real rather than just an exercise then I suggest you aim to satisfy Boyce-Codd / 5th Normal Form rather than 3NF.