Professional Documents
Culture Documents
CAR SHOWROOM
MANAGEMENT SYSTEM
A
PROJECT PRESENTED
BY
MEGAMINDS
GROUP MEMEBERS
1.Akhil Raj
2.Arjun R Dev
3.Ayman A.K
4.Gautham Saju
5. Gouri M.S
6.Jerin Joseph
7.Lenac Liju
DECLARATION
ACKNOWLEDGEMENT
TABLE OF CONTENTS
Contents page no
1.Introduction 8
1.1. Details of the project 9
1.2. Features of the project 10
1.3. overview of the project 10
2.System analysis 12
2.1. Existing system 10-12
2.2. Proposed system 13-17
2.3. Feasibility Study 17-20
3. Software Requirement and specification 20
3.1 System Requirements 21
4.Testing 22
4.1 Acceptance Testing 23
4.2Test Cases 23
5.System Design 24
5.1. Forms
5.2. Tables
6.Future Enhancement
7.Conclusion
CHAPTER-01
INTRODUCTION
1. Introduction
Detail of project
Our project car showroom management system includes managing the details of cars, customers,
employees, and storing the details into the system in a computerized way.
The modern industrial world is very much advanced in technology and the competition in the world is
intense.
The management system has been developed to override the problems prevailing in the practicing manual
system.
This software is supported to eliminate and, in some cases, reduce the hardships faced by the existing
system; moreover, this management system is designed for the particular need to carry out operations in a
smooth and effective manner. This kind of system reduces as much as possible type of errors while
inserting the data. Every organization, whether big organization or small organization, has challenged to
overcome all the loop holes of its management system.
This is designed to assist in strategic planning, and will help you ensure that your organization is
equipped with the right level of information and details for your future goals. Also, for those busy
executives who are always on the go, our system comes with remote access features, which will allow you
to manage your workforce anytime, at all times.
This kind of management system will ultimately allow you to manage the resources in a better way.
Overview of project
CHAPTER-02
SYSTEM ANALYSIS
System Analysis
Existing System
In the existing system of car showroom management, the details regarding the management
quota are stored manually.
This kind of system provides no direct role for the higher officials.
In this type of system, the procedure to maintain the details of the management is highly
complicated.
This existing system of management is very time consuming and requires man power; all
the work is done on paper.
The whole session is stored in register and at the end of the session the reports are
generated.
Thus, we are not interested in generating report in the middle of the session organization as
per the requirement because it takes more time in calculations.
The existing system only provides text-based interface which is not user friendly as the
graphical user interface.
Since the system is implemented in manual the response is very slow.
The existing system is not user friendly because the retrieval of the data is
very slow and the maintenance of the data is not done in an efficient
manner.
Manual control:
All calculations are carried out manually and the maintenance of the data
is manual thus there is greater chance of errors.
The present existing system requires lots of paper work. Loss of even a
single register or record will lead to difficult situations because all papers
are needed to generate the report.
Time consuming:
Since all the management work is done manually, we cannot generate the
report in the middle of the session organization as per the requirement
and thus it consumes a lot of time.
Proposed system
The aim of the proposed system is to develop a system of better and improvised facilities.
The proposed system can overcome all the limitations of the existing system and it also
provides proper security and reduces the manual work.
Data accuracy.
Ensures data security to the user.
Proper control of the administrator.
Minimum time is required to operate.
o System needs to store information of every new entry of car sold and purchased by the
customer.
o System needs to help the internal staff to keep the information of the sales and find them
as per the queries.
o System needs to maintain quantity record. o System needs to update and maintain
records. o System needs to keep record of customers. o System needs to keep record of
employees.
o System needs to keep records and details related to all cars. o System needs to update and
delete the records. o It needs a security system to prevent data loss.
o System needs a search area.
User friendly:
The user feels easy to work on it. The software provides accuracy along with a
pleasant interface.
The retrieval and the storing of information is fast and data is maintained in an
efficient manner.
Reports can be easily generated in the proposed system so the user can generate
the report as per the requirement organization in the middle of the session.
Moreover, work becomes very less and fast because there is no need to keep data
on papers.
All the data is stored on the computer and reports are generated through
computers.
Enhancement:
The software improves the working methods by replacing the existing manual
system with computer-based system.
Automation:
The car showroom management system automates each and every activity of the
manual system and increases the throughput.
Thus, the response time of the system is very less and it works very fast.
Accuracy:
This system provides the user with a quick response with very accurate
information regarding the users.
Maintenance:
No redundancy:
In the proposed system utmost care is taken that the information is not repeated
anywhere in the storage.
This would ensure economic use of storage space and consistency in the data
stored.
Protected:
Feasibility study
All projects are feasible given unlimited resources and infinite time. Study and analyzing all the
existing organization required functionalities of the system.
Feasibility study includes consideration of all the possible ways to provide solution to the given
problem.
The proposed system must satisfy all the user requirements and should be flexible enough so that
the future changes can be easily done based on the future upcoming requirements.
Operational feasibility
Economic feasibility
Technical feasibility
As HTML with CSS and Mongo DB are database-based applications and most of
the users now-a-days are well familiar with the use of these, so there is no need of
any special skills required by the users or making them aware of the system. On
the other hand the system does not have any extra ordinary technical
requirements. So the project is technical feasible too.
Software is easy to operate on and user can easily understand the operations of the
software and proper help is also provided for the user.
Technical feasibility concerns around the current system technology i.e. Software
and Hardware and to what extent it can support the proposed system. It also
involves the financial consideration to accommodate the technical enhancements.
There are technical guarantees of accuracy, reliability, ease of access and high
data security.
CHAPTER-03
Software Requirements and
Specification
Hardware Requirements:
Software Requirements:
Chapter -04
TESTING
Acceptance Testing:
This testing is done to verify the readiness of the system for the implementation. Acceptance testing begins when
the system is complete. Its purpose is to provide the end user with the confidence that the system is ready for use.
It involves planning and execution of functional tests, performance tests and stress tests in order to demonstrate
that the implemented system satisfies its requirements.
Test coverage Analyzer – records the control paths followed for each test case.
Timing Analyzer – also called a profiler, reports the time spent in various regions of the code are areas
to concentrate on to improve system performance.
Coding standards – static analyzers and standard checkers are used to inspect code for deviations from
standards and guidelines.
Test Cases:
Test cases are derived to ensure that all statements in the program have been executed at least once
during testing and that all logical conditions have been executed.
Using White-Box testing methods, the software engineer can drive test cases that
Execute all loops at their boundaries and within their operational bounds.
The test case specification for system testing has to be submitted for review before system testing
Chapter-05
System Design
Forms
Table Structure:
Login Details
Customer Details:
Product details:
Field name Datatype Size constraints
Car ID Integer primary key
Car Type Varchar 30
Car Model Varchar 20
Price Integer 20
features Varchar 20
color Varchar 20
Admin Details:
Field name Datatype Size constraints
First Name Varchar 30
Last Name Varchar 30
Address Varchar 80
Mobile no Integer 10
Email ID Varchar 30
Date Of Birth Date
Gender Varchar 10
User ID Varchar 10 Foreign Key
Password Varchar 20
Employee Details:
Booking Details:
Chapter-06
FUTURE ENCHANCEMENT
FUTURE ENHANCEMENTS:
This application avoids the manual work and the problems concern with it.
It is an easy way to obtain the information regarding the various products information that are
Primarily, when we request information about a particular product it just shows the company, product
id, product name and no. of quantities available. So, after getting the information we can get access to
the product company website just by a
The next enhancement that we can add the searching option. We can directly
search to the particular product company from this site. These are the two enhancements that we could
think of at present.
Chapter-07
CONCLUSION
CONCLUSION:
The package was designed in such a way that future modifications can be done easily.
The following conclusions can be deduced from the development of the project.