A

Project Report On

CAR SHOWROOM MANAGMENT

INDEX
Sr Subject Page
no no:
1 Project Profile 2
1.1 Definition 2
1.2 Scope 2
1.3 Objective 3

2 System analysis and specification 4

2.1 System analysis 4
2.2 User requirement 5
3 System Requirement and specifications 6
4 SDLC 7
5 Overview of .net Technology 11
6 System Design 15
6.1 Data Flow Diagram 16
6.2 E-R Diagram 17
6.3 Data Dictionary 18
7 Screenshot 19
8 Report 30
9 Testing 32
10 Enhancements 34
11 References 35

CAR SHOWROOM MANAGMENT

 1-Project Profile
(1.1)Defination:-

An online showroom is an online space where a business

presents its products to the customers The product presentation usually
includes an image, price or tiered pricing, and product description. An
online showroom can also have online ordering and/or online payment
options. A business can host the online showroom on their website or
create and host it on other platforms.
In the online showrooms, products are usually combined
into categories or collections, while the customer has several range
options. The most common are ranging by price or by brand.
The online showrooms became more popular during the COVID-19
pandemic. While physical stores were forced to be closed, owners
shifted their businesses online

(1.2) scope:-
 current system allow the customer to register account and save
favourite vehicles into wishlist

 The design of the web application involves the listing the

vehicles,search for vehicles etc.

 Its provide update information about the vehicles of all the

companies

 Customer can view purchase details and billing records any time by
logging in his account
CAR SHOWROOM MANAGMENT
(1.3)Objective:-

 Our site very useful in people.

 In this system is worked properly.
 Our main aim is to manage the car Booking.
 User can book the book any time.
 We had developed a fully computerized system.

CAR SHOWROOM MANAGMENT

 2-System analysis and specification

(2.1)System Analysis:-
Feasibility Study:-
 In this system there are logically three concepts we can cosider
as a feasibility study on eventmanagemant.

1. Technical Feasibilit:-
.Net framework and sqlserver is installed or required for the current system.

 Software requirement:-

 Operating system:Microsoft Windows 8

 Visual Studio 2010
 Tools:SQL server 2010

 Hardware Requirement:-

 C.P.U : Pentium c4 2.40 GHZ

 RAM : 256 of RAM
 Hard Disk : 40GB HDD

2. Economical feasibility:-

The Current System Is Require No Cost of SoftWare Because In Which Environment of

SoftWare.
This System Is Developed Is Very Cheap.
In Event Manager We Need Some Time To Handel Specific Events.

3. Operation feasibility:-

CAR SHOWROOM MANAGMENT

 o In The Current System Is When Develop. There Are Two Developer Is
enough Or Require To Develop This System.

No Other Programmers or Developer Are Needed

CAR SHOWROOM MANAGMENT

 (2.2)User requirement:-

 Registration/Login:
User can register and can login to the website.

contact: user can contact

CAR SHOWROOM MANAGMENT

 3- System Requirement and specifications

Admin Side:-

 Register:
This webpage will display Register form.

 ManageUser:
This web page will show all the detail of user which have being
registered to the site.

 ManageBooking:
This webpage will display all the booking in date wise and
venue selected by the user.

CAR SHOWROOM MANAGMENT

4- SDLC

SDLC Overview
SDLC, Software Development Life Cycle is a process used by
software industry to design, develop and test high quality
softwares. The SDLC aims to produce high quality software that
meets or exceeds customer expectations, reaches completion
within times and cost estimates.

SDLC is a process followed for a software project, within a

software organization. It consists of a detailed plan describing how to
develop, maintain, replace and alter or enhance specific software. The
life cycle defines a methodology for improving the quality of software
and the overall development process.

A typical Software Development life cycle consists of

the following stages:

CAR SHOWROOM MANAGMENT

Stage 1: Planning and Requirement Analysis:

Requirement analysis is the most important and fundamental

stage in SDLC. It is performed by the senior members of the team with
inputs from the customer, the sales department, market surveys and
domain experts in the industry. This information is then used to plan
the basic project approach and to conduct product feasibility study in
the economical, operational, and technical areas.
Planning for the quality assurance requirements and
identification of the risks associated with the project is also done in
the planning stage. The outcome of the technical feasibility study is
to define the various technical approaches that can be followed to
implement the project successfully with minimum risks.

Stage 2: Defining Requirements:

Once the requirement analysis is done the next step is to clearly
define and document the product requirements and get them
approved from the customer or the market analysts. This is done
through ‘SRS’ – Software Requirement Specification document which
consists of all the product requirements to be designed and
developed during the project life cycle.

CAR SHOWROOM MANAGMENT

Stage 3: Designing the product architecture:

budget and time constraints , the best design approach is

selected for the product.
A design approach clearly defines all the architectural modules
of the product along with its communication and data flow
representation with the external and third party modules (if any).
The internal design of all the modules of the proposed architecture
should be clearly defined with the minutest of the details in DDS.
Stage 4: Building or Developing the Product:

In this stage of SDLC the actual development starts and the

product is built. The programming code is generated as per DDS during
this stage. If the design is performed in a detailed and organized
manner, code generation can be accomplished without much hassle.

Developers have to follow the coding guidelines defined by their

organization and programming tools like compilers, interpreters,
debuggers etc are used to generate the code. Different high level
programming languages such as C, C++, Pascal, Java, and PHP are used
for coding. The programming language is chosen with respect to the
type of software being developed.

CAR SHOWROOM MANAGMENT

Stage 5: Testing the Product:
This stage is usually a subset of all the stages as in the modern
SDLC models, the testing activities are mostly involved in all the stages
of SDLC. However this stage refers to the testing only stage of the
product where products defects are reported, tracked, fixed and
retested, until the product reaches the quality standards defined in the
SRS.

Stage 6: Deployment in the Market and Maintenance:

Once the product is tested and ready to be deployed it is released

formally in the appropriate market. Sometime product deployment
happens in stages asper the organizations’ business strategy. The
product may first be released in a limited segment and tested in the real
business environment (UAT- User acceptance testing).
Then based on the feedback, the product may be released as it
is or with suggested enhancements in the targeting market segment.
After the product is released in the market, its maintenance is done
for the existing customer base.

CAR SHOWROOM MANAGMENT

5- Overview of .net Technology
ASP.NET is a web application framework developed and marketed
by Microsoft to allow programmers to build dynamic web sites, web
applications and web services. It was first released in January 2002
with version 1.0 of the .NET Framework, and is the successor to
Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on
the Common Language Runtime (CLR), allowing programmers to
write ASP.NET code using any supported .NET language. The
ASP.NET SOAP extension framework allows ASP.NET components to
process SOAP messages.

CAR SHOWROOM MANAGMENT

 History

After the release of Internet Information Services 4.0 in 1997, Microsoft

began researching possibilities for a new web application model that would
solve common complaints about ASP, especially with regard to separation of
[1]
presentation and content and being able to write "clean" code. Mark
Anders, a manager on the IIS team, and Scott Guthrie, who had joined
Microsoft in 1997 after graduating from Duke University, were tasked with
determining what that model would look like. The initial design was
developed over the course of two months by Anders and Guthrie, and
Guthrie coded the initial prototypes during the Christmas holidays in 1997.

The initial prototype was called "XSP"; Guthrie explained in a 2007

interview that, "People would always ask what the X stood for. At the time it
really didn't stand for anything. XML started with that; XSLT started with that.
Everything cools seemed to start with an X, so that's what we originally named
[1] [3]
it." The initial prototype of XSP was done using Java, but it was soon
decided to build the new platform on top of the Common Language Runtime
(CLR), as it offered an object-oriented programming environment, garbage
collection and other features that were seen as desirable features that
Microsoft's Component Object Model platform didn't support.

Mark Anders first demonstrated ASP+ at the ASP Connections conference

in Phoenix, Arizona on May 2, 2000. Demonstrations to the wide public and
initial beta release of ASP+ (and the rest of the .NET Framework) came at the
2000 Professional Developers Conference on July 11, 2000 in Orlando, Florida.
During Bill Gates' keynote presentation, Fujitsu demonstrated ASP+ being used in
[5]
conjunction with COBOL, and support for a variety of other languages was
announced, including Microsoft's new Visual Basic .NET and C# languages, as
well as Python and Perl support by way of interoperability tools created by
[6]
ActiveState.

CAR SHOWROOM MANAGMENT

 Once the ".NET" branding was decided on in the second half of 2000, it was
decided to rename ASP+ to ASP.NET. Mark Anders explained on an
appearance on The MSDN Show that year that, "The .NET initiative is really
about a number of factors, it's about delivering software as a service, it's
about XML and web services and really enhancing the Internet in terms of
what it can do ... we really wanted to bring its name more in line with the
[4]
rest of the platform pieces that make up the .NET framework."

After four years of development, and a series of beta releases in 2000 and 2001,
ASP.NET 1.0 was released on January 5, 2002 as part of version 1.0 of the .NET
Framework. Even prior to the release, dozens of books had been written about
[7]
ASP.NET, and Microsoft promoted it heavily as part of their platform for web
services. Guthrie became the product unit manager for ASP.NET, and
development continued apace, with version.

1.1 being released on April 24, 2003 as a part of Windows Server 2003. This
release focused on improving ASP.NET's support for mobile devices.

CAR SHOWROOM MANAGMENT

 6- System Design
(6.1)Data Flow Diagram:

CAR SHOWROOM MANAGMENT

 E-R Diagram:-

CAR SHOWROOM MANAGMENT

 Data Dictionary

Table1:-LOGIN

ColumnName DataType Constrain

Username varchar(50)
Password varchar(50)

Table2:-BOOKING

ColumnName DataType Constrain

Id varchar(50) -
Name varchar(50) -
Address varchar(50) -
City varchar(50) -
Contact varchar(50)
Email varchar(50)
Date varchar(50)

CAR SHOWROOM MANAGMENT

 Login page

CAR SHOWROOM MANAGMENT

 Home page

CAR SHOWROOM MANAGMENT

 About us

CAR SHOWROOM MANAGMENT

 Contact us page

CAR SHOWROOM MANAGMENT

 Screenshot

CAR SHOWROOM MANAGMENT

CAR SHOWROOM MANAGMENT
CAR SHOWROOM MANAGMENT
CAR SHOWROOM MANAGMENT
 Report

CAR SHOWROOM MANAGMENT

 9. Testing

Testing Principal:-
Following are the testing principal, which are used. All
testing should be traceable to user reuirements.
Tests should be being in small and progress toward testing in the
large.
Exhaustive testing is not possible.
To be most effective testing should be consulted by an
independent third party.
Testing Methods:-

 White box testing or glass box texting

or structural testing.
 Black box testing or function testing.
 Interface testing.

White Box Testing:-

This is concerned with the implementation of the program.in
this type of testing different programming structures and data
structure used in the program are tested for proper operation.
This test concentrates on the examination of the coding. The
system software engineers and programmer join test cases and test
data. The system designer creates test cases that have the like hood
of finding out possible errors.

CAR SHOWROOM MANAGMENT

 Black Box Testing:-
This is concerned with the proper execution of the program
specification. In this testing each function or sub program used in
the main program is first identified.

Interface Testing:-
This is concerned with both program spection and program
implementation .this type of testing is particularly important for
object oriented system.

CAR SHOWROOM MANAGMENT

 10. Enhancements
(9.1) Advantages:-

 Maintain whole system through one Admin.

 Routin work is done more effecitively is less time.
 No extra supported staff needed.
 It is also less costly and more effective system.
 The safety of data is increased to provide

utilities. (9.2) Limitation:-

 Replacement facility is not available.

 Online payment is not allowed.
 Only cash on delivery.

(9.3) Future Scope:-

 We want to do following enhancements in projects.

 Some of limitation is removed by using some
advance technology in future.
 We will also add some additional features so that
admin functionality will be less cumbersome.
 Reminder facility will be providing to user and admin.
 Online help can be introduced into the system.
 Online payment facility will also be included into
the system.

CAR SHOWROOM MANAGMENT

 11. References
Web site

Http://www.w3school.com
Http://www.google.com
Http://www.C# Corner.com

CAR SHOWROOM MANAGMENT

 THANK YOU…

CAR SHOWROOM MANAGMENT

 A
Project Report On

“CAR SHOWROOM MANAGMENT”

Submitted By

1. Rohit Krushnat Jadhav

2. Vishal Balaso Warake

Submitted To,

SHIVAJI UNIVERSITY, KOLHAPUR

FOR THE AWARD OF

BACHELOR OF COMPUTER APPLICATION

(B.C.A-III) Sem-V

Under The Guidance of

Prof. A.C.Kumbhar
Through

SADASHIVRAO MANDLIK MAHAVIDYALAYA, MURGUD

TAL-KAGAL DIST. KOLHAPUR2020-2021

CAR SHOWROOM MANAGMENT

 Shivaji University Kolhapur
SADASHIVRAO MANDLIK
MAHAVIDYALAYAMURGUD TAL-KAGAL
DIST.KOLHAPUR.

CERTIFICATE

This is to certify that the project entitled “Car Showroom managment” submitted
by 1.Rohit krushnat Jadhav 2. Vishal Balaso Warake to Shivaji University Kolhapur,
in partial fulfillment of the degree of B.C.A.-III This project work has been carried out
under my guidance.
The conclusion drawn by them are based on work done and data collected by them during
project work.to the best of our knowledge and belief, the matter presented here has not
been submitted earlier.

Date:
Place: Murgud

HOD EXAMINER GUIDE

Prof. Mr.Kumbhar A.C. 1.

2. Prof. Mr.Kumbhar A.C.

CAR SHOWROOM MANAGMENT

 ‘

-: AKNOWLEDGEMENT :-

It gives us great pleasure to remain deeply indebted to our guide

Pro. A. C .kumbhar. for providing us with the required facilities for

the academic achievement.The faith and confidence shown by him in
us boosted our moral and motivated us to perform better in
performiong this project.
We also remain thankful to our honourable Principal Dr
.A.D.Kumbhar for providing us required resource and motivating us.

Thanking
You,

1. Rohit Krushnat Jadhav

2.Vishal Balaso Warake

CAR SHOWROOM MANAGMENT

CAR SHOWROOM MANAGMENT