0% found this document useful (0 votes)
6 views41 pages

Vehicle Purchase Application Report

The document is a project report submitted by Muthukumaran R and Nandhakumar K for their Bachelor's degree in Electronics and Communication Engineering at K. Ramakrishnan College of Engineering. It presents the 'True Vehicle Purchase System', an application designed to automate and streamline the vehicle purchasing process, enhancing efficiency and customer experience. The report outlines the project's objectives, methodologies, and educational outcomes, along with acknowledgments and a structured table of contents.

Uploaded by

Sakthivel Nk
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views41 pages

Vehicle Purchase Application Report

The document is a project report submitted by Muthukumaran R and Nandhakumar K for their Bachelor's degree in Electronics and Communication Engineering at K. Ramakrishnan College of Engineering. It presents the 'True Vehicle Purchase System', an application designed to automate and streamline the vehicle purchasing process, enhancing efficiency and customer experience. The report outlines the project's objectives, methodologies, and educational outcomes, along with acknowledgments and a structured table of contents.

Uploaded by

Sakthivel Nk
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

APPLICATION FOR PURCHASE

VEHICLE

A PROJECT REPORT

Submitted by

MUTHUKUMAR. R (Reg. No. 8115U21EC109)

NANDHAKUMAR. K(Reg. No. 811519106146)

in partial fulfillment for the award of the

degree of

BACHELOR OF ENGINEERING

IN

ELECTRONICS AND COMMUNICATION


ENGINEERING

K. RAMAKRISHNAN COLLEGE OF ENGINEERING

(AUTONOMOUS)

SAMAYAPURAM

MAY 2025

I
K. RAMAKRISHNAN COLLEGE OF ENGINEERING
SAMAYAPURAM, TRICHY-621112
DEPARTMENT OF ECE
VISION

To be distinguished as a prominent program in Electronics and


Communication Engineering Studies by preparing students for Industrial
Competitiveness and Societal Challenges.

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.

PROGRAM EDUCATIONAL OBJECTIVES (PEO’S)

PEO1: Graduates will become experts in providing solution for the Engineering
problems in Industries, Government and other organizations where they are
employed.

PEO2: Graduates will provide innovative ideas and management skills to


enhance the standards of the society by individual and with team works through
the acquired Engineering knowledge.

PEO3: Graduates will be successful professionals through lifelong learning and


contribute to the society technically and professionally.

II
PROGRAM SPECIFIC OUTCOMES (PSO’S)

PSO1: Students will qualify in National level Competitive Examinations for


Employment and Higher studies.
PSO2: Students will have expertise in the design and development of Hardware
and Software tools to solve complex Electronics and Communication
Engineering problems in the domains like analog and digital electronics,
embedded and communication systems.
PROGRAM OUTCOME

PO1: Engineering knowledge: Apply the knowledge of mathematics, science,


engineering fundamentals, and an engineering specialization to the solution of
complex engineering problems.

PO2: Problem analysis: Identify, formulate, review research literature, and


analyze complex engineering problems reaching substantiated conclusions using
first principles of mathematics, natural sciences, and engineering sciences.

PO3: Design/development of solutions: Design solutions for complex


engineering problems and design system components or processes that meet the
specified needs with appropriate consideration for the public health and safety, and
the cultural, societal, and environmental considerations.

PO4: Conduct investigations of complex problems: Use research-based


knowledge and research methods including design of experiments, analysis and
interpretation of data, and synthesis of the information to provide valid
conclusions.

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.

PO9: Individual and Team Work: Function effectively as an individual, and as


a member or leader in diverse teams, and in multidisciplinary settings.

PO10: Communication: Communicate effectively on complex engineering


activities with the engineering community and with society at large. Some of
them are, being able to comprehend and write effective reports and design
documentation, make effective presentations, and give and receive clear
instructions.

PO11: Project Management and Finance: Demonstrate knowledge and


understanding of the engineering and management principles and apply these to
one’s own work, as a member and leader in a team, to manage projects and in
multidisciplinary environments.

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

After successful completion of this course, the students should be able to

CO1: Apply knowledge of basic science and engineering to electronics and


communication engineering problems.

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

Certified that this project report “APPLICATION FOR PURCHASE


VEHICLE” is the bonafide work of “MUTHUKUMAR R,
N A N D H A K U M A R K ” who carried
out the project work under my supervision

Dr.M. MAHESWARI M. Tech, Ph.D., Dr. P. SATHEESLINGAM M.E., Ph.D.,


HEAD OF THE DEPARTMENT SUPERVISOR
PROFESSOR ASSOCIATE PROFESSOR

Department of Electronics and Department of Electronics and


Communication Engineering, Communication Engineering,
K. Ramakrishnan College of K. Ramakrishnan College of
Engineering, Samayapuram, Engineering, Samayapuram,
Trichy – 621112. Trichy – 621112.

Submitted for the project Viva-Voce held at K. Ramakrishnan College


of Engineering on .

INTERNAL EXAMINER EXTERNAL EXAMINER

VI
DECLARATION

We hereby declare that the work entitled “APPLICATION FOR


PURCHASE VEHICLE” is submitted in partial fulfillment of the requirement of
the award of the degree in B.E., K. Ramakrishnan college of Engineering, Trichy is
a record of our own work carried out by us during the academic year 2024-2025
under the supervision and guidance of Dr. P. SATHEESLINGAM Associate
Professor, Department of ELECTRONICS AND COMMUNICATION
ENGINEERING, K. RAMAKRISHNAN COLLEGE OF ENGINEERING. The
extent source of information is derived from the existing information are derived
from the existing literature and have been indicated through the dissertation at the
appropriate places. The matter embodied in this work is original and has not been
submitted for the award of any degree or diploma, either in this or any other
University.

MUTHUKUMAR. R (Reg. No. 8115U21EC109)

NANDHAKUMAR. K (Reg. No. 8115U21EC110)

I certify that the declaration made above by the candidate is true.

Dr. P. SATHEESLINGAM M.E., Ph.D.,

ASSOCIATE PROFESSOR,

DEPARTMENT OF ELECTRONIC AND


COMMUNICATION

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

Buying a vehicle has traditionally been a time-consuming process


involving multiple steps, paperwork, and coordination between
customers and dealership staff. With advancements in digital
technology, businesses in the automotive sector are increasingly turning
toward automated platforms to simplify and enhance the vehicle
purchasing experience. “True Vehicle” is one such application designed
to automate and streamline the process of buying vehicles from True
Vehicle, a New York-based authorized dealer of Velo Inc. vehicles. The
application allows customers to browse through a comprehensive
catalog of available new and used vehicles, view specifications, compare
models, and select the vehicle they wish to purchase. Customers can also
view ongoing promotions and pricing offers applicable to specific
models. The system facilitates the end-to-end process including
capturing customer details, selecting vehicle configurations, generating
offers, uploading necessary documentation, and confirming the
purchase. Upon order confirmation, customers receive an automated
notification with order and delivery details. The “True Vehicle Purchase
System” enhances operational efficiency, minimizes manual errors, and
ensures a seamless experience for customers and dealership staff alike.
The solution has been implemented using Pega Platform version 24.2,
leveraging its advanced case management, process automation, and user
interface capabilities. This application has been initially developed for
the True Vehicle Manhattan branch and is designed to be scalable for
future rollout to other branches across New York. With just a few simple
steps, customers can now buy their preferred vehicle with ease and
confidence, backed by an intelligent and responsive digital system.

IX
TABLE OF CONTENTS

CHAPTER NO TITLE PAGE NO:

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

6. CONCLUSION AND FUTURE SCOPE 26

7. REFERENCES 27

XI
LIST OF FIGURES

FIGURE NO FIGURE NAME PAGE NO

4.1 FLOW DIAGRAM 13


4.2 LOGIN / SIGN UP FLOW 14

4.3 PRODUCT FLOW 14

5.1 EXISTING USER 16

5.2 NEW USER DETAILS 18

5.3 ADDRESS DETAILS 19

5.4 CATEGORY OF THE PRODUCTS 20

5.5 PRODUCTS IN THE CATEGORY 20

5.6 REVIEW PRODUCTS 21

5.7 PAYMENT VIA UPI 22

5.8 PAYMENT VIA CREDIT CARD 22

5.9 MANAGER APPROVAL 23

5.10 ORDER DETAILS 24

5.11 ORDER CANCELLATION 24

5.12 FEEDBACK OF THE CUSTOMER 26

XII
CHAPTER 1

INTRODUCTION

Pegasystems Inc. is an American software company based in Cambridge,


Massachusetts. Founded in 1983, Pegasystems develops software for customer relationship
management (CRM) and business process management (BPM). Alan Trefler founded
Pegasystems in 1983 at the age of 27, in Cambridge, Massachusetts. Prior to founding the
company, in the early 1980s Trefler had developed computer systems that could play chess.
Trefler recollects that when he started Pegasystems, he wanted to create software for business
people, how business-people wanted things to work.. Pega is a low-code platform for
workflow automation and AI-powered decisioning. Pega's low-code technology allows you to
build an application that captures data and initiates business [Link] power of Pega's
low-code technology allows you to create an application where you can interact with your
users in the channel of their choice. With omni channel development capabilities, organizations
can unify their development activities for all the required channels rather than maintain
disparate lines of code. Users are a great source for data, but the data that is needed is often
located in another system. Through a visual interface, Pega Platform empowers users to build
integrations to these systems to obtain the data necessary to drive the process forward. Pega
Platform assists users by graphically mapping data into their application for a holistic view of
the data landscape. Pega's visually-driven, end-to-end application development tools make
everyone more productive — citizen developers and professional developers alike. While low-
code enables the non-developer to create application code, it also allows the experienced
developer to write code more rapidly and [Link] enable citizen developers with
additional functionality to meet your organizational needs, Pega Platform application
development studios enable developers to dive deeper to craft a solution to the business

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 Pega Platform, you can improve productivity by using role-based


workspaces. Users see what they need when they need it. For example, front-end
developers can design interface channels in one workspace, while system
administrators can switch between workspaces as they configure advanced
functionality and monitor run-time results.
Pega Platform™ provides four role-based authoring workspaces, known studios:
 App Studio
 Dev Studio
 Prediction Studio
 Admin Studio

1.2 APP STUDIO

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.

1.3 DEV STUDIO

In Dev Studio, implementation experts access rule forms directly to


address complex or less-common configuration requirements. In addition, Dev Studio
provides features for configuring security permissions and access control, managing rules
to promote reuse, and addressing the performance limitations of an application. By
providing two development environments, Pega Platform supports each group of
application developers with an environment tailored to their skill level and optimized for
the tasks they [Link] Studio contains tools that you can use to develop advanced
aspects of your application in a convenient, low-code way. In many scenarios, Dev
Studio expands the possibilities that App Studio offers, so that you can create
applications for unique, complex, and less common business processes. Dev Studio
combines access to all of the capabilities that you might need when you create an
application, such as case management, security, reporting, mobile, and UI, so that you
can provide end-to-end digital solutions for your projects

1.4 ADMIN STUDIO

Admin Studio is a workspace for system administrators, database


administrators, and security administrators that provides run time information and
configuration options for system [Link] Admin Studio, you can observe system
execution at run time, such as monitoring job schedulers and queue processors, and
managing system nodes. For example, as part of a software audit, a developer uses
Admin Studio to identify active requestors, both human and system users, and monitor

15
their usage.

1.5 PREDICTION STUDIO

Prediction Studio is a Pega Platform workspace in which users


create prediction models. For example, data scientists or decision analysts design and
create analytical models. The analytical models created in Prediction Studio can also be
used with Dev Studio and App Studio as part of the case type life cycle for decision-
making, such as when rules. Adding the pxPredictionStudio portal to your access group
gives you access to Prediction Studio; however, the appropriate role should be added to
perform the desired operations. Prediction Studio has four work areas: Predictions,
Models, Data, and Settings. The workspace also provides data scientists everything they
need to author, deploy, govern, monitor, and change AI models. The header at the top of
Prediction Studio enables you to view the name of the current application, perform a
search across the rules in that workspace, view the online help, and toggle the Agile
Workbench.

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

limitations observed in each approach.

In 2015, K. Aarthi, S. Prabha, and R. Gopalakrishnan presented a paper


titled “Automated Vehicle Showroom Management System”, which proposed an
application developed using Java and MySQL. The system allowed customers to view
different vehicle models, submit booking forms, and receive a basic confirmation. While
it improved customer engagement, the system lacked integration with pricing algorithms,
case management features, and dynamic offer generation, which are critical for real-time
dealership operations.

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 2018, Shaikh, M. and Joshi, A. proposed “Online Car Booking System”,


implemented using [Link]. This application included modules for vehicle search,
booking, and user registration. While the system supported customer-side operations, it
did not cater to dealership-side workflows such as approval processes, automated
notifications, or compliance checks—features that are essential for a full-fledged
commercial dealership.

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

In the proposed system, customers need not visit the vehicle


showroom to purchase a car. They can now explore, select, and purchase their
desired vehicle through the True Vehicle Purchase System using their
smartphones or computers from the comfort of their home. The dealership
administrator (admin) will oversee the system, and staff members can be assigned
specific roles to manage orders, customer queries, and documentation. The system
will also support notifications and allow for scheduling home delivery or branch
pick-up of the purchased vehicles.
With the rise in internet usage and smart devices, digital
vehicle purchases are becoming more convenient and attractive to customers.
Through this Pega-based application, customers can compare different vehicle
models, check specifications, apply filters, and explore promotional offers before
finalizing their purchase. The system is designed to ensure easy navigation, a
secure payment gateway, and real-time order tracking.
Online vehicle purchasing offers numerous advantages,
including time savings, transparent pricing, instant access to promotional
discounts, and the ability to review extensive model details and availability. The
proposed application will be implemented using Pega Platform version 24.2,
known for its low-code capabilities, case management, and user-friendly
interface. This ensures both flexibility and faster development cycles to match
evolving business requirements.
Customers can use the application to search for specific
vehicle models by make, price, or type. The system allows easy account
registration, viewing of vehicle listings, and order placement. Payment options
will include net banking, debit/credit cards, and financing offers where applicable.
20
Once the purchase is confirmed, the admin processes the order, arranges for
documentation, and schedules delivery or branch pickup. Notifications will be
sent via email or SMS to keep the customer updated throughout.

4.1 MODULES

The system after careful analysis has been identified to be presented


with the following modules.
 Customer
 Manager
 CUSTOMER
A Customer can searches through and selects from the items
available. Places an order if interested and makes payments.

 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.

4.2 PROCESS OVERVIEW

 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.

4.3 FLOW DIAGRAM


23
Figure 4.1 : Flow Diagram

 LOGIN /SIGN UP

 User can Login / Sign up using their credentials.

 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.

 After login, they have to enter their address details.

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.

 MANAGER APPROVAL / REJECTION

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

 User friendly application


 Send surprise gifts easily
 Saves time and efforts
 Convenience of shopping at home
 Saves money
 Comparison of products
 Read reviews of the products

27
CHAPTER 5
RESULTS AND DISCUSSIONS

5.1 MODULE DESCRIPTION

 Module 1: Register or login into an account.


 Module 2: Choosing the products.
 Module 3: Completing the payment process.
 Module 4: Fulfillment of orders.
 Module 5: Shipment Process.
 Module 6 : Review of the order.

In module 1, the output for the user login an account process is


obtained using pega. In module 2, the output for the selection of products in various
category is obtained using pega. In module 3, the output for the payment process using
different modes is obtained using pega. In module 4, the output for the manager
approval or rejection of orders is obtained using pega. In module 5, the output for the
shipment and tracking of orders is obtained. In module 6, the output of the feedback is

28
obtained using pega.

5.2 MODULE 1 OUTPUTS


The module 1 consists of the outputs for the login an account of
existing user and new user.

A. EXISTING USER
Figure 5.1 represents the output of the existing user logging an
account.

Figure 5.1: Existing User

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

Figure 5.3 : Address Details

5.3 MODULE 2 OUTPUTS


The module 2 consists of output of the product category , the
products in the category and the selected products for review .

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.

Figure 5.5 : Products in the category.

32
B. REVIEW PRODUCTS

Figure 5.6 represents the output of the selected


products to be reviewed.

Figure 5.6 : Review Products

5.4 MODULE 3 OUTPUTS

In this module , different payment modes outputs are


obtained. Figure 5.7 represents the output of the UPI Payment mode and
Figure 5.8 represents the output of the Credit Card Payment mode.

33
[Link] MODE

Figure 5.7 : Payment via UPI

B. CREDIT CARD MODE

Figure 5.8 : Payment via Credit Card

34
5.5 MODULE 4 OUTPUTS

Figure 5.9 represents the output of the managers approval of


the orders

Figure 5.9 : Managers Approval

5.6 MODULE 5 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

Figure 5.11 : Order Cancellation

36
5.7 MODULE 6 OUTPUTS

Figure 5.12 represents the output of the feedback of the customer for
their orders.

Figure 5.12 : Feedback of the customer

37
CHAPTER 6
CONCLUSION AND FUTURE SCOPE

6.1 CONCLUSION

The project entitled Online Gift Store was completed


[Link] system has been developed with much care and at the same time
it is efficient and less time consuming. The purpose of this project was to develop
an application for purchasing items from a shop.
This project helped us in gaining valuable information and practical
knowledge on several topics in pega like report definition, repeating dynamic
layout,UI,etc.,This system will help customers in ordering custom gifts. So the
customer will pick exactly the things which he/she wants in their gifts. This will
surely enhance the image of the gift shop and customer satisfaction will be more.
This project has given us great satisfaction in having designed an application
which can be implemented to any nearby shops or branded shops selling various
kinds of products by simple modifications.

6.2 FUTURE SCOPE

There is a scope for further development in our project to


a great extend.A number of features can be added to this system in future like
providing manager more control over products so that each manager can maintain
their own products. We will host the platform on online servers to make it
accessible worldwide and implementing the backup mechanism for taking backup
of database on regular basis on different servers.

38
REFERENCE

[1] [Link]
your-locales.

[2] [Link]
Volume-11/[Link]

[3] SunWeiQin, The solution on Tomcat and Java Web development of


Technology. [M]. Beijing: publishing house of electronics industry, 2009.1

[4] YeDaFeng, Eclipse programming techniques and examples [M].


Beijing: Posts & Telecom Press : 2207-2232

[5] Raju Kumar, K. Gopalakrishna, K. Ramesha on “Intelligent Shopping


Cart” in International Journal of Engineering Science and Innovative
Technology (IJESIT) Volume 2, Issue 4, July 2013.

[6] 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

[7] A. Yewatkar, F. Inamdar,R. Singh, [Link] etal., “Smart cart with


automatic billing, product information, product recommendation using rfid &
zigbee with anti- theft,” Procedia Computer Science, vol. 79, pp. 793-800, 2016.

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.

[9] Suganya R, Swarnavalli N, Vismitha S, Rajathi GM (2016) Automated


Smart Trolley with Smart Billing Using Arduino. International Journal for
Research in Applied Science & Engineering Technology.

[10] White paper on “Online Shoppers and Buyers”, February 2013, Canada
Post

40
41

You might also like