urgent! It's last day.

thanks

Consider the following scenario, for the Reliable Rentals Ltd. The requirements collection and analysis phase of the database design process has provided the following data requirements for a company called Reliable Rentals, which rents out vehicles (cars and vans). The Company has various outlets (garage/offices) throughout Glasgow. Each outlet has a number, address, phone number, fax number, and a manager who supervises the operation of the garage and offices at each site. Each site is allocated a stock of vehicles for hire; however, individual vehicles may be moved between outlets, as required. Only the current location for each vehicle is stored. The registration number uniquely identifies each vehicle for hire and is used when hiring a vehicle to a client. Clients may hire vehicles for various periods of time (minimum 1 day to maximum 1 year). Each individual hire agreement between a client and the Company is uniquely identified using a hire number. Information stored on the vehicles for hire include: the vehicle registration number, model, make, engine size, capacity, current mileage, date MOT due, daily hire rate, and the current location (outlet) of each vehicle. The data stored on a hire agreement includes the hire number, the client's number, name, address and phone number, date the client started the hire period, date the client wishes to terminate the hire period, the vehicle registration number, model and make, the mileage before and after the hire period. After each hire a member of staff checks the vehicle and notes any fault(s). Fault report information on each vehicle is stored, which records the name of the member of staff responsible for the check, date checked, whether fault(s) where found (yes or no), the vehicle registration number, model, make and the current mileage. The Company has two types of clients: personal and business. The data stored on personal clients includes the client number, name (first and last name), home address, phone number, date of birth and driving license number. The data stored on business clients includes the client number, name of business, type of business, address, telephone and fax numbers. The client number uniquely identifies each client and the information stored relates to all clients who have hired in the past and those currently hiring a vehicle. Information is stored on the staff based at various outlets including: staff number, name (first and last name), home address, home phone number, date of birth (DOB), sex, National Insurance Number (NIN), date joined the Company, job title and salary. Each staff member is associated with a single outlet but may be moved to an alternative outlet as required, although only the current location for each member of staff is stored. Using the relational approach to data modelling, produce a relational data model for the above scenario. The proposed database schema should be normalised up to a BCNF. Your submission should comprise: a list of the identified functional dependencies, Correct identification/specification of Functional Dependencies, incl. any assumptions - 6 Marks a fully-fledged discussion explaining and justifying the normalisation process, 5 marks for the correct identification/justification of the primary key, 5 marks for the correct application of the normalisation process, 5.5 marks for the justification/discussion of the steps taken 15.5 Marks the final relational schema along with primary keys, foreign keys, etc. .5 mark for the correct identification/specification of the primary keys, 3 marks for the correct identification/specification of the foreign keys, but no more than 2 marks if the FKs are not fully specified (i.e. referencing/referenced table(s)/column(s)) 3.5 Marks 25 Marks