Car Dealership Management Database System ER Diagram

Generate an entity-relationship diagram (ERD) illustrating a car dealership management database system. The ERD should include the following entities, attributes, relationships and their cardinalities: Entities: 1. Branch – with attributes: unique branch ID, phone number, address (composed of city, state, zip code). There is a one-to-one relationship with the branch manager identified by the Manager entity. 2. Manager (Employee) – with attributes: Employee ID, name, phone number, email address, date of birth. Each Manager manages one branch. 3. Employee – with attributes: Employee ID, name, phone number, email address, date of birth. Each employee is assigned to one branch, but each branch can have multiple employees. 4. Car – with attributes: unique license number, make, model, year, price. Each Car is associated with a single Branch, but a Branch can have multiple Cars. Each Car is managed by a single Employee. A Car could have multiple Owners. 5. Owner – with attributes: Owner ID, name. An Owner can own multiple Cars. Also, include the attribute 'percentage owned' to represent their share of ownership of the car. 6. Registration – with attributes: license number, registration date, registration expiration date. Each Car must link to its Registration details. 7. Insurance – with attributes: Insurance ID, type of insurance, insurance details. Insurance policy is linked to a car. Specify primary keys for each entity and cardinality ratios for each relationship type.