A database is to be created for a repairs and services section of a car garage where owners of cars make

a booking for their car for certain jobs to be carried out $($repairs or service$).$

Data is stored on the owners of the cars who are referred to as customers. Details stored on customers

are: a unique customer ID$,$ a name and a mobile phone number. A car is always associated with a single

customer.

Each customer may own one or more cars. The data stored on cars includes: car registration number $($a

unique code for each car$),$ car manufacturer $($e$.$g$.,$ Toyota$),$ car model $($e$.$g$.,$ Yaris$),$ car year, and whether

the car is under warranty, or not, with the garage.

When a car is booked for a job, the booking date is stored. In addition, the following details are held on

each job: a unique ID for the job, the day and time booked for the car to come to the garage for the

job, a description of the job required $($e$.$g$.,$ oil change, replace brake pads$),$ the duration of the job $($in

hours$),$ the cost of the job $($which comprises the cost of parts $($if any$)$ and the cost of labour$),$ the day

and time the car is ready for pick$-$up$,$ a summary of the work done by the mechanics and any follow$-$up

instructions $($e$.$g$.,$change tyres in $6$ months$).$

As part of each job, one or more diagnostic tests could be run on a car. Each diagnostic test has its own

unique ID$,$ a name, and the expected $($normal$)$ value for t