DATA BASE MANAGEMENT

SYSTEM PROJECT

ON

CAR SHOWROOM
MANAGEMENT SYSTEM

Submitted By:- Submitted to:-

Dr.Omdev
Name-Sachin Prajapati (26990)
Reg.No-12114973
Roll No-47
Section-K21QT
 INTRODUCTION
Introduction to CAR SHOWROOM MANAGEMENT SYSTEM
Database applications are software programs designed to collect, manage and disseminate
information efficiently. The current project deals with CAR SHOWROOM MANAGEMENT
SYSTEM for the owner to deals with organization. Car showroom management system
software is useful for handling distributors information, cars waiting list details, billing details,
customer’s information, Customer help.
The car showroom management system is a standalone application which is based on selling
cars also generating bill and also storing customer and employee details. The main principle
behind the need of car showroom managementsystem is easy supervision of car showroom. It
has user friendly and modular approach. The modular approach of the software increases the
flexibility and the software. Data storing is easier. It will be able to view the details a any time.
Therefore, further the software can make all the system computerize, reduce time
consumption, simple database is maintained, easy operator of the system, user interfaces are
user friendly, it takes very less time to get use to with system. This project also maintains the
record of sold car and available quantity of car.

Introduction to Database Management System

A database is an organized collection of data. A relational database, more restrictively, is a
collection of schemas, tables, queries, reports, views, and other elements.Database designers
typically organize the data to model aspects of reality in a way that supports processes
requiring information, such as (for example) modelling the availabilityof rooms in hotels in a
way that supports finding a hotel with vacancies.
A database-management system (DBMS) is a computer-software application that interactswith
end-users, other applications, and the database itself to capture and analyse data.
A general-purpose DBMS allows the definition, creation, querying, update, and administration
of databases. Well-known DBMSs include MySQL, PostgreSQL, Enterprise DB, MongoDB,
Maria DB, Microsoft SQL Server, Oracle, Sybase, SAP HANA,MySQL, SQLite and IBM.A
database is not generally portable across different DBMSs, but different DBMSs can
interoperate by using standards such as SQL and ODBC or JDBC to allow a single application
to work with more than one DBMS. Sometimes a DBMS is loosely referred toas a "database".

APPLICATION
Databases are used to support internal operations of organizations and to underpin online
interactions with customers and suppliers.
Databases are used to hold administrative information and more specialized data, such as
engineering data or economic models. Examples of database applications include
computerized library systems, flight reservation systems, computerized parts inventory
systems, and many content management systems that store websites as collections of
webpages in a database.

Introduction to SQL
Structure Query Language (SQL) is a programming language to request data from
a database, to add, update, or remove data within a database, or to manipulate the
metadata of the database. SQL was the first commercial language introduced for E.F
Cod’s Relational model. Today almost all RDBMS (MySQL, Oracle, Informix,
Sybase, MS Access) uses SQL as the standard database language.SQL is used to
perform all type of data operations in RDBMS. Commonly used statements are
grouped into the following categories:

Data Query Language (DQL)

SELECT - Used to retrieve certain records from one or more tables.

Data Manipulation Language (DML)

INSERT - Used to create a record.
 o UPDATE - Used to change certain records.
o DELETE - Used to delete certain records.

• Data Definition Language (DDL)

o CREATE - Used to create a new table, a view of a table, or otherobject in database.
o ALTER - Used to modify an existing database object, such as a table.
o DROP - Used to delete an entire table, a view of a table or otherobject in the
database

ER DIAGRAM:-

An ER model is typically implemented as a database. In a simple

relational database implementation, each row of a table represents one
instance of an entity type, and each field in a table represents an
attribute type. In a relational database a relationship between entities is
implemented by storing the PRIMARY KEY of one entity as a pointer
or "foreign key" in the table of another entity. There is a tradition for
ER/data models to be built at two or three levels of abstraction. Note
that the conceptual-logical-physical hierarchy below is used in other
kinds of specification and is different from the three- schema approach
to software engineering. While useful for organizing data that can be
represented by a relational structure, an entity relationship diagram can't
sufficiently represent semi-structured or unstructured data, and an ER
Diagram is unlikely to be helpful on its own in integrating data into a
pre-existing information system. Cardinality notations define the
attributes of the relationship between the entities. Cardinalities can
denote that an entity is optional.
.
TABLES WITH CODE AND THEIR SCREENSHOTS:-

create table cars(

cars_id int,
serial_no varchar(15),
models varchar(20),
year int,
color varchar(20),
price int,
forsale int )
 Insertion in table:-

INSERT INTO cars

VALUES('11111','RKW213',DS234RK1','2011','GREEN','2300000000',
'2000000000')

INSERT INTO cars

VALUES('11112,'RKW214',DS234RK2','2012','red','2700000000','2300
000000')

INSERT INTO cars

VALUES('11113,'RKW215',DS234RK3','2013','VOILET','3000000000',
'2700000000')

INSERT INTO cars

VALUES('11114,'RKW216',DS234RK4','2014','BLACK','3300000000','
2000000000')

create table services(

service_id int,
service_name varchar(20),
hourly_rate int
)
Insertion in table

INSERT INTO SERVICES

VALUES('112','screen wash','230')

INSERT INTO SERVICES

VALUES('113','power steering','250')

INSERT INTO SERVICES

VALUES('114','brake fluid,'440')

INSERT INTO SERVICES

VALUES('115','engine coolant','500')

create table mechanics(

mechanic_id int,
fname varchar(30),
lname varchar(30),
phone_no int
)
Insertion in table:-

INSERT INTO mechanics

VALUES('211','Sachin','Prajapati','1234543982')

INSERT INTO mechanics

VALUES('212','Sachin','Srivastava','7237899992')

INSERT INTO mechanics

VALUES('213','Sameer','Srivastava','72378996677')

INSERT INTO mechanics

VALUES('214','Divyansh','Jaiswal','7237899688')

create table sales_persons(

salesperson_id int,
fname varchar(30),
lname varchar(30)
)

Insertion in table:-

INSERT INTO sales_persons

VALUES('311','Arun','Soni')

INSERT INTO sales_persons

VALUES('312','Saksham','Thakur')

INSERT INTO sales_persons

VALUES('313','Sanjay','Kumar')

INSERT INTO sales_persons

VALUES('314','Atul','Kumar')

create table customers(

cust_id int,
fname varchar(20),
lname varchar(20),
phone int,
address varchar(20),
post_code int
)
 ➔ Insertion in table

INSERT INTO CUSTOMERS

VALUES('51111','Angad','Prajapati','7237890711','ludhiana','271201')

INSERT INTO CUSTOMERS

VALUES('51112','Arpit','Prajapati','7237890733','Jalandhar','271211')

INSERT INTO CUSTOMERS

VALUES('51113','Mahi','Prajapati','7237890744','Balrampur','271222')

INSERT INTO CUSTOMERS

VALUES('51113','suresh','Prajapati','7237890755','Gonda','271333')