Vehicle Purchase Application Report
Vehicle Purchase Application Report
VEHICLE
A PROJECT REPORT
Submitted by
degree of
BACHELOR OF ENGINEERING
IN
(AUTONOMOUS)
SAMAYAPURAM
MAY 2025
I
K. RAMAKRISHNAN COLLEGE OF ENGINEERING
SAMAYAPURAM, TRICHY-621112
DEPARTMENT OF ECE
VISION
MISSION
M1. To equip the students with latest technical, analytical and practical knowledge
M2. To provide vibrant academic environment and Innovative Research culture
M3. To provide opportunities for students to get Industrial Skills and Internships to
meet out the challenges of the society.
PEO1: Graduates will become experts in providing solution for the Engineering
problems in Industries, Government and other organizations where they are
employed.
II
PROGRAM SPECIFIC OUTCOMES (PSO’S)
PO5: Modern tool usage: Create, select, and apply appropriate techniques,
resources, and modern engineering and IT tools including prediction and modeling
to complex engineering activities with an understanding of the limitations.
PO6: The engineer and society: Apply reasoning informed by the contextual
III
knowledge to assess societal, health, safety, legal and cultural issues and the
consequent responsibilities relevant to the professional engineering practice.
PO7: Environment and sustainability: Understand the impact of the
professional engineering solutions in societal and environmental contexts, and
demonstrate the knowledge of, and need for sustainable development.
PO8: Ethics: Apply ethical principles and commit to professional ethics and
responsibilities and norms of the engineering practice.
PO12: Lifelong learning: Recognize the need for, and have the preparation and
ability to engage in independent and lifelong learning in the broadest context of
technological change.
IV
CO-PO MAPPING FOR PROJECT WORK – EC8811
CO2: Identify, formulate real time problems and find solutions by applying
engineering concepts.
CO3: Implement the design in hardware and verify the performance of the design
using modern simulation tools.
V
K. RAMAKRISHNAN COLLEGE OF ENGINEERING
BONAFIDE CERTIFICATE
VI
DECLARATION
ASSOCIATE PROFESSOR,
ENGINEERING.
VII
ACKNOWLEDGEMENT
We thank the Almighty GOD, without whom it would not have been possible
for us to complete our project.
We wish to address our profound gratitude to our Chairman
Dr. K. RAMAKRISHNAN, [Link] College of Engineering, who
encouraged & gave us all help throughout the course.
We would like to express our sincere thanks to our Executive Director
Dr. S. KUPPUSAMY for forwarding us to do our project and offering adequate
duration in completing our project.
We also grateful to our Principal Dr. D. SRINIVASAN, for his constructive
suggestions and encouragement during our project. We wish to express our profound
thanks to [Link], Professor & Head of the Electronics and
Communication Engineering Department, for providing all necessary facilities for
doing this project.
We whole heartedly and sincerely acknowledge our deep sense of gratitude
and indebtedness to our beloved guide Dr. P. SATHEESLINGAM, Assistant
professor, Electronics and Communication Engineering Department,
Tiruchirappalli, for her expert guidance and encouragement throughout the
duration of the project.
We extend our gratitude to all the FACULTY MEMBERS of Electronics and
Communication Engineering Department, for their kind help and valuable support
to complete the project successfully. We would like to thank our parents and
friends who have always been a constant source of support in our project
VII
I
ABSTRACT
IX
TABLE OF CONTENTS
ABSTRACT IX
LIST OF FIGURES XII
INTRODUCTION 1
1.1 WORKSPACE 2
1.2 APP STUDIO 2
1.
1.3 DEV STUDIO 2
1.4 ADMIN STUDIO 3
1.5 PREDICTION STUDIO 4
2. LITERATURE SURVEY 5
3. EXITING SYSTEM 7
PROPOSED WORK 9
4. 4.1 MODULES 11
4.2 PROCESS OVERVIEW 12
4.3 FLOW DIAGRAM 13
4.4 ADVANTAGES 16
X
RESULT AND DISCUSSION 17
5. 5.1 MODULE DESCRIPTION 17
5.2 MODULE 1 OUTPUT 17
5.3 MODULE 2 OUTPUT 19
5.4 MODULE 3 OUTPUT 21
5.5 MODULE 4 OUTPUT 23
5.6 MODULE 5 OUTPUT 23
5.7 MODULE 6 OUTPUT 25
7. REFERENCES 27
XI
LIST OF FIGURES
XII
CHAPTER 1
INTRODUCTION
13
problem, hiding the implementation and visualizing the business logic for others to consume.
With patterns for reuse and extension built into the Pega platform, developers can build a
solution once and leverage it many times throughout the entire ecosystem.
1.1 WORKSPACES
In App Studio, users can quickly build from a business case by developing a
working outline of the process to be performed in the application. This outline eases
collaboration across technical and business members of the team. The studio also
supports real-time UI design as you process work. For example, a team testing the end-
user interface of an online shopping application can add new fields and make changes to
controls. This ability is helpful for reviews with stakeholders, who can see their feedback
implemented in real [Link] Studio supports the Pega Express methodology to help you
visualize key factors of the desired business process. As you outline the process, you can
14
draft relationships between stages of the process, participating personas, channels of
communication, and data required for process resolution.
15
their usage.
16
CHAPTER 2
LITERATURE SURVEY
There are many ways to design and implement a vehicle purchasing application.
This chapter covers various literature studies that provide insights into building digital
platforms for vehicle sales using different technologies, along with some of the
In 2019, Rajkumar, A.; Deepika, S.; and Naveen, R. proposed the “Online
Vehicle Management System”, which focused on streamlining the process of buying
and selling vehicles using a PHP-based web application. The system allowed customers
to search for available vehicles, view details, and contact sellers directly. However, the
system lacked automation in backend processing and did not offer a structured workflow
for handling approvals, document verification, or delivery tracking, limiting its scalability
for enterprise use.
In 2021, Rahul M., Sneha T., and Gokul R. developed “Vehicle Showroom
Automation Using IoT”, which focused on integrating smart sensors to automate vehicle
17
stock monitoring and inventory management. Although innovative, the solution primarily
dealt with physical inventory and hardware automation. It did not cover the digital
vehicle purchase journey from a customer's perspective, such as document uploads,
payment processing, or delivery tracking.
In 2017, Ramesh, K. and Aruna, B. introduced “Car Lease and Sales Management
System” developed using Python and SQLite. The system allowed users to either buy or
lease cars through a simple GUI interface. While functional, it lacked support for
promotional pricing, did not use modular design principles, and was not scalable for use
in large multi-branch organizations.
18
CHAPTER 3
EXISTING SYSTEM
The present scenario for buying vehicles typically involves customers physically
visiting automobile showrooms, interacting with sales representatives, and
manually comparing different vehicle models. The process often requires multiple
visits to complete test drives, understand pricing, verify documents, and finalize
payments. Transactions are primarily handled at the dealership, either through
traditional paperwork or limited digital support, often restricted to simple booking
forms or inquiry submissions.
This traditional approach is not user-friendly for all, as it demands considerable
time, effort, and coordination. Customers have to depend heavily on verbal
information from sales staff, and there is limited access to detailed vehicle
specifications, promotional offers, or real-time availability. Many customers also
face difficulties in locating nearby branches or dealerships with suitable options,
especially in areas where access to high-quality showrooms is limited.
In some existing systems, car dealerships have developed web-based applications
using technologies like JSP or PHP with MySQL databases. These platforms offer
basic online browsing and booking capabilities. However, such systems generally
lack deeper automation features, offer poor integration with backend dealership
operations, and do not support a complete end-to-end purchase process.
Moreover, these platforms often require extensive manual coding and testing,
making them less flexible and harder to maintain or scale.
Furthermore, these systems typically do not support real-time pricing, automatic
offer generation, document verification, or dynamic workflows. Customers may
still be required to visit the dealership in person to submit documents or complete
payments, reducing the effectiveness of the digital experience.
19
CHAPTER 4
PROPOSED SYSTEM
4.1 MODULES
Registration
A new user will have to register in the system by providing
essential details in order to view the products in the system.
Login
A user must login with his user name and password to the system
after registration.
View Products
User can view the list of products based on their names after
successful login. A detailed description of a particular product with product
name,products details, product image, price can be viewed by users.
Search Product
Users can search for a particular product in the list by name.
21
Add to Cart
The user can add the desired product into his cart by clicking
add to cart option on the [Link] can view his cart by clicking on the cart
button. All products added by cart can be viewed in the cart.
Feedback
User can give their reviews about their purchase.
MANAGER
Manages the overall process. Responsible for confirming and
fulfilling the orders received, managing the deliveries and also for processing
order cancellations.
Order Confirmation
Manager can view the Orders which is generated by the users.
He/She can verify the details of the purchase and confirms the order.
Order Cancellation
Manager can cancel the order if the order is in out of stock.
Placing an order
This application lets the user choose products from a variety of
options. Users can browse through the items based on category. The details of the
products available with specifications are uploaded by the seller. Sellers provide
the following information about the product - Price, Description, Features &
details, Category. Once the items are chosen, user can proceed for payments. This
would require the user to provide additional information like shipping address,
22
mode of payment and other details to complete the [Link] can then add
the items they are interested to purchase into a cart. It is important to note that the
user needs an account otherwise he needs to create an account to add items into
the cart and make purchases.
Order Fulfillment
After receiving the order, the manager confirms it and proceeds for
packaging and shipment. After users’ orders are received and confirmed, the
manager takes charge of fulfilling them.
Shipment
The manager makes sure that the product is delivered to the destination
[Link] manager starts the shipment process after validating the user’s
payment method and order [Link] this stage, the order is given one of the three
different statuses such as pending , shipped etc.,
Order Cancellation
Buyers can cancel their orders any time before the product is
[Link] user can cancel their own orders within a stipulated amount of time.
After that, the user can request for a cancellation and the manager cancels the
request. The user and the manager must also provide the reasons for the
cancellation.
Return Order
Buyers can request for return the products if not interested or The user
can go for a return the order in case the item received is physically damaged,
missing parts or accessories, different from their description on the product detail
page, and defective/does not work properly.
LOGIN /SIGN UP
EXISTING USER
If user is an existing user , they can login with their username and
password which is stored in the database. A user must login with his user name
and password to the system after registration. If they are invalid, the user not
allowed to enter the system.
NEW USER
If user is a new user, they can fill their details and set a password to
login to the application again.A new user will have to register in the system by
providing essential details in order to view the products in the system.
24
Figure : 4.2 Login / SignUp flow
REQUIREMENTS
Username and password will be provided after user registration
is confirmed. Password should be hidden from others while typing it in the
[Link] must be able to verify and validate [Link] system must
encrypt the password of the customer to provide security.
PRODUCTS
The user can able to view the products details such as product
id,product name , product image,price, they can also able to choose the quantity
what they [Link] on the quantity , Gross total will be calculated
automatically by using declare expression rule. The user can add the
desired product into his cart by clicking add to cart option on the product. He can
view his cart by clicking on the cart [Link] products added by cart can be
viewed in the cart. After confirming the items in the cart the user can submit the
cart by providing a delivery address.
25
Figure 4.3 : Product Flow
REVIEW PRODUCTS
After the selecting the products , they can review the selected
[Link] this review product total amount will be displayed including shipping
cost and tax amount .Now the payment process will be proceed.
PAYMENT
Payment can be done through different modes such as UPI , Credit Card, debit
card, netbanking etc…
The user needs to pay the amount, so it can be done using different methods
such as UPI,credit card,debit card,netbanking.
For UPI the user can scan the QR code and pay the amount. For debit card and
credit card ,the user should enter the card’s number,CVV number and expiry
date of their card. For netbanking , the user can choose their bank account and
pay the amount.
REQUIREMENTS
The details which given in the payment process should be verified by
validating that the card number must be of 12 digits and CVV number should be
of 3 digits and the expiry date should be in future date not the past date.
26
Manager will view the selected products and he/she will decide
whether the order will be approved or [Link] the order is approved, manager
will assign the delivery date and the approval mail will be sent to the user. If the
order is rejected, rejection mail will be sent to the user.
SHIPMENT PROCESS
After users orders are received and confirmed, the manager takes
charge of fulfilling them. The manager starts the shipment process after validating
the user’s payment method and order [Link] this process , user can view the
details of the shipment process and status of the [Link] user can also track
the package.A wait shape is implemented to check the status of the shipment
[Link] the product is shipped mail is sent to the [Link] user can also
cancel the order if they are not satisfied. In the cancellation process , user can
give the reason to cancel the order.
FEEDBACK
The buyer can provide his feedback for the items purchased. This
feedback can be useful for other users to make purchases accordingly. The user is
given an option - write a review or by giving the star ratings.
4.4 ADVANTAGES
27
CHAPTER 5
RESULTS AND DISCUSSIONS
28
obtained using pega.
A. EXISTING USER
Figure 5.1 represents the output of the existing user logging an
account.
B. NEW USER
Figure 5.2 represents the output of the new user registering into an
account and Figure 5.3 represents the output of the users address details.
29
Figure 5.2 : New User Details
30
A. PRODUCT CATEGORY
Figure 5.4 represents the output of the category of the
products and Figure 5.5 represents the products in the category.
31
Figure 5.4 : Category of the products.
32
B. REVIEW PRODUCTS
33
[Link] MODE
34
5.5 MODULE 4 OUTPUTS
Figure 5.10 represents the output of the order details and the
figure 5.11 represents the output of the cancellation of the order in the shipment
process.
35
Figure 5.10 : Order Details
36
5.7 MODULE 6 OUTPUTS
Figure 5.12 represents the output of the feedback of the customer for
their orders.
37
CHAPTER 6
CONCLUSION AND FUTURE SCOPE
6.1 CONCLUSION
38
REFERENCE
[1] [Link]
your-locales.
[2] [Link]
Volume-11/[Link]
39
[8] M. R. Sawant, K. Krishnan, S. Bhokre, and P. Bhosale, “The rfid based
smart shopping cart,” International Journal of Engineering Research and General
Science, vol. 3, no. 2, pp. 275-280, 2015.
[10] White paper on “Online Shoppers and Buyers”, February 2013, Canada
Post
40
41