Reference no: EM132091749
1. The following is the business environment of Enterprise Car Rental. A car is manufactured by one manufacturer only. A manufacturer manufactured at least one of Enterprise's cars. A car could have had many maintenance events (but a brand new car may not have had any, yet.) A car may not have been rented to any customers (again, the case of a brand new car) or to many customers. A customer may have rented many cars from Enterprise, and to be in Enterprise's business environment must have rented at least one. Please draw the ERD for the above business. Include any and all attributes you think are required such as Customer Details, etc.
Convert the ERD to tables and write CREATE table statements including all contstraints.
Note: If you are making any assumptions, do mention them explicitly.
2. The UT system is trying to create and convert their student records into digital form. The idea behind this database is to list all students in UT system colleges/universities with their Name, major, age during enrollment, address of residence and the corresponding school and university details.
There are no students who attend 2 colleges with in UT system at the same time, but there are many students who did their under-grad and grad with in UT systems. However, the variables Start_date and End_date is to mark when they went to which school. Branch_ID is not a unique value, same Branch_Id may represent another Branch in another University and a student can belong to only one branch in a college at a time.
To help understand UT systems data, an excel worksheet (UT students.xls) of current data fields they keep track of are provided. Look at the given MS Excel worksheet to see what kind of data they collect and record for each student enrollment.
Create tables for this database in 3NF form. Please note,
Look at the data in the excel sheet provided and determine the functional dependencies in the data. (20 Points)
Please provide detailed explanation about how you would proceed and split the data into multiple tables so that resulting tables do not contain redundancy so that it is in 3NF form. List each resulting table with its primary key(s), foreign key(s) properly identified. Remember to use the relational schema representation we used in class to show the list of tables, foreign keys.