Drive2Impress Car Database Project: ERD, Entities, and Attributes

This assignment presents a comprehensive solution for the Drive2Impress car database project, addressing the need for a more efficient system than the current Excel-based approach. The solution begins with an introduction to the project and its context, outlining the business requirements of Drive2Impress, a car dealership operating in Canberra. The core of the solution lies in the design of an Entity Relationship Diagram (ERD), which visually represents the database structure. This ERD defines the entities involved, such as showrooms, customers, suppliers, car types, and car models, along with their respective attributes. The assignment thoroughly details each entity, specifying primary and foreign keys to establish relationships between tables. The solution provides a clear understanding of the database's structure and how data will be stored and interconnected, enabling efficient data management and retrieval. The solution also includes relevant references.

Car Database 1
Assessment -2 Car Database
Submitted By
Course
Professor
Date

Car Database 2
Introduction
Methodically organized archive of indexed data (normally that is a group of related data values)
that allows recovery, updating, analysis, as well as output of the data. This data can be of type
designs, reports, contents, tables, its content, etc. representing practically each type of
information. Each system applications (that includes antivirus software, spreadsheets, and word-
processors) are databases at their center. (http://www.businessdictionary.com, 2017).
According to given scenario, Drive2Impress is a private venture that offers cars in Canberra.
Drive2Impress can get cars from a few distinct providers. Drive2Impress keeps its cars in a few
showrooms over the city. At this stage clients can't see the accessible cars online so to arrange
they should visit one of the showrooms. Clients call Drive2Impress to organize a visit before
they go to a showroom. Drive2Impress has been uses an Excel software to track their business
exercises; and this has caused numerous redundancies and inefficiency. In order to increase their
business and for the new management, they decided to research the choice of actualizing a
database framework. Being a database admin, my duty is to design the Drive2Impress database
structure.
Entity Relationship Diagram (ERD)
An entity relationship diagram, which is also known as an entity relationship (ER) outline, is the
graphical portrayal of entities and how they are connected with each other, is also used as the
part of figuring as to the connection of information that is stored in databases or data
frameworks. It is a bit of data or idea about which we can say that data is stored. (Beal, V.,
2017).

Car Database 3

Car Database 4
Entities
Various entities with their attributes are shown as following:
1. Showroom  ShowroomID, Showroom_address, showroom_postcode, , showroom_phone
Primary key  ShowroomID
2. Customer  CustomerCode, Customer_name, Customer_phone, Customer_address,
date_of_arrival, ShowroomID
Primary key  CustomerCode
Foreign key  ShowroomID references showroom.
3. Supplier  SupplierID, company_name, supplier_address, supplier_city, supplier_phone,
account_no, contact_person.
Primary key  SupplierID
4. Car_type  Type_code, type_name, market_segment, showroomID, SupplierID
Primary key  Type_code
Foreign key  ShowroomID references showroom, SupplierID references supplier
5. Car_model  Model_no, model_name, engine_capacity, seating_capacity,
year_manufactured, retail_price, Type_code.
Primary key  Model_no
Foreign key  Type_code references car_type.

Car Database 5
References
Database. Retrieved from - http://www.businessdictionary.com/definition/database.html
Beal, V. (2017). Entity-relationship diagram (model). Retrieved from -
http://www.webopedia.com/TERM/E/entity_relationship_diagram.html