Draw an entity diagram diagram for a car rental business identifying primary and foreign keys with the below attributes and cardinality Customer - Customer_ID (pk), Cust_Title, FirstName, LastName, DoB, Telephone, Address1, Address2, City, State, ZipCode Employee - Emp_ID (pk), Firstname, lastname, Telephone, Address, City, State, ZipCode, hiredate, SSN Car - Car_ID (pk), Model, Make, Year, Color, capacity, Customer_ID (fk), Payment_ID (fk) Payment - Payment_ID (pk), PaymentType, PaymentMethod, payment amount, Signature, PaymentDate, Receipt_ID (fk) Receipt - Receipt_ID (pk), Bill_To, Receipt_Total, Total_Amt_Due, Amt_Paid, CreateDate, Payment_ID (fk) Relationship and Cardinality Description Customer/Car: 1:M - one customer can have multiple cars on file, a car must belong to a customer Employee/Customer:1:M - One employee can have many customers to attend to but just one customer can be attended to at a time. Car/Payment: 1:M - one car can have multiple payment options on file, a payment must be associated with a car Payment/Receipt: 1:1 - each payment will generate one receipt and vice versa
Draw an entity diagram diagram for a car rental business identifying primary and foreign keys with the below attributes and cardinality
Customer - Customer_ID (pk), Cust_Title, FirstName, LastName, DoB, Telephone, Address1, Address2, City, State, ZipCode
Employee - Emp_ID (pk), Firstname, lastname, Telephone, Address, City, State, ZipCode, hiredate, SSN
Car - Car_ID (pk), Model, Make, Year, Color, capacity, Customer_ID (fk), Payment_ID (fk)
Payment - Payment_ID (pk), PaymentType, PaymentMethod, payment amount, Signature, PaymentDate, Receipt_ID (fk)
Receipt - Receipt_ID (pk), Bill_To, Receipt_Total, Total_Amt_Due, Amt_Paid, CreateDate,
Payment_ID (fk)
Relationship and Cardinality Description
Customer/Car: 1:M - one customer can have multiple cars on file, a car must belong to a customer
Employee/Customer:1:M - One employee can have many customers to attend to but just one customer can be attended to at a time.
Car/Payment: 1:M - one car can have multiple payment options on file, a payment must be
associated with a car
Payment/Receipt: 1:1 - each payment will generate one receipt and vice versa
Trending now
This is a popular solution!
Step by step
Solved in 2 steps with 1 images
