insurance website database layout urgent help :(

[busby]

hello

 

im creating a vehicle insurance website for a university project.

 

its going to be an online profile site similar to http://www.swiftcover.com

 

where users create a profile which stores their personal and vehicle data and they can view and edit their policy at any time and submit claims and view certificate etc.

 

my only question is...what tables would i need for the database?

 

would i have a customer table storing all their personal info and their username and password.

 

then a vehicle table storing all vehicle info connected to the customer table via the C_ID

 

would the customer table be connected to the vehicle table via the V_ID?

 

what other tables would i need?

 

i dont know why but i just cant picture the database in my head and i think once i know the tables i can continue on my own

[kickstart]

Hi

 

Think you would need a customer table, and person table (to cope with multiple named drivers), a vehicle make table, a vehicle model table, probably a sub model table (so you can select the engine or trim level of a model), application table (to store details for a particular application), insurer table (storing each other company they do a quote for) and a results table, listing the results of an application for a particular insurer.

 

Sure there are probably more details to be stored. For example storing the type of cover available, list of levels of excess allowed, list of levels of no claims allowed, etc.

 

All the best

 

Keith

[fenway]

Also, it's against the rules to ask for "urgent" help.