Cars-To-Drive (CTD) is a used car dealership operating in the Sydney CBD as a franchise business. They wish to have their customers to be able to view the cars listed for sale online and to track what cars are being sold and what other cars are in stock by each franchisee.
CTD has hired you to design a relational database to better track and record their operational data, according to the business rules listed below:
1. CTD dealers exist in six different locations around the Sydney area and each location has just one dealer, being the franchisee.
Every location is identified by a location code, location name, street, city, state, postcode and phone number. Similarity, a franchisee is identified by a number, name, contact, etc...
2. A franchisee employs between 4 to 8 staff members in each location and one of these employees is the manager who supervises all other staff/employees.
Information about all the employees and the manager in each location is to be kept in the database.
3. Each location stores various types of cars, and each type may contain a range of the same type; for example a type is Commodore and a range is Commodore Calais-V, a Commodore Evoke, etc., but each range is of only one type.
Information about all the car type, range, year, and condition in each location is to be kept in the database.
4. CTD needs to also record the cars that were sold by each franchisee: the type and range, the date sold and the salesperson who sold the car. Accordingly a franchisee may sell many cars of the same type and range.
· Create an ERD that represents the entities, attributes, the relationships between entities, and the cardinality and optionality of each relationship that are described by this business rule.
· Clearly show the primary and foreign keys for each entity.
NOTE
Use Flow Chart Maker & Online Diagram Software (https://www.draw.io) to create your ERD
Use Crows Foot notations
Any M:N relationship is to be resolved to a 1:M relationship
Manually drawing the ERD is NOT acceptable.
Online submission via Turnitin is required for this assignment. Details will be provided by your subject lecturer.
Rationale
This assessment item is designed to test your understanding of basic database design and modelling concepts, and your ability to interpret business rules into an Entity Relationship Diagram.
Additionally, your ability to apply correct relationships, cardinalities, optionalities, and the use of Crows Foot modelling notations are tested.