lOMoARcPSD|53383464

Car Showroom Management System

Software Engineering (Lovely Professional University)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by aha jang (ahajang141@gmail.com)
 lOMoARcPSD|53383464

CAR SHOWROOM MANAGEMENT SYSTEM

BACHELOR OF TECHNOLOGY
in
COMPUTER SCIENCE AND ENGINEERING

By
RANAJOY DHAR
Registration number
12105101

Supervisor
DR. ASHISH SONI SIR

School of Computer Science and Engineering (14 Bold)

Lovely Professional University
Phagwara, Punjab (India)
Month……11…… Year …22…

@ Copyright LOVELY PROFESSIONAL UNIVERSITY, Punjab (INDIA)

Month …11.., Year …22..

ALL RIGHTS RESERVED

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

DECLARATION

I here by declare that the project report entitled “CAR

SHOWROOM MANAGEMENT SYSTEM” submitted by me to
lovely Professional University in partial Fulfilment for the
award of degree of BTech in computer science engineering is
a record of bona fide project work carried out by me under
the guidance of Dr. Ashish Soni Sir.
I further declare that the work reported in this project has
not been submitted and will not be submitted, either in part
or full, for the award of any other degree in this institute or
any other institute or university.

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

ACKNOWLEDGEMENT

The satisfaction that accompanies that the successful

completion of any task would be incomplete without the
mention of people whose ceaseless cooperation made it
possible, whose constant guidance and encouragement
crown all efforts with success.
I am grateful to mine project guide Dr. Ashish Soni Sir for the
guidance, inspiration and constructive suggestions that helps
me in the preparation of this project.

I also thank mine colleagues who have helped me in

successful completion of the project.

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

TABLE OF CONTENTS

1. COVER PAGE
2. DECLARATION
3. ACKNOWLEDGEMENT
4. INTRODUCTION
5. ER DIAGRAM
6. ATTRIBUTE AND ENTITIES
7. NORMALIZATION
8. FUNCTION DEPENDENCY
9. ABOUT SQL AND PL/SQL USED IN PROJECT
10. CONCLUSION

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

INTRODUCTION

This is live project which was developed for a local vehicle agent it is
useful to the agent to maintain the customer details sales diesel
company items and services and also vehicle details if any customer
by a vehicle in loan that person vehicle will recognises with the help
of vehicle number vehicle recognition system which will cover the
following modulates the agent will enter the vehicle number it will
help the user to search the vehicle details and required details of the
customer the agent enters the customer details and maintain
company details vehicle showroom management system is ideal for
dealers resellers of any size the vehicle showroom control panel can
be installed on any operating system the product features include:
easy stock inventory updates, full user management, photograph
uploads, image optimization.

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

ER DIAGRAM

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

ATTRIBUTES AND ENTITIES

Entities:
• Cars Entity : Attributes of Cars are car_id,
car_driver_id, car_customer_id, car_number,
car_company car_type, car_description
• Car Models Entity : Attributes of Car Models are
car_model_id, car_model_number, car_model_year,
car_model_name, car_model_type,
car_model_description
• Car Owners Entity : Attributes of Car Owners are car
owner_id, car owner_name, car owner_mobile, car
owner_email, car owner_username, car
owner_password, car owner_address
Inventory Entity: Attributes of Inventory are
inventory_id, inventory_items, inventory_number,
inventory_type, inventory_description
• Customer Entity : Attributes of Customer are
customer_id, customer_name, customer_mobile,
customer_email, customer_username,
customer_password, customer_address
• Booking Entity: Attributes of Booking are booking_id,
booking_title, booking_type, booking_ticket,

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

booking_date, booking_description

ATTRIBUTES:

Table name: Admin

Attribute: adminid, adminname, username, password,
contactnumber varchar(50), lastlogin, status.

Table name: Customer

Attribute: custid, fname, lname, contactno, emailed, password,
lastlogin, status.

Table name: Dealer

Attribute: dealerid, adminid, image, fname, lname, userid, password,
contactno varchar(50), lastlogin, status.

Table name: Image

Attribute: imagename, image_id, img_path varchar(50), V_id.

Table name: Showroom

Attribute: showroomid, dealerid, showroomnamevarchar(50),
imagepath, contactno, address, status.

Table name: Sales

Attribute: salesid, vehid, custid, showroomid, cost, taxid.

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

Table name: Tax

Attribute: taxid, taxdescriptiontext, tax, status.

Table name: Vehicle

Attribute: vehid, dealerid, vehname, vehmodel, vehtype, vehcost,
status.

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

NORMALIZATION

 Normalization is a method to remove anomalies and bring the

database to a consistent state.

 First Normal Form - As per First Normal Form, no two Rows of

data must contain repeating group of information.

 Second Normal Form - No non-prime attribute is dependent on

the proper subset of any candidate key of the table.

 Third Normal Form - Transitive functional dependency of non-

prime attribute on any super key should be removed.

 In other words 3NF can be explained like ts: A table is in 3NF if

it is in 2NF and for each functional dependency X-> Y at least
one of the following conditions hold: X is a super key of table
and Y is a prime attribute of table.

 Boyce-Codd Normal Form - It is an advance version of 3NF

that's why it is also referred as 3.5NF. BCNF is stricter than 3NF.
A table complies with BCNF if it is in 3NF and for every
functional dependency X->Y, X should be the super key of the
table.

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

FUNCTION DEPENDENCY

 Functional dependency (FD) is a set c constraints between two

attributes in a relation. Functional dependency says that if two
tuples have same values for attributes A1, A2,..., An, then those
two tuples must have same values for attributes B1, B2, ..., Bn.

 Functional dependency is represented by an arrow sign (→)

that is, X→Y, where X functionally determines Y. The left-hand
side attributes determine the values of attributes on the right-
hand side.

 A functional dependency is a relationship between two

attributes. Typically between the PK and other non-key
attributes with in the table.

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

PL/SQL:
SQL FOR TABLE CREATION
1.CREATE TABLE ADMIN
(
A_ID NUMBER(20),
A_NAME VARCHAR(20),
USERNAME VARCHAR(20),
PASSWORD NUMBER(10),
LAST_LOGIN DATE,
STATUS VARCHAR(20),
CREATE_DATE DATE,
CONSTRAINT AD_PK1 PRIMARY KEY(A_ID)
);
2. CREATE TABLE CUSTOMER(CU_ID NUMBER(20),
CU_NAME VARCHAR(20),
CO_NUM NUMBER(20),
GENDER CHAR,
PASSWORD NUMBER(20),
ADDRESS VARCHAR(20),
MAIL_ID VARCHAR(20),
LAST_LOGIN DATE,
STATUS VARCHAR(20),
CONSTRAINT SU_PK1 PRIMARY KEY(CU_ID));
3. CREATE TABLE DEALER(D_ID NUMBER(20),

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

A_ID NUMBER(10),
CMPNY_NAME VARCHAR(20),
USERNAME VARCHAR(20),
PASSWORD NUMBER(20),

ADDRESS VARCHAR(20),
LAST_LOGIN DATE,
STATUS VARCHAR(20),
CONSTRAINT DEALER_PK1 PRIMARY KEY(D_ID),
CONSTRAINT DEALER_FK1 FOREIGN KEY(A_ID) REFERENCES ADMIN(A_ID) ON
DELETE SET NULL);
4. CREATE TABLE SHOWROOM(SH_ID NUMBER(20),
D_ID NUMBER(20),
SH_NAME VARCHAR(20),
IMG_PATH VARCHAR(20),
ADDRESS VARCHAR( 20),
CO_NUM NUMBER(20),
STATUS VARCHAR(20),
CONSTRAINT SH_PK1 PRIMARY KEY(SH_ID),
CONSTRAINT SH_FK1 FOREIGN KEY(D_ID) REFERENCES DEALER(D_ID) ON
DELETE SET NULL);
5. CREATE TABLE TAX(TAX_ID NUMBER(20),
TAX_DESC VARCHAR(20),
TAX NUMBER(20) NOT NULL,
STATUS VARCHAR(20),
CONSTRAINT TAX_PK1 PRIMARY KEY(TAX_ID));

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

6. CREATE TABLE VEHICLE(V_ID NUMBER(20),

D_ID NUMBER(20),
V_NAME VARCHAR(20),
V_MODEL VARCHAR(20),
V_TYPE VARCHAR(20),
V_DESC VARCHAR(20),

V_COST NUMBER(20) NOT NULL,

CREATE_DATE DATE,
STATUS VARCHAR(20),
CONSTRAINT V_PK1 PRIMARY KEY(V_ID),
CONSTRAINT V_FK1 FOREIGN KEY(D_ID) REFERENCES DEALER(D_ID) ON
DELETE SET NULL);
7. CREATE TABLE IMAGE(IMG_ID NUMBER(20),
IMG_NAME VARCHAR(20),
V_ID NUMBER(20),
IMG_PATH VARCHAR(20),
DEFAULTING VARCHAR(20),
CONSTRAINT IMG_PK1 PRIMARY KEY(IMG_ID),
CONSTRAINT IMG_FK1 FOREIGN KEY(V_ID) REFERENCES VEHICLE(V_ID) ON
DELETE SET NULL);
8. CREATE TABLE SALES(SAL_ID NUMBER(20),
V_ID NUMBER(20),
CU_ID NUMBER(20),
SH_ID NUMBER(20),
V_COST NUMBER(20),

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

TAX_ID NUMBER(20),
ORD_DAT DATE,
DEL_DAT DATE,
SAL_DESC VARCHAR(20),
STATUS VARCHAR(20),
CONSTRAINT SAL_PK1 PRIMARY KEY(SAL_ID),
CONSTRAINT SAL_FK1 FOREIGN KEY(V_ID) REFERENCES VEHICLE(V_ID) ON
DELETE SET NULL,
CONSTRAINT SAL_FK2 FOREIGN KEY(CU_ID) REFERENCES CUSTOMER(CU_ID)
ON DELETE SET NULL);
CONSTRAINT SAL_FK3 FOREIGN KEY(SH_ID) REFERENCES SHOWROOM(SH_ID)
ON DELETE SET NULL,
CONSTRAINT SAL_FK4 FOREIGN KEY(TAX_ID) REFERENCES TAX(TAX_ID) ON
DELETE SET NULL));

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

DATA ENTRY:
Insert into admin table:
INSERT INTO ADMIN VALUES('10','ajay','ajay','000','10-july-
2015','complete','10-jun-2000');
INSERT INTO ADMIN VALUES(20,'kumar','kumar',000,'10-jan-
2015','complete','10-jul-2000');
INSERT INTO ADMIN VALUES(30,'yadav','yadav',000,'10-aug-
2015','complete','10-jul-2002');
INSERT INTO ADMIN VALUES(40,'ram','ram',000,'10-apr- 2015','complete','10-
jan-2002');
INSERT INTO ADMIN VALUES(50,'mohan','mohan',000,'10-apr-
2016','complete','10-jan-2008');

Insert into customer table:

INSERT INTO CUSTOMER
VALUES('&CU_ID','&CU_NAME','&CO_NUM','&GENDER','&
amp;PASSWORD','&ADDRESS','&MAIL_ID','&LAST_LOGIN','&am
p;STATUS');
INSERT INTO CUSTOMER
VALUES(1,'srikanth',510245,'m',000,'rampur','sri@gmail.com','25-may-
2016','ready');
INSERT INTO CUSTOMER
VALUES(2,'sriram',510255,'m',000,'banglore','sriram@gmail.com','22-may-
2016','ready');
INSERT INTO CUSTOMER
VALUES(3,'maha',520255,'f',000,'bellary','maha@gmail.com','22-jul-
2015','ready');
INSERT INTO CUSTOMER
VALUES(4,'raja',520235,'m',000,'mysore','raja@gmail.com','02-jan-
2016','ready');

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

INSERT INTO CUSTOMER

VALUES(5,'rani',520222,'f',000,'hyd','rani@gmail.com','02-jan-2011','ready');

Insert into dealer table

INSERT INTO DEALER
VALUES('&D_ID','&A_ID','&CMPNY_NAME','&USERNAME','
&PASSWORD','&ADDRESS','&LAST_LOGIN','&ATUS');
INSERT INTO DEALER VALUES(101,10,'BAJAJ','BAJAJ',000,'BANLORE','10-may-
2016','selling');
INSERT INTO DEALER VALUES(102,20,'HONDA','HONDA',000,'BELLARY','11-aug-
2016','not selling');
INSERT INTO DEALER VALUES(103,30,'YAMAHA','YAMAH',000,'MYSORE','15-
aug-2015','not selling');
INSERT INTO DEALER VALUES(104,40,'HERO','HERO',000,'GADAG','15-FEB-
2017','selling');
INSERT INTO DEALER VALUES(105,50,'BULLET','BELLET',000,'BANGLORE','11-
JAN-2017',' selling');

Insert into showroom table:

INSERT INTO SHOWROOM

VALUES('&SH_ID','&D_ID','&SH_NAME','&IMG_PATH','&a
mp;ADDRESS','&CO_NUM','&STATUS');
INSERT INTO SHOWROOM
VALUES(111,101,'GURU','E:AS/','BANGLORE’',258741,'FULL');
INSERT INTO SHOWROOM
VALUES(112,102,'GAYATRI','D:AS/','MYSORE',258111,'AVG');
INSERT INTO SHOWROOM
VALUES(113,103,'LAKSHMI','E:44/','TUMKUR',257851,'FULL');
INSERT INTO SHOWROOM
VALUES(114,104,'RADHA','E:AS/','BANGLORE',257415,'FULL');

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

INSERT INTO SHOWROOM

VALUES(115,105,'BANU','E:AS/','BANGLORE',257415,'FULL');

Insert into tax table:

INSERT INTO TAX

VALUES('&TAX_ID','&TAX_DESC','&TAX','&STATUS');
INSERT INTO TAX VALUES(1000,'ALL_TAX',542,'PENDING');
INSERT INTO TAX VALUES(2000,'ROAD_TAX',5000,'PENDING');
INSERT INTO TAX VALUES(3000,'ALL_TAX',5420,'CLEAR');
INSERT INTO TAX VALUES(4000,'INSU_TAX',533,'CLEAR');
INSERT INTO TAX VALUES(5000,'ALL_TAX',5412,'PENDING');

Insert into vehicle table:

INSERT INTO VEHICLE
VALUES('&V_ID','&D_ID','&V_NAME','&V_MODEL','&
V_TYPE','&V_DESC','&V_COST','&CREATE_DATE','&STATUS
');
INSERT INTO VEHICLE
VALUES(11,101,'SPLENDER','H456','BIKE','GOOD',45000,'10-JUN-
2016','AVAILABLE');
INSERT INTO VEHICLE
VALUES(12,102,'PULSER','P4569','BIKE','GOOD',85000,'11-JUN-
2015','AVAILABLE');
INSERT INTO VEHICLE VALUES(13,103,'RX','R123','BIKE','GOOD',70000,'11-JAN-
2015','SOLD_OUT');
INSERT INTO VEHICLE VALUES(14,104,'AUDI','A417','CAR','GOOD',805000,'11-
AUG-2016','AVAILABLE');
INSERT INTO VEHICLE VALUES(15,105,'BENZ','P4569','BIKE','GOOD',155000,'30-
SEP-2016','SOLD_OUT');

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

Insert into image table:

INSERT INTO IMAGE
VALUES('&IMG_ID','&IMG_NAME','&V_ID','&IMG_PATH','
&DEFAUTING');
INSERT INTO IMAGE VALUES(100,'BIKE1',11,'C:/PA/','IMAGE');
INSERT INTO IMAGE VALUES(200,'BIKE2',12,'D:/RA/','IMAGE');
INSERT INTO IMAGE VALUES(300,'BIKE3',13,'C:/PA/','IMAGE');
INSERT INTO IMAGE VALUES(400,'BIKE4',14,'E:/XX/','IMAGE');
INSERT INTO IMAGE VALUES(500,'BIKE5',15,'F:/PA/','IMAGE');

Insert into sales table:

INSERT INTO SALES
VALUES('&SAL_ID','&V_ID','&CU_ID','&SH_ID','&V_CO
ST','&TAX_ID','ORD_DAT','DEL_DAT','SAL_DESC','STATUS');
INSERT INTO SALES VALUES(110,11,1,111,45000,1000,'15-JAN- 2016','16-JAN-
2016','HIGH','SUPER');
INSERT INTO SALES VALUES(120,12,2,112,85000,2000,'16-JAN- 2016','18-JAN-
2016','HIGH','MEDIUM');
INSERT INTO SALES VALUES(130,13,3,113,70000,3000,'19-JAN- 2016','20-JUN-
2016','HIGH','AVERAGE');
INSERT INTO SALES VALUES(140,14,4,114,805000,4000,'20-JAN- 2016','21-JAN-
2016','HIGH','SUPER');
INSERT INTO SALES VALUES(150,15,5,115,155000,5000,'15-JAN- 2016','16-
MAR-2016','HIGH','MEDIUM');

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

--------------------------------------------OUTPUT---------------------------------------------

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

Downloaded by aha jang (ahajang141@gmail.com)

 lOMoARcPSD|53383464

Conclusion

This is the perfect system for the car showrooms to manage their
data and help their customers to buy a car without any problem. It
makes the process of buying a car very simpler.
This module is designed specifically for the customers. They can log
in into the system after getting their credentials. This module keeps
track of each and every customer and all the information related to
each customer is being added into this module. This module is
updated timely by the admin of this system.
All the details of the company are added to the module. Along with
the existing details, new details are also added into this module
about the company and various new companies are being updated
by the admin of the system, frequently.
All the facts and figures related to a car of each model is present in
this module & the viewer can view this module after login into the
system. New car details and existing car details are added into this
module. Lists of all the cars are available inside this module.

Downloaded by aha jang (ahajang141@gmail.com)