PROJECT REPORT

ON

LUXURY CAR DEALERSHIP

WEBSITE(OffRoad)

SUBMITTED BY SUBMITTED TO
NAME: UTKARSH KUMAR, NAINA JHA SUPERVISOR: DR. APEKSHA MITTAL
PROGRAM: BCA DESIGNATION: ASSISTANT PROFESSOR
UNIVERSITY ROLL NO: 210160212015, DEPARTMENT: SOES
210160212020

SCHOOL OF ENGINEERING AND SCIENCES,

G D GOENKA UNIVERSITY

18/03/24
 Group Profile

GROUP NAME: OFFROAD

PROJECT NAME: LUXURY CAR DEALERSHIP WEBSITE(OffRoad)

S.NO STUDENT NAME COURSE ENROLLMENT

1. UTKARSH KUMAR BCA 210160212015

2. NAINA JHA BCA 210160212020

 TABLE OF CONTENT

1. SRS

 Objective
 Introduction
 System Description
 Functional Requirements
 Non-Functional Requirements
 Hardware Requirements
 Work Table

2. Design Document
 FlowChart
 Languages and Tools
 Data Flow Diagram
 ER Diagram
 Class Diagram

3. Testing
 CAR DEALERSHIP WEBSITE(OffRoad)
Objective
The objective of this project is to develop a platform that seamlessly integrates the front-end
and back-end, providing an optimal user experience and provides the client with an easy-to-
use system to efficiently manage the content of the website.

Introduction
Purpose
The purpose of this document is to define the requirements for the development of an website
for a luxury car dealership “OffRoad”. The objective is to create a user- friendly and visually
appealing platform with a simple back-end system that allows the client to manage inventory,
orders, and services without external assistance.
Scope
The scope of this project includes the creation of a comprehensive website, covering the sale
and rental of luxury cars, along with services for restoring various classic car.

System Description
System Overview
The system comprises a front-end for user interaction and a back-end for administrative tasks.
The front-end provides an intuitive interface for users to browse, purchase, and rent cars,
while the back-end enables the client to manage inventory, orders, and services seamlessly.
Front-end Features
 User-friendly interface for easy navigation.
 Categories for browsing luxury cars for sale and rent.
 Detailed product pages with specifications and pricing.
 Secure user authentication and registration.
 Intuitive booking system for car rentals.
 Service pages outlining restoration options.
Back-end Features
 Admin login for secure access to the back-end.
 Inventory management for adding, updating, and removing cars.
 Order management for tracking sales and rentals.
  Service management for handling car restoration requests.
 User management for handling customer accounts and inquiries.

Functional Requirements
General User Requirements
 Users should be able to register, log in, and manage their accounts.
 Users can browse luxury cars for sale and rent, with detailed product pages.
 Users can book and pay for car rentals through a secure payment gateway.
 Users can request car restoration services.
Admin User Requirements
 Admins should be able to log in securely to the back-end system.
 Admins can manage the inventory of luxury cars.
 Admins can track and manage orders for sales and rentals.
 Admins can handle service requests and manage the restoration process.

Non-functional Requirements
Performance
 The website should load quickly to provide a seamless user experience.
Security
 User data should be securely stored and transactions should be encrypted.
 Admin access should be password-protected with multi-factor authentication.
Usability
 The front-end should have an intuitive design for easy navigation.
 The back-end should have a simple and user-friendly interface for admin tasks.

Constraints
 The system must be compatible with major web browsers.
 The website should be responsive for optimal viewing on various devices.
Hardware Requirements
The system should be hosted on a server with the following minimum specifications:
 Processor: Dual-core 2.0 GHz or higher
 RAM: 4 GB or higher
 Storage: 100 GB SSD or higher
 Internet Connection: High-speed broadband

Technical Feasibility
 The required technologies and tools for development are readily available.
 The integration of front-end and back-end technologies is feasible.
Operational Feasibility
 The website will be designed for ease of use for both customers and administrators.
 Adequate training and documentation will be provided for admin users.
Economic Feasibility
 The project budget is within acceptable limits.
 The benefits of increased sales, rentals, and service requests justify the investment.
 DESIGN DOCUMENT

FlowChart
FlowChat is divided into two parts front-end (for user) and back-end (for admin).
Front-end flowchat:
Back-end flowchat:

Languages and Tools

Languages: HTML, CSS, JavaScript, PHP.
Tools: WordPress, Hostinger.
Data Flow Diagram (DFD)
Data flow diagram shown below:

ER Diagram (Entity-Relationship Diagram)

Entity-relationship diagram shown below:
Class Diagram
Class diagram shown below:
 TESTING

Home Section Interface

Go to Listing button function
Categories Section Interface
 Categories/Convertible

 Categories/Coupe
 Categories/Passenger

 Categories/Sedan
Rental Section Interface
Restore Section Interface
About Us Section Interface
Contact Us Section Interface
Sign In Section Interface
Before Sign In:
After Sign In:

User Account Section Interface

Add Listing Section Interface
Without Sign In:

With Sign In:

Car Details Section Interface