The Islamia University Of Bahawalpur

CAR MARKET

Final Year Project

Supervisor: <Abdul Kareem Nawaz Sahab>

Presented by:

Student Reg# F20BINFT1E02110

Student Name: Muhammad Nouman

Department of Information Technology (DIT)

The Islamia University Of Bahawalpur
 CAR MARKET

By

Muhammad Nouman

Project submitted to

Department of Information Technology,

The Islamia University of Bahawalpur.

in partial fulfillment of the requirements for the degree of

BACHELOR OF SCIENCE
IN
INFORMATION TECHNOLOY (BSIT)

Supervisor Signature In- Charge Examination Signature

Chairman, Department of Information

Technology
Abstract
Car Market (CM) provides users with an online dealing management system according to their
needs which makes deals in cars or buying and selling car parts very easy and efficient. This
system includes three user types which are admin, seller, and buyer. The platform features
several filters to find the best service for your use. The admin reviews the services and
approves/reject them as he deems fit. The system also provides chat support for better
communication between buyers and sellers.

Problem Statement:
The traditional car dealing process is time consuming and difficult. It’s not easy to find all the
spare parts you need at one place. Even if you do, you must search in the market and get them.
Which requires a lot of time.

Objectives:
The objective is to build a platform for users that makes the process of buying/selling spare parts
and cars in very convenient and fast way. Customers are searching by different filters, which
allows them to search for the services and products according to their needs. A user-friendly and
secure marketplace that facilitates the user with advance booking, buying, selling and
communication between buyer and seller.

Scope
Admin
• Admin can register in the system.
• Admin can disable accounts, products, and services.
• Approves/Reject dealing services.
• Manages Categories.
• Review Reports.
Seller
• Seller can login to their account.
• Seller has access to seller dashboard.
• Seller can add/update/delete his/her services, products.
• View services and orders received.
• Can buy other seller products.
• Can report chat of other users.
• Manage account settings.

Conclusion:
Our goal is to provide companies and people with web-based platform to provide easy and
effective solution for dealing vehicles, and buying/selling parts all at one place.

i
 Acknowledgement
< The successful testing and evaluation of this website would not have been possible
without the contributions of several individuals and resources. We would like to express
our sincere gratitude to the following:

 The Development Team: Their dedication to building the core functionalities of the
website is acknowledged. Their work forms the foundation upon which a successful
online store can be established.
 The Design Team: Their efforts in creating a user-friendly and visually appealing
interface are appreciated. Their focus on usability contributes significantly to a positive
customer experience.
 The Testing Team: Their meticulous testing efforts are a key factor in identifying
potential issues and ensuring a smooth user experience for customers. Their dedication
to quality assurance is commendable.
 Management: Their vision and support throughout the testing process are
appreciated. Their commitment to providing a reliable and functional ecommerce
platform is recognized.
 External Resources: Any external tools, libraries, or consulting services utilized during
testing should be acknowledged here.

We would also like to extend our thanks to any internal stakeholders or individuals who
provided valuable feedback or participated in the testing process. Their contributions
helped refine the testing scope and ensure a comprehensive evaluation.

By acknowledging these key players, we recognize the collaborative effort that goes into
building and testing a successful website.>

ii
List of Figures:
Here are some lists of Figures:
1. Schematic Representation of the Online Car Parts Marketplace System:
 Illustrates the overall architecture and flow of the online platform.

2. Flowchart depicting the User Registration Process:

 Visualizes the steps involved in the registration process for users.

3. Dashboard Interface Design for Sellers:

 Displays the user interface designed specifically for sellers to manage their listings and
sales.

4. Dashboard Interface Design for Buyers:

 Shows the user interface tailored for buyers to browse and purchase car parts.

5. Data Visualization of Car Parts Sales Trends:

 Presents visual representations of sales trends over a period.

6. Prototype Design of Search Functionality for Car Parts:

 Demonstrates the interface design for users to search for specific car parts.

7. Comparison Chart of Popular Car Parts Brands:

 Compares different brands of car parts based on popularity or other relevant metrics.

8. Geographic Distribution of Customers Using the Online Marketplace:

 Maps the geographical distribution of users accessing the online marketplace.

9. User Interface Design for Adding New Listings:

 Displays the interface for sellers to add new listings for car parts they want to sell.

10. Feedback and Rating System Interface Design:

 Illustrates the interface for users to provide feedback and ratings for sellers and products.

List of Tables
Here are some lists of tables

iii
List of Car Parts Categories and Subcategories:
Provides a categorized inventory of car parts available for sale.

Pricing Strategy Matrix for Car Parts:

Outlines the pricing strategies employed for different types of car parts.

Seller Registration Information:

 Records details of sellers who have registered on the platform.

Buyer Registration Information:

 Stores information about buyers who have registered on the platform.

Sales Data for Car Parts by Category:

 Summarizes sales data for different categories of car parts.

Comparative Analysis of Shipping Costs:

 Compares shipping costs from different providers for efficient logistics management.

Customer Feedback and Ratings for Sellers:

 Tracks feedback and ratings provided by buyers for sellers' performance.

Inventory Management System Overview:

 Provides an overview of the system used for managing inventory of car parts.

Payment Gateway Integration Options:

 Lists various payment gateway options integrated into the online marketplace.

Summary of Website Traffic Analysis:

 Summarizes website traffic data to analyze user engagement and behavior.

iv
v
TABLE OF CONTENTS
ABSTRACT........................................................................................................................................................ I
ACKNOWLEDGEMENT................................................................................................................................. II
LIST OF FIGURES.......................................................................................................................................... III
LIST OF TABLES............................................................................................................................................ III
CHAPTER 1. INTRODUCTION............................................................................................................................ 1
1.1 INTRODUCTION..................................................................................................................................................1
1.2 OBJECTIVES....................................................................................................................................................... 1
1.3 PROBLEM STATEMENT.........................................................................................................................................1
1.4 SCOPE..............................................................................................................................................................1
CHAPTER 2. REQUIREMENTS ANALYSIS............................................................................................................ 3
2.1 LITERATURE REVIEW...........................................................................................................................................3
2.2 USER CLASSES AND CHARACTERISTICS.....................................................................................................................3
2.3 DESIGN AND IMPLEMENTATION CONSTRAINTS..........................................................................................................3
2.4 ASSUMPTIONS AND DEPENDENCIES........................................................................................................................3
2.5 FUNCTIONAL REQUIREMENTS................................................................................................................................3
2.6 USE CASE DIAGRAM...........................................................................................................................................7
2.7 NONFUNCTIONAL REQUIREMENTS.........................................................................................................................8
2.8 OTHER REQUIREMENTS.......................................................................................................................................8
CHAPTER 3. SYSTEM DESIGN............................................................................................................................ 9
3.1 APPLICATION AND DATA ARCHITECTURE.................................................................................................................9
3.2 COMPONENT INTERACTIONS AND COLLABORATIONS..................................................................................................9
3.3 SYSTEM ARCHITECTURE.......................................................................................................................................9
3.4 ARCHITECTURE EVALUATION.................................................................................................................................9
3.5 COMPONENT-EXTERNAL ENTITIES INTERFACE...........................................................................................................9
3.6 SCREENSHOTS/PROTOTYPE.....................................................................................ERROR! BOOKMARK NOT DEFINED.
3.7 OTHER DESIGN DETAILS.......................................................................................................................................9
CHAPTER 4. TEST SPECIFICATION AND RESULTS.............................................................................................. 10
4.1 TEST CASE SPECIFICATION..................................................................................................................................10
4.2 SUMMARY OF TEST RESULTS..............................................................................................................................10
CHAPTER 5. CONCLUSION AND FUTURE WORK.............................................................................................. 11
5.1 PROJECT SUMMARY..........................................................................................................................................11
5.2 PROBLEMS FACED AND LESSONS LEARNED.............................................................................................................11
5.3 FUTURE WORK.................................................................................................................................................12
REFERENCES..................................................................................................... ERROR! BOOKMARK NOT DEFINED.
APPENDIX A GLOSSARY.............................................................................................................................. 13
APPENDIX B DEPLOYMENT/INSTALLATION GUIDE......................................................................................13

vi
Revision History
Name Date Reason For Changes Version

vii
Chapter 1. Introduction
1.1 Introduction

Online car buying and selling is a convenient way for people to purchase and sell
vehicles through the internet. Instead of visiting traditional dealerships or relying on
classified ads in newspapers, individuals can now use websites and apps dedicated to car
transactions. When buying a car online, you can browse through a wide range of
options, compare prices, and read reviews from other buyers, all from the comfort of
your own home. Sellers can also list their vehicles online, reaching a larger audience and
potentially getting a better price for their cars. With the ease of online payment and
secure transactions, this digital approach to car buying and selling has become
increasingly popular in recent years, offering both buyers and sellers a hassle-free
experience.

1.2 Objectives

The objective of online car buying and selling is to make it easier and more convenient
for people to buy and sell cars using the internet. This means creating digital platforms
where buyers can browse through a wide selection of cars, compare prices, and make
informed decisions from the comfort of their own homes. For sellers, the objective is to
provide a platform where they can list their vehicles and connect with potential buyers,
reaching a larger audience and potentially getting better offers. Overall, the objective is
to simplify and improve the car transaction process by leveraging the power of online
technology, making it more accessible and efficient for everyone involved.

1.3 Problem Statement

The intended audience for online car buying and selling includes individuals who are
looking to buy or sell a car and want to do so through the internet. This can range from
people who are searching for a new or used car for personal use to those who want to
sell their vehicles. It's also for anyone who prefers a convenient and digital approach to
car transactions, where they can explore options, compare prices, and complete the
process online. For those interested in online car buying and selling, I recommend

1
 starting by exploring popular online marketplaces and car listing websites like Auto
trader, Cars.com, or eBay Motors. These platforms offer a wide selection of cars and
provide helpful search filters to narrow down your choices. Additionally, consider
reading online reviews and guides about buying and selling cars online, which can offer
valuable tips and insights on how to navigate the process smoothly and avoid common
pitfalls. It's also a good idea to familiarize yourself with online payment methods and
safety precautions for secure transactions when buying or selling a car online.

1.4 Scope

The scope of online car buying and selling refers to the wide range of activities and
opportunities available through the internet when it comes to purchasing and
selling vehicles. It includes all the different aspects and possibilities related to
buying and selling cars online. For buyers, the scope encompasses the ability to
browse and search for various types of cars, both new and used, from different
sellers and dealerships. They can compare prices, read reviews, and access detailed
information about the vehicles.

Buyers can also explore financing options and insurance quotes online. For sellers,
the scope includes listing their cars for sale on various online platforms, reaching a
broader audience of potential buyers. They can provide detailed descriptions,
photos, and even video tours of their vehicles to attract. interested parties. Online

car selling also allows for negotiation and secure transactions. Overall, the scope
of online car buying and selling extends to the convenience, accessibility, and
efficiency offered by the internet in the entire process of acquiring or selling a
vehicle.

2
Chapter 2. Requirements Analysis
2.1 Literature Review
The car market has undergone a significant transformation with the advent of digital platforms.
Traditional methods of buying and selling cars, which involved visiting multiple dealerships and
engaging in prolonged negotiations, have been increasingly supplemented or even replaced by online
marketplaces. These platforms offer a range of benefits, including convenience, wider selection, and
often better pricing. This literature review explores the current state of online car markets, examining
their evolution, benefits, challenges, and the technologies that support them.

2.2 User Classes and Characteristics

Car Market is the web-based application that is used to retrieve Car information. The
characteristics of this web-based application is that a user can manage allocated
information according to his/her role.

 Admin
 Buyer
 Seller

2.3 Design and Implementation Constraints

Constraints can act as a catalyst for innovation, experiments, and creativity.
Theme:
This is always the main limitation and is often revealed at the start of the event.
Team:
It encourages people to create teams on running
fast working, so you will have to juggle each
person’s strengths and weakness.
Time:
Developer have only (say) specific hours to create an application, this forces the team
to come up with a plan and stick to it throughout the event.

Tools:
This refers to the different types of software that might be available for participants.

2.4 Assumptions and Dependencies

This application is dependent on internet connection. Application features are
accessible only if there is internet connection. Once user login then he/she will get
information of their relevant layouts. Admin, Seller of this website are assumed to
have a laptop or mobile phone. Each user must have a valid email and password.
Every user must login into the website to access relevant layouts.
3
2.5 Functional Requirements
1.User Management

User Registration and Login:

 Users (buyers and sellers) can register by providing necessary details such as name, email, password,
and contact information.
 Users can log in using their email and password.
 Password recovery option via email.

User Profiles:

 Users can create and update their profiles, including personal information and contact details.
 Sellers can add additional information related to their business.
 Product Management

2. Product Listing:

 Sellers can list car spare parts with details such as part name, description, price, brand, model
compatibility, and images.
 Option to add, update, or delete listings.

Product Search and Filter:

 Buyers can search for spare parts using keywords.

 Filters available for categories, brands, models, price range, condition (new/used), and seller ratings.

Product Details:

 Detailed view of each product with all specifications, images, seller information, and reviews.
 Shopping Cart and Order Management

3.Shopping Cart:

 Buyers can add or remove products from the shopping cart.

 View cart with product details, quantity, and total price.

Order Placement:

 Buyers can place orders by providing shipping information and selecting a payment method.
 Order summary and confirmation details.

Order Tracking:

 Buyers can track the status of their orders (e.g., processing, shipped, delivered).

4
Order History:

 Buyers can view their past orders with details such as order date, products, total amount, and status.
 Payment and Transactions

Payment Processing:

 Integration with payment gateways for secure transactions.

 Multiple payment options like credit/debit cards, PayPal, and other online payment methods.

2.5.1 Name of Use-Case 1

Identifier UC-1
Purpose Allow users to create an account on the platform.
Priority High
 The user must have access to the internet.
Pre-conditions
 The user must have a valid email address.
 The user account is created and stored in the
database.
Post-conditions
 The user can log in to the platform using the
registered credentials.
Typical Course of Action
S# Actor Action System Response
The user navigates to the registration
1 The system displays the registration form.
page.
The user fills in the registration form
2 The system validates the entered data.
details (name, email, password, etc.).
The system creates a new user account
3 The user submits the registration form.
and sends a confirmation email.
…
Alternate Course of Action
S# Actor Action System Response
The user enters an already registered The system displays an error message
1 email. indicating the email is already registered.
The system prompts the user to fill in the
2 The user submits an incomplete form.
required fields.
The user enters invalid data (e.g., weak The system displays an error message
3 password). with validation requirements.
…

Table 1: UC-1

2.5.2 Name of Use-Case 2

5
Product Search and Filter

Identifier UC-2
Purpose Allow users to search for and filter car spare parts.
Priority High
 The user must be logged into the platform.
Pre-conditions
 There must be products available in the database
 The user can view a list of products matching the
Post-conditions
search and filter criteria.
Typical Course of Action
S# Actor Action System Response
The system displays the search bar and
1 The user navigates to the search bar.
filter options.
The user enters a keyword in the search The system processes the keyword and
2
bar. searches the product database.
The user applies filters (brand, model, price The system refines the search results
3
range, etc.). based on the selected filters.
The system displays the products
4 The user views the list of filtered products.
matching the search criteria.
Alternate Course of Action
S# Actor Action System Response
The user enters a keyword that yields no The system displays a message indicating
1 results. no products found.
The system displays a message indicating
2 The user applies contradictory filters.
no products match the selected filters.
.

Table 2: UC-2

6
2.6 Use Case Diagram

7
Product Prospective:

Home: The user can visit the car market home page and then show the details about the car market
including Contact detail, details, Car Categories, and Feature Products.

About Us: Users must visit the website to view the About Us page and read details about car
market services. Users can go to the Apply Now page and fill out the admission form
according to his/her program.

Cars: User can view the Car Categories and add the car in the Car Market

Login: Seller and Admin can log in to the Car Market and operate the file successfully.

Contact us: Buyer can view the contact information including address Email and Phone Number

Car Categories: The admin can add Categories and the Seller add the Car and also can view Cars
and Featured Products in the Car Market.

Search Car: Buyers can Search Car Brands select and view the car description.

Update Car: Admin can add the car from his/her dashboard. Admin can also manage car categories
such as add/update/delete.

View Car Detail: Buyers can view the category of the car. Select the car and display the detailed
information of the cart.

Seller: Seller can log in to the account open the dashboard to add the car for selling and provide
details about the car.
Buyer: Buyer can search for the desired cars and view the details of the car then select to buy it.

2.7 2.2 Product Features

This web-based application will support three types of user privileges, Admin, Seller and
Buyer. These roles perform different functions which are as follows:

Admin:

⚫ Login.
⚫ Update his/her profile.
⚫ Approve/Disapprove accounts.
⚫ View New Cars.
⚫ Add/update/delete Cars.

Seller:

8
⚫ Login/Register.
⚫ Approved by Admin.
⚫ Update his/her profile.
⚫ View Cars list.
⚫ Add/update/delete Cars.

Buyer:

⚫ View Home.
⚫ View Cars Categories.
⚫ Select Car and View Car for buy.

User Classes and Characteristics

Car Market is the web-based application that is used to retrieve Car information. The
characteristics of this web-based application is that a user can manage allocated
information according to his/her role.

⚫ Admin
⚫ Buyer
⚫ Seller
Operating Environment
The operating environment for the "Car Market" is MySQL, and PHP for the
implementation of this website. We use JavaScript, jQuery, Ajax PHP, and MySQL for
programming and HTML5, and CSS3 for the designing purposes.
Design and Implementation Constraints
Constraints can act as a catalysts for innovation, experiments, and creativity.

Theme:
This is always the main limitation and is often revealed at the start of the event.

Team:
It encourages people to create teams on run fast working, so you will have to juggle each
person’s strengths and weaknesses.
Time:
Developers have only (say) specific hours to create an application, this forces the team
to come up with a plan and stick to it throughout the event.

Tools:
This refers to the different types of software that might be available for participants.

Assumptions and Dependencies:

This application is dependent on an internet connection. Application features are

accessible only if there is an internet connection. Once the user logs in then he/she
will get information on their relevant layouts.

9
 Admin and Seller of this website are assumed to have a laptop or mobile phone. Each
user must have a valid email and password. Every user must log into the website to
access relevant layouts.

External Interface Requirements

Login Interface: When user open “Car Market” he/she will have to login first then perform
anything.

User Interfaces:
• User must have ―laptop or mobile phone‖ to use the application.
• User have access on any browser like Google Chrome, Internet Explorer etc., to
open web-based application. • If we want to run the application on PC, we will need
a browser.
Hardware Interfaces:
• Only the basic requirements of the system required.
• Computer with Window’s Operating System and Mobile phone with a browser.
Software Interfaces :
• No other specific hardware is required to run this application.
• User just need a mobile phone or laptop to install browser in laptop or mobile phone to
load and view the web pages and operate the web-based application.

Communications Interfaces
NIC: Maybe used for both wired and wireless communications.
TCP/IP: ISP to share and access information over the internet.

2.8 Nonfunctional Requirements

2.8.1 Performance Requirements

Our application performance is reliable in all aspects, it will secure Seller and Buyer data so
that any unauthorized person cannot access it. It will facilitate Seller and Buyer with all his
requirements regarding searching for Car add Car Categories etc. It has a proper record of
Seller for future needs.

2.8.2 Safety Requirements

The data of the user will be fully secured so that unauthorized persons cannot access and
change personal data. The application must be able to link up with the internal system in
order for users to probably log in and identified. This information must be kept secure.

2.8.3 Security Requirements

10
Our application is completely saved from the user’s point of view because the data or record
of each user will not be shared by any unauthorized person, and it will be it private. Each user
must have an ID and password to use this web-based application.

2.8.4 Additional Software Quality Attributes

• Availability
• Correctness
• Maintainability
• Usability

2.9 Other Requirements

Performance:

The system should support 1000+ concurrent users with a response time of less than 2 seconds for
most operations.

Scalability:

The architecture should be scalable to handle increasing loads by adding more servers or resources as
needed.

11
Chapter 3. System Design
3.1 Application and Data Architecture
The application will use a microservices architecture to ensure modularity and scalability, with
services communicating via REST APIs. Data will be stored in a relational database (e.g., MySQL) for
structured data and a NoSQL database (e.g., MongoDB) for flexible data storage needs.

The application will be designed using a microservices architecture to enhance modularity and
scalability, allowing for independent deployment and development of individual services. These
services will communicate via REST APIs, facilitating efficient and standardized data exchange. For
data management, a relational database such as MySQL will be used to handle structured data,
ensuring consistency and reliability, while a NoSQL database like MongoDB will cater to flexible data
storage requirements, accommodating a variety of data types and large volumes of information.

Incorporating a microservices architecture, the application will ensure high modularity and scalability,
enabling seamless independent deployment and maintenance of services. REST APIs will serve as the
communication backbone between services, promoting interoperability and streamlined data transfer.
Data storage will be bifurcated between a relational database (e.g., MySQL) for handling structured
data, which requires transactional integrity, and a NoSQL database (e.g., MongoDB) for managing
flexible data storage needs, supporting diverse data formats and scalability. This approach will provide
a robust, efficient, and adaptable infrastructure for the application.

3.2 Component Interactions and Collaborations

The front-end component interacts with the back-end services via RESTful APIs, enabling operations
like user registration, product search, and order processing. The back-end services collaborate with the
relational database for transactional data and the NoSQL database for storing user-generated content
and product details.

The front-end component leverages RESTful APIs to communicate with the back-end services,
facilitating user registration, product search, and order processing. This interaction ensures a seamless
user experience. On the back end, services work in conjunction with a relational database to manage
transactional data and a NoSQL database to handle user-generated content and product information,
optimizing data storage and retrieval processes.

Through RESTful APIs, the front-end component engages with back-end services to support essential
functions such as user registration, product search, and order processing. This API-driven interaction
promotes efficient data exchange and operational fluidity. Back-end services utilize a relational
database for managing transactional data, ensuring data integrity and consistency. Concurrently, a
NoSQL database is employed to store user-generated content and detailed product information,
enhancing the system's capacity to handle diverse data types and large volumes of information.

3.3 System Architecture

"The system will use a multi-tiered architecture with a presentation layer for web and mobile
interfaces, an application layer with microservices for business logic, and a data layer comprising
relational and NoSQL databases. An API Gateway and Message Queue will handle integration, while
security and infrastructure layers ensure secure and scalable operations.

12
The system's architecture will be multi-tiered, featuring a presentation layer designed for both web and
mobile interfaces, ensuring consistent user experiences across platforms. The application layer will
utilize microservices to manage business logic efficiently, while the data layer will integrate both
relational and NoSQL databases for comprehensive data management. Integration will be managed
through an API Gateway and Message Queue, facilitating seamless communication between
components. Security and infrastructure layers will be crucial in maintaining the system's security and
scalability.

A robust multi-tiered architecture will underpin the system, with a presentation layer catering to web
and mobile interfaces, providing a unified user experience. The application layer will consist of
microservices, delivering modular and efficient business logic management. The data layer will
leverage relational and NoSQL databases, offering flexible and efficient data storage solutions.
Integration will be streamlined through an API Gateway and Message Queue, ensuring efficient
component communication. The security and infrastructure layers will be integral to providing secure
and scalable operations, safeguarding data and ensuring reliable performance."

3.4 Architecture Evaluation

The multi-tiered architecture ensures modularity, making the system scalable and maintainable, while
microservices allow independent development and deployment of components. The use of both
relational and NoSQL databases enhances data management flexibility, and the integration of security
measures ensures robust protection of user data and transactions.

The system's multi-tiered architecture promotes modular design, facilitating scalability and ease of
maintenance. Microservices architecture further allows for independent development and deployment
of various components, enhancing the overall efficiency of the development process. By incorporating
both relational and NoSQL databases, the system achieves superior data management flexibility.
Additionally, robust security measures are integrated to protect user data and ensure secure
transactions.

Leveraging a multi-tiered architecture, the system achieves a high degree of modularity, which
supports scalability and maintainability. The use of microservices enables independent component
development and deployment, streamlining the development cycle. The combination of relational and
NoSQL databases provides versatile data management solutions. Comprehensive security measures are
in place to safeguard user data and transaction integrity, ensuring a reliable and secure user experience.

3.5 Component-External Entities Interface

Creating a seamless 'Component-External Entities Interface' for an online car parts marketplace,
enhancing accessibility and efficiency in sourcing and purchasing automotive spare parts.
The implementation of a comprehensive 'Component-External Entities Interface' revolutionizes the
online car parts marketplace, significantly improving the ease of access and the efficiency of locating
and buying automotive components. This interface streamlines interactions between various system
components and external entities, providing a user-friendly experience.

By integrating a sophisticated 'Component-External Entities Interface,' the online car parts marketplace
achieves unparalleled accessibility and operational efficiency. This innovation facilitates effortless
sourcing and purchasing of automotive spare parts, making the overall process more intuitive and
efficient for users."

13
3.6 Other Design Details
The interface employs intuitive categorization and search algorithms for effortless navigation through a
vast inventory of car components. It incorporates secure payment gateways and real-time inventory
updates, ensuring a smooth and reliable shopping experience for users across diverse automotive
needs.

The system uses advanced search and filtering techniques to help users quickly find the exact car parts
they need. Secure payment integration provides peace of mind during transactions, while continuous
inventory synchronization guarantees up-to-date availability. This creates a seamless and dependable
online shopping environment for a wide range of automotive requirements.

Efficient organization and robust search capabilities simplify browsing through the extensive selection
of car accessories. Integrated secure payment systems enhance transaction safety, and dynamic
inventory management keeps product information current. Users benefit from a streamlined,
trustworthy purchasing process tailored to various automotive demands.".

14
Chapter 4. Test Specification and Results
4.1 Test Case Specification

Identifier TC-1
Related requirements(s) Login
Short description The test case will determine the correct functionality of the login
Pre-condition(s) The user record must exist in the system
1. Enter username, and password and select user type.
Input data
2. Press the Login button
Detailed steps …
1. The user is login to the system in case of correct
information.
Expected result(s)
2. The system shows error message in case of incorrect
credentials
Post-condition(s) The user is successfully log in to the system.
The user was able to log in successfully with correct credentials. An
Actual result(s)
error message was displayed when incorrect credentials were used.
Test Case Result Successful Login

Table 6.1: TC-1

4.2 Summary of Test Results

Number of defects Number of The number of

found defects corrected defects still
Module Name Test cases run
so far needs to be
corrected
User Authentication 1 1 0
TC1
(Login)
Product Search TC-2 0 0 0
Add to Cart TC-3 0 0 0
Checkout Process TC-4 1 0 1
Complete System TC-1, TC-2, TC-3, 2 1 1
TC-4

Table 6.2: Summary of All Test Results

15
Chapter 5. Conclusion and Future Work
5.1 Project summary
The project involves developing an online marketplace for selling car spare parts, providing functionalities for
user authentication, product search, adding items to the cart, and completing purchases. The system aims to
streamline the process of buying and selling spare parts, ensuring ease of use and efficient transaction handling
for users.

5.2 Problems faced and lessons learned

Problems Faced:
 Integration Issues: Integrating various modules like user authentication, product search, and
checkout was challenging due to compatibility issues and ensuring seamless data flow between
components.

User Authentication:
 During testing, we encountered issues with the login functionality, specifically handling
incorrect credentials and session management.

Checkout Process:
 We faced a defect in the checkout process where the payment gateway integration was
unstable, causing transaction failures.

Performance Optimization:
 Ensuring the application could handle a large number of simultaneous users without slowing
down required extensive performance testing and optimization.

Lessons Learned:
Thorough Testing:
 Comprehensive testing, including unit, integration, and system testing, is crucial for identifying
and resolving defects early in the development process.

Effective Communication:
 Regular communication and collaboration among team members helped in quickly resolving
integration issues and ensuring all modules worked together seamlessly.

User Experience
 : Prioritizing user experience by conducting usability testing provided valuable insights that
guided the design and functionality improvements, making the application more user-friendly.

Flexibility in Planning:
 Being flexible and adapting the project plan based on unexpected challenges and feedback
helped in successfully overcoming hurdles and meeting project goals.
16
5.3 Future work

The future of the online car market promises to be a dynamic landscape characterized by
continued digital transformation and evolving consumer preferences. As technology
continues to advance, the car-buying process is expected to become even more streamlined
and convenient. Virtual showrooms and augmented reality experiences will enable buyers to
explore vehicles from the comfort of their homes, while AI-powered algorithms will provide
personalized recommendations and assist in decision-making. Online auctions and bidding
platforms may gain popularity, offering real-time opportunities for buyers and sellers alike.
Block chain technology is likely to play a pivotal role in ensuring transparency and trust by
recording a car's history securely. The rise of electric and autonomous vehicles will
necessitate platforms that cater to these emerging technologies, and sustainability concerns
will lead to more eco-friendly data points in the decision-making process. Enhanced data
security and global market expansion will be key considerations, making data protection and
a broader range of car options essential. Peer-to-peer sales and evolving regulatory
frameworks will further shape this future, ensuring that the online car market remains a
dynamic and accessible avenue for both buyers and sellers.

17
Appendix A Glossary
ERD: Entity Relationship Diagram
GUI: Graphical User Interface
HTML: Hyper Text Markup Language
CSS: Cascading Style Sheet
PHP: Hypertext Preprocessor
IP: Internet Protocol
MS: Microsoft
OS: Operating System
REQ: Requirement
SRS: Software Requirement Specification
TCP: Transmission Control Protocol
WBS: Work Breakdown Structure

Deployment/Installation Guide for Car Market Project on

XAMPP

This guide will help you deploy and install your car market project on XAMPP, including selling car spare
parts online and renting cars.
Prerequisites:

1. XAMPP installed on your system.

2. Your Project Files: Source code of your car market project.
3. Database File: SQL file to set up the database.
Step 1: Install XAMPP

1. Download XAMPP: Go to the [official XAMPP website](https://www.apachefriends.org/index.html)

and download the appropriate version for your operating system.
2. Install XAMPP: Follow the installation instructions to install XAMPP on your system.

Step 2: Start XAMPP

1. Open the XAMPP Control Panel.

2. Start Apache and MySQL modules by clicking on the "Start" buttons next to them.

18
Step 3: Set Up the Project Files

1. Copy Project Files: Copy your project files into the `htdocs` directory of your XAMPP installation. This
directory is typically located at `C:\xampp\htdocs` on Windows.
- Create a folder named `car_market` (or any other name) inside `htdocs` and paste your project files
there.
Step 4: Configure the Database

1. Open phpMyAdmin: In your browser, go to `http://localhost/phpmyadmin`.

2. Create a Database:
- Click on "New" in the left sidebar.
- Enter a name for your database (e.g., `car_market_db`) and click "Create".
3. Import Database:
- Select the database you just created.
- Go to the "Import" tab.
- Click on "Choose File" and select your SQL file (e.g., `car_market_db.sql`).
- Click on "Go" to import the database.

Step 5: Configure Database Connection in Your Project

1. Open your project directory and locate the file responsible for database connection (e.g., `db_config.php`
or `config.php`).
2. Update the database connection details to match your XAMPP setup:
```php
<?php
$servername = "localhost";
$username = "root";
$password = "";
$dbname = "car_market_db";

// Create connection
$conn = new mysqli($servername, $username, $password, $dbname);

// Check connection
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}
?>

19
 ```

Step 6: Test the Project

1. Access the Project:

- Open your web browser and go to `http://localhost/car_market` (or the folder name you used in
`htdocs`).
2. Verify Functionality:
- Ensure that all pages load correctly.
- Test the database interactions such as logging in, registering, adding products, etc.
- Check for any errors and debug as necessary.
Troubleshooting Tips

-Apache and MySQL Not Starting:

- Ensure that no other programs (e.g., Skype) are using ports 80 or 443 (Apache) and 3306 (MySQL). You
can change these ports in the XAMPP Control Panel > Config.
- Database Connection Errors:
- Verify that your `db_config.php` (or equivalent) file has the correct database name, username (`root`),
and password (usually empty for XAMPP).
- **Permission Issues**:
- On Windows, run XAMPP Control Panel as an administrator.
- On macOS/Linux, ensure your project files have the necessary read/write permissions.

Conclusion:
You have successfully deployed and installed your car market project on XAMPP. Your project should
now be accessible via the local server, and you can begin testing and demonstrating its functionality. If you
encounter any issues, refer to the troubleshooting tips or consult the XAMPP documentation for additional
assistance.

20