CAR SHOWROOM MANAGEMENT SYSTEM

By RUKMANI B

Roll No: 1619MCA0015

Reg No: 67119100002

A PROJECT REPORT

Submitted to the

FACULTY OF INFORMATION AND COMMUNICATION ENGINEERING

in partial fulfilment for the award of the degree

of

MASTER OF COMPUTER APPLICATIONS

CENTRE FOR DISTANCE EDUCATION ANNA UNIVERSITY CHENNAI 600 025

August, 2022
 BONAFIDE CERTIFICATE

Certified that the Project report titled CAR SHOWROOM MANAGEMENT SYSTEM is

the bonafide work of Ms. RUKMANI B who carried out the work under my supervision.

Certified further that to the best of my knowledge the work reported herein does not form

part of any other project report or dissertation on the basis of which a degree or award was

conferred on an earlier occasion on this or any other candidate.

Signature of student Signature of Guide

RUKMANI B Dr. A. Arun Kumar M.E,PhD,

Roll No: 1619MCA0015 Anna University,

Reg No: 67119100002 Chennai - 25

 2

Certificate of VIVA-VOCE-Examination

This is to certify that Ms. RUKMANI B (Roll No. 1619MCA0015; Register No.

67119100002 ) has been subjected to Viva-voce-Examination on ……………………

(Date) at .......……………. (Time) at the Study centre

…………………………………………………………………………….............................

…………...................... (Name and Address of the Study centre).

Internal Examiner External Examiner

Name: Name:
Designation: Designation:
Address: Address:

Coordinator Study Centre

Name:

Designation:

Address:

Date:
 3

ABSTRACT (ENGLISH)

This is a live project which was developed for a local Vehicle Agent. It is useful to the Agent
to maintain the User details, Sales Details, Company items and services and also Vehicle
Details. If any user buy a vehicle in loan that persons vehicle will recognizes with the help
of vehicle no. The agent will enter the Vehicle No It will help the user to search the vehicle
details and the required details of the User. The agent enters the User details and maintain
admin details. Regarding the registration module, it contains the information about newly
joined User details like name of the user, password etc. Billing and Payment Detail will
contain the details like Actual Amount to be paid. Searching is having the details of the user.
Any agent will login and search the details of the user it will show all details like user Details,
vehicle name, payment type etc. This “Car Showroom Management System" project mainly
contains the vehicle information and loan recovering details. The vehicle is purchased that
vehicle amount will be cleared or not. Creating the application for car show room
management system.
 4

TABLE OF CONTENTS

CHAPTER 1................................................................................................................. 08

INTRODUCTION .......................................................................................................... 08

1.1OVERVIEW OF THE PROJECT…. ............................................................................. 08

1.2 EXISTING SYSTEM ................................................................................................. 08

1.2.1 EXISTING SYSTEM OVERVIEW ........................................................................... 08

1.3 PROPOSED SYSTEM ............................................................................................... 08

1.4 OBJECTIVE AND SCOPE OF THE PROJECT............................................................. 10

1.5 ORGANISATION OF THE PROJECT ......................................................................... 10

CHAPTER 2............................................................................................................... 110

SYSTEM AND REQUIREMENTS SPECIFICATION ....................................................... 110

2.1 INTRODUCTION ................................................................................................... 110

2.2 OVERALL DESCRIPTION........................................................................................................10

2.3 SYSTEM REQUIREMENTS......................................................................................................10

2.3.1 SOFTWARE REQUIREMENT ...............................................................................................10

2.3.2 PERFORMANCE REQUIREMENT ......................................................................................11

2.3.3 SOFTWARE QUALITY ATTRIBUTES.................................................................................11

CHAPTER 3........................................................................................................ ...............12

SYSTEM DESIGN AND IMPLEMENTATION ..........................................................................12

3.1 DETAILED DESIGN................................................................................................. ...............12

3.1.1 SYSTEM ARCHITECTURE….............................................................................................12

3.1.2 USE CASE DIAGRAM..........................................................................................................13

3.1.3 CLASS DIAGRAM ...............................................................................................................14

3.1.4 SEQUENCE DIAGRAM ......................................................................................................14

 5

3.1.5 COMMUNICATION DIAGRAM...................................................................... ...................15

3.1.6 DATA FLOW................................................................................................ .........................16

3.2 DATABASE DESIGN........................................................................................... ...................17

3.2.1 Add Cart Car TABLE............................................................................................................17

3.2.2 Registration Admin/User TABLE.........................................................................................18

3.2.3 Second hand car table TABLE..............................................................................................18

3.2.4 Payment TABLE...................................................................................................................19

3.3 MODULE DESCRIPTION ......................................................................................................20

3.4CODING................................................................................................................ .....................22

CHAPTER 4.................................................................................................... ..................32

TEST PLAN AND RESULTS .................................................................................... ....................32

4.1 TEST PLAN .......................................................................................................... ...................33

4.1.1 TESTING OBJECTIVES......................................................................................................34

4.1.2 TESTING PRINCIPLES........................................................................................................34

4.1.3 TESTING STRATEGIES......................................................................................................34

4.1.4 TEST CASE........................................................................................................ ..................35

4.2 RESULT .................................................................................................................................35

CHAPTER 5.................................................................................................... ................37

CONCLUSION AND FUTURE WORK .....................................................................................37

5.1 CONCLUSION...................................................................................................... .................37

5.2 FUTURE WORK................................................................................................... .................37

CHAPTER 6...................................................................................................................37

REFERENCES ............................................................................................... ..................37

 6

TABLE OF FIGURES

Figure 1: System Architecture .............................................................................................12

Figure 2: Use Case Diagram ................................................................................................13
Figure 3: Class Diagram ......................................................................................................14
Figure 4: Sequence Diagram................................................................................................15

Figure5:CommunicationDiagram……….............................................................................15
Figure 6: Data Flow Diagram ..............................................................................................16
Figure 7: Home Page.................................................................................................. ...........22

Figure 8: Admin Page ..........................................................................................................23

Figure 9: Forgot Password ...................................................................................................23
Figure 10: Car Showroom Details…....................................................................................24
Figure 11: Buying Car Details….........................................................................................25

Figure 12: Booking Confirmation………………………………………………………...26

Figure 13:Second Hand Car Purchase......... ......................................................................27
Figure 14: View and Manage the second hand vehicle……................................................28

Figure 15: Payment detail for second hand car….................................................................29

 7
LIST OF TABLES

Table 3.2.1: Add Cart Car /second hand car Table ................................................. 22
Table 3.2.2: Registration for user/admin Table ............................................................ 23

Table 3.2.3: Second Hand Car Purchase Table...............................................................23

Table 3.2.4: Payment Table...............................................................................................24

 8

CHAPTER 1

INTRODUCTION

1.1OVERVIEW OF THE PROJECT

Car Showroom Management System is a project that is used to manage and control the
complete record of Cars. To present hold the record of Cars, Customers, corporations,
booking. This Car showroom management system project is devised for Admin and
users who are engaged in cars. This system has the track of all the cars with every single
detail. From the date of production to up to what price can one consult while taking that
car, one can view all the data here. If someone is involved in buying the car, then he/she
can reach the retailer as well for the same, via the system.

1.2 EXISTING SYSTEM

1.2.1 EXISTING SYSTEM OVERVIEW

In the existing scenario, if someone has to buy a car or even interested in buying any car, then
the person has to go to the showroom. Not only once, but every time, whenever he/she is
looking for some fact, the only option left is to go to the showroom. This is very time
consuming and very hectic as well. Sometimes, the buyer even lost interest because of this
practice.
 9

1.3 PROPOSED SYSTEM

Car showroom management system is very effective. If someone is interested in buying any
car or bike, then he/she can check all the information related to the car or bike in the given
portal. He/she can even book the test drive within the system. The proposed system also helps
the buyer to check which cars and companies are good for them, by showing them the past
reviews about the car/companies. The proposed system is so helpful and effective.

ADVANTAGES:

▪ Less time consumption.

▪ No manual work.
▪ Easy booking the car or bike in two hand details.

1.4 OBJECTIVE AND SCOPE OF THE PROJECT

Input Design is the process of converting a user-oriented description of the input into a
computer-based system. This design is important to avoid errors in the data input process and
show the correct direction to the management for getting correct informatio n from the
computerized system.
It is achieved by creating user-friendly screens for the data entry to handle large volume
of data. The goal of designing input is to make data entry easier and to be free from errors.
The data entry screen is designed in such a way that all the data manipulates can be performed.
It also provides record viewing facilities.
When the data is entered it will check for its validity. Data can be entered with the help of
screens. Appropriate messages are provided as when needed so that the user will not be in
maize of instant. Thus the objective of input design is to create an inp ut layout that is easy to
follow.
 10

1.5 ORGANISATION OF THE PROJECT

A project organization is a structure that facilitates the coordination and

implementation of project activities. One of the important decisions of project
management is the form of organizational structure that will be used for the project.
The structure defines the relationships among modules of the project and the
relationships with the external environment. A properly designed project organization
chart is essential to project success.

CHAPTER 2

SYSTEM AND REQUIREMENTS SPECIFICATION

2.1 INTRODUCTION

Each application has specific goals and designed to achieve particular

objective. This application mainly aimed and designed to provide an ease for projects
to manage non billable resources

2.2 OVERALL DESCRIPTION

This project expects moderate requirements which is common now a days for
all the developer level people in terms of development this application requires JAVA
and My SQLyog Community 32 Database. It can be installed on normal computers
with at least 8 GB of RAM. And there is no big specification requirement to run or use
the application which will run on any desktop. It will run on any desktop which has the
windows 7 or higher version

2.3 SYSTEM REQUIREMENTS 2.3.1 SOFTWARE REQUIREMENT

Operating System : Windows 7/10

Coding Language : JAVA
Data Base : MYSQL
IDE : NetBeans
 11

2.3.2 PERFORMANCE REQUIREMENT

A requirement that specifies a performance characteristic that a system or system

component must possess. Performance of the any software will be based on the design and
the way of infrastructure that it designed and build on.

2.3.3 SOFTWARE QUALITY ATTRIBUTES

Availability

• This application can be installed and executed on any desktop so it’s easy to check.
• As user can register easily it’s simple to maintain.
• Access to content of the application will be availed by the registered users alone

Correctness

• Admin can easily provide access to Resource Managers and Project Managers with
the registered Email Id.

Maintainability

• The administrator be maintaining the adding or removing resource details.

• Project details will be maintained by admin.

Usability

• This application makes ease for Mangers for resource allocation to a project.

Flexibility
Anyone with a basic understanding of computers may use this application because to
its flexible, user-friendly user interface and easy navigation.
 12

Security

The back end of the application is developed in MySQL and password are encrypted stored
securely in database. Also, in the application level each module is loaded after checking the
authentication and access level. If the user doesn’t have access the user will not be possible
to enter webpage.

CHAPTER 3

SYSTEM DESIGN AND IMPLEMENTATION

3.1 DETAILED DESIGN

3.1.1 System Architecture

It shows the Overall System Architecture of the project on a high level.

Figure 3.1.1 System Architecture

 13

3.1.2 Use Case Diagram

Use case diagram explains the modules that are involved in the system

Figure 3.1.2Use Case Diagram

 14

3.1.3 Class Diagram

Figure 3.1.2 Class Diagram

3.1.4 Sequence Diagram:

Figure 3.1.4 Sequence Diagram

 15

3.1.5 Communication Diagram:

Figure 3.1.4 Communication Diagram

3.1.6 Deployment Diagram:

Figure 3.1.4 Deployment Diagram

 16

Data Flow Diagram:

Level 0:

Level 1:

Level 2:
 17

3.2 Database Design

Database Design Diagram

Database Design diagram describes the relation between the tables in database

3.2.1 Add Cart Car Table

FIELD TYPE DEFAULT VALUE

S No int not null

email varchar not null

uid varchar not null

Uname varchar not null

cid varchar not null

Cname varchar not null

engine varchar not null

image varchar not null

des Varchar not null

status Varchar Not null

ano Varchar Not null

Table 3.2.1 Add Cart Car Table

 18

3.2.2 Registration for user/admin Table

FIELD TYPE DEFAULT VALUE

S No int not null

name varchar not null

pass varchar not null

email varchar not null

mobile varchar not null

gender varchar not null

location varchar not null

state varchar not null

Table 3.2.2 Registration Admin/User Table

3.2.3 Second Hand Car Purchase Table

FIELD TYPE DEFAULT VALUE

S No int not null

email varchar not null

uid varchar not null

Uname varchar not null

cid varchar not null

Cname varchar not null

engine varchar not null

 image varchar not null

des Varchar not null

status Varchar Not null

ano Varchar Not null

Table 3.2.3 Second Hand Car Purchase Table

3.2.4 Payment Table

FIELD TYPE DEFAULT VALUE

S No int not null

uid varchar not null

pname varchar not null

email varchar not null

cid varchar not null

cname varchar not null

Engine varchar not null

image varchar not null

des varchar not null

status varchar not null

ano varchar not null

exp varchar not null

cardno varchar not null

cost varchar not null

 20

3.3 MODULE DESCRIPTION

3.3.1 Recruiter

The Recruiter interface is a web application which is having the following modules,

• Admin
• User Booking car
• User 2nd hand car/bike booking detail
• User Post second hand selling car with detail
• Second Hand Car Boy

1. Admin
• Login
• Add Car & Full Details
• View & Manage car
• View New Payment & booking Detail
• View all Transaction detail
• Logout
2. User Booking car

• Register the account with the basic information

• Login the account with correct credentials
• Add all new car
• View new car .
• Purchase the car through online card payment
• Logout
 21

3. User 2nd hand car/bike booking detail

• Register the account with the basic information

• Login the account with correct credentials
• View second hand car .
• Purchase the car through online card payment
• Logout

4. User Post second hand selling with detail

• Login the account with the correct credentials

• Upload the second-hand car
• View and manage the second-hand car posted
• Payment Detail for
• View Transaction detail
• Logout

5. Log out

• Admin can log out.

• User can Log out.

• Click on car showroom log , user can able to logout

 22

3.4 CODING

Home Page

It’s the first page of the website app which will take the user to the home page on app start.

• User will be landed on the home page when the application starts.

• User need to enter valid credentials to access the home page

• Connect the database with the page to validate the credentials.

• User can request access if it’s a new registration

• User can also reset the password

 23

•
Figure 3.4.1 Home page

Forgot Password:

• User can reset their password by providing the values for all the fields in this form.

• User need to provide the Registered Email ID and current password

• Once current password is verified on successful verification, we can change the
password by entering New Password Reset it.
 24

Car Showroom Dashboard

• User can view the list of car available.

• User can able to view and manage the second hand car
 25

Buying the Car Product

• User buying the car through credit and debit card payment.
• User can able to view car detail with price tag.
 26

Verify Booking Confirmation

Booking confirmation popup will display
 27

View Transaction on Booking Car

▪ User can able to view the transaction detail
▪ Action will show the admin response either purchase request is confirmed or
waiting

Second Hand Car Purchase

• Register the second hand car information to sell.
• Upload the second hand car image to sell.
 28
View and Manage the second hand vehicle posted

• User can able to view the posted second hand vehicle .

• User can able to change the action like delete and unavailable.
 29

Payment detail for second hand car.

• User can able to view the payment transcation detail.
 30
User can able to see the other user posted second hand car

Purchase and payment for second hand car

 31

Booking Confirmation Popup

 32
View Transaction for second hand car

CHAPTER 4

TEST PLAN AND RESULTS

4.1 TEST PLAN

Testing is to make sure the software product meeting the requirements or not with all the
expected results in different scenarios. There is different level of testing’s which helps us
to check the software in different aspects. The test process is initiated by developing a
comprehensive plan to test the general functionality and special features on a variety of
platform combinations. Strict quality control procedures are used.

UNIT TESTING

Any software will be tested first for unit testing which gives the result for individual
functionality or the module that developed will be tested then and there at the time of
 33

development itself. Unit testing must be done with occur when the program is run in a
realworld environment. Unit testing will be performed after the completion of an
individual unit of the system before integrating with other modules.

INTEGRATION TESTING

Software integration testing is the incremental integration testing of two or more

integrated software components on a single platform to produce failures caused by
interface defects. The task of the integration test is to check that components or software
applications, e.g., components in a software system or – one step up – software
applications at the company level – interact without error.

ACCEPTANCE TESTING

User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

PERFORMANCE TESTING

The Performance test ensures that the output be produced within the time limits, and
the time taken by the system for compiling, giving response to the users and request
being send to the system for to retrieve the results.

SYSTEM TESTING

System testing ensures that the entire integrated software system meets requirements. It tests
a configuration to ensure known and predictable results. An example of system testing is the
configuration-oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.
 34

4.1.1 TESTING OBJECTIVES

Testing is to make sure whether the software meets the requirements and working as
expected, it helps to find any errors that are involved in the system which means the
functionality didn’t work as expected or any error involved in the system. Any testing is to
identify the errors, or the miscellaneous behavior of the system and it performed at different
levels in different aspects for different goals as multiple aspects of system to be tested to
make the system complete.

4.1.2 TESTING PRINCIPLES - VERIFICATION & VALIDATION

Verification is a process of checking the system whether that is working fine

asexpected. It refers more in quality aspect of the system.

Validation is to check or test whether the system responding or

behavingaccordingly with the data inputs.

It validates the data and work according to the system functionality.

4.1.3 TESTING STRATEGIES

Testing should be performed on the system at each level and the errors or the defects which
are identified should be maintained so that the system performance so far will be identified
easily and the correction or the modified system will be tested again.
 35

4.1.4 TEST CASES

Steps Step Description Data/Value Result Status

1 User enter User Name User Name Login to Admin Dashboard Success
and Password Password
2 If No value entered Validation should display Success
message
3 Click Request Access Opens Sign Up Page Success
to Sign Up
4 Enter User Details User Name The characters are visible in text Success
Login ID fields
Password

5 Click on Request Details updated in database Success

Acces button
6 Click Forgot Password Opens Forgot Password Page Success
to change password
7 Enter New Password Password Validate two passwords are Success
and Confirm Password same and display message
8 Click on Reset to update Updates the new password in Success
password in Database database
9 Admin can able to add New Car added should show Success
new car
10 Admin can able to Admin can able to accept or Success
confirm the order decline the oder

11 User can able to view User is viewed the car list for Success
the car description purchasing

12 User can able to make User can do online card Success

a car payment through payment successfully
card
13 User can able to hand User can add second hand Success
the second hand car/bike for selling.
car/bike
14 User can able to see Transaction should display Success
the transaction detail
15 User can able to view User can able to delete and Success
and manage the enable to car detail
uploaded car
16 User can able to see the Transaction should display for Success
transaction detail for second hand car
second hand car
17 User can able to make User can do online card Success
a car payment for payment successfully for second
second hand card hand car
through card
18 Click on Car Show User can able to logout Success
R)OM Icom

19 Click on Logout for User/Admin can able to logout Success

user/admin login

4.1.4 Test Cases Tables

4.2 RESULT

All the test cases are successfully tested with various data set and got the results as
expected.
 CHAPTER 5

CONCLUSION AND FUTURE WORK

5.1 CONCLUSION

There is scope for future enhancements as the need and the usage becoming

more can add and enhance a lot. There are different possibilities to add more advance

features as the system enhancing. Adding new fea tures with available technologies

and advanced options makes the application more interesting and provides the good

look as well. Can add different kinds of analysis option and import and export of reports

for future reference.

CHAPTER 6

REFERENCES

6.1 Web Resources

http://www.w3schools.com
http://tutorialspoint.com