Car Selling Application

- Amrish Nayak, Briana Crowe, Yash Chaturvedi


Description

This project is a part of CS 34800 Information Systems class at Purdue University. We designed a vehicle selling application/dashboard, where a buyer can customize, build and buy the cars that they want. It also has functionalities appropriate for the seller too which are listed below.


Application Features ->

 

• A potential buyer can choose from one of the default models.

• A potential buyer can look at the details of the car they selected.

• A potential buyer can look at any accessories to be added to the car and the costs associated with them.

• A potential buyer can look at total price of products in the car before purchasing it.

• A potential buyer can change the models/features/accessories and so the costs associated will also be updated accordingly.

• Seller can stop selling any vehicle.

• Seller can view cars purchased on a particular date.

• Seller can look at number of cars sold on a particular date.

• Seller can look at most common accessory sold for any particular model of any car.

Relational Database Schema


ERD Diagram



ERD Diagram Assumptions ->

  • A buyer always has a cart.

  • A particular cart can only be associated with one particular user (Assuming his account details are not shared with other people).

  • A particular cart can be made up of 0 or multiple brands (vehicles), so basically people can buy multiple cars at once (in a single order).

  • A particular car brand can be present in 0 or more carts. Basically, many people can buy the same brand’s vehicle.

  • Multiple brands can own a particular make(model) of a car or not. Example - BMW & Alpina have few models owned by both brands.

  • A particular make (model) belongs to at least 1 or more brands.

  • A particular make (model) can have 0 or more accessories added to it.

  • A particular make (model) is available in 1 or more colors.

  • A particular color can be available in 0 or more make (models).

  • A particular accessory can be compatible with 0 or more makes (models).



Tables

Buyer

Customer_ID (PK)

Name

Address

Phone Nos

Pin_Code

Cart_ID (FK)

Color

Color_ID (PK)

Color_Price

Color

Payment

Payment_ID (PK)

Payment_Method

Total_Amount

Customer_ID (FK)

Cart_ID (FK)

Accessories

Accessories_ID (PK)

Accessor_Price

Accessory

Cart

Cart_ID (PK)

Date_Added

Purchased

Brand_ID (FK)

Vehicle_Brand

Brand_ID (PK)

Make_ID (FK)

Make

Make_ID (PK)

Model_Shape

Engine_Power

0-60 mph

Price

Color_ID (FK)

Accessories_ID (FK)