Is this normalised to 3NF?

[margybear]

Hi. My ICT coursework requires this database to be normalised to 3NF, and I was wondering if you could check if it works?
To me it makes sense, but I don't think that's a great way to confirm it!

In short:
*One customer can have many credit cards attributed to them.
*One customer can create many bookings.
*Each booking can only have one session list (i.e: a maximum of 4 sessions per booking
*One member of staff can carry out many sessions.

Does it make sense?
Thanks in advance!

Relationship screenshot attached!

 

[jdraw]

In order to get to a database in 3rd NF, there must have been a paragraph or two of verbiage describing the "business" at hand. In order to give you advice, we would have to see the business description.
In your model I see treatment1, treatment2, treatment3... which typically means you are missing a table, but since your description hasn't mentioned or defined session, treatment,staff and none of the attributes in you proposed tables, it's difficult to respond other than with some questions.

More of the initial description would be extremely useful to anyone trying to offer assistance.

A few questions:

How does booking tie in with Credit Card? Is it supposed to?
What is a Booking; a Session?
Is a Cost associated with a Booking or a Session?
You show Appointment in a table, but it isn't mentioned in your post?
Don't you need to identify what type of Credit Card(s) the Customer has?
My guess is that credit card is somehow associated with payment for Session and/or Booking.

 

[tehNellie]

^^ what he said basically.

Knowing nothing else about what's going on, the 4 treatment columns should be ringing alarm bells. What happens if next week they want 6? If you only book one treatment what goes in the other three?

Even if you have a cast iron, 100% written guarantee, signed in the blood of the owner's firstborn that there will always be 4 treatments per booking, no more, no less I'd still do it differently. Those cast iron guarantees only hold up for about .25Nanoseconds after you finish implementing it that way.

 

[spikepl]

1-to-1 between customer and booking precludes any repeat business for the same customer, without reregistering him or her (or IT?)

 

[peregrin]

Looks alright. Except sessions isn't really defined, so jury is out on that.

This looks less than ideal in a table:

Treatment 1
Treatment 2
Treatment 3
Treatment 4

Though strictly speaking this will limit you to 4 *treatments*. Not 3NF though, I guess, if you get down to the nitty gritty.