A Project Report

on
“Vihicle Showroom Management System”

Prepare By:
Harshkumar Budhabhai Talpada

A Report Submitted to
Sardar Patel University
In Partial Fulfilment of
BCA (Bachelor of Computer Applications) Degree
Academic Year: 2020 / 2021

Sardar Patel College of Administration & Management (SPCAM)

Sardar Patel Education Campus(SPEC)
Bakrol-388315

Guided By: Mr. ChintanParmar

 Sardar Patel College of administration & Management

Certificate

This is to certify that Mr/ Ms_Harsh Talpada___________

Seat No ___of BCA – SEM - VI has worked on project entitled

Vehical Showroom Management System from 08/09/2021 to 10/11/2021.

US06CBCA27 Project - IIis in-house project course of two credits.

He/She was regular in his/her work and developed around 70 hours for the
project including analysis and design. He/she has completed the project
satisfactorily.

Director / Head
Project Guide
 Acknowledgement
This project work has been the most practical and exciting part of my learning experience,
which would be an asset for me for my future career. It was a fruitful experience in
developing the project. There were many new things which I learned during development of
the project.

No system is created entirely by an individual. Many people have helped to create this
system and each of their contribution has been valuable. Proper organization of concept and
analysis of the system is due to keen interest and helping hand of my teachers and colleagues.
It is my sincere desire to express my heartfelt gratitude for their guidance as well as support.

My sincere thanks to our DirectorDr. NIRAV TRIVEDI for molding my thoughts and
vision towards all the subjects, I was studying in all these three years.

I am very thankful to Mr. RUTUL PATEL, Head of the Department, who provided this
opportunity for us to work on the project.

I express my deepest gratitude to my project guide Mr. CHINTAN PARMAR, whose

continuous encouragement and valuable suggestions has helped me to complete my project
successfully.

Finally, I am thankful to the entire staff of the B.C.A. department, Sardar Patel University,
and all my colleagues for their kind cooperation. All of these have made my project a
successfully.

Regards
- Harsh Talpada
 CHAPTER 1- INTRODUCTION
1.1 Introduction:

This is a live project which was developed for a Vehicle Showroom. It is useful to the
Management system to maintain the customers details, Sales Detail, Company items and
services and also vehicle details.

1.2 Organization profile

SPEC is a student centric, multidisciplinary, research and holistic development oriented not
for profit campus with a view to promote welfare. Within a short span of time, since 2007 till
date, it has emerged as a campus known for teaching-learning-activities across the state of
Gujarat. The campus, spread across the sprawling lush green environment and a bit away
from noise and pollution of city, has number of institutes, named after Iron man of India –
Shri Sardar Vallabhbhai Patel, including SPCP, SPCE(ENGG),SPCAM - MBA,
SPCAM(BBA,BCA,BBA/ISM), SPCC(B.com), SPCE(B.ED) and SPIAS. All technically
professional courses are affiliated with Gujarat Technological University and other courses
are affiliated with Sardar Patel University.

1.3 Purpose of the project

The main purpose for preparing this document is to give a general insight into the analysis
and requirements of the existing system or situation and for determining the operating
characteristics of the system.

1.4 Problem in Existing System

The existing system is effect less No feedback for all. No proper maintenance of records.
Disadvantages of Existing System
• It is difficult for the manager to maintain the stock.
• On users side can’t find good interface.

• Manager has to keep of all details securely.

1.5 Solution of These Problems

 Chapter 2 : System Analysis

2.1 Introduction
System Analysis is a very critical activity while developing a application. This stage
involves study of existing system and interacting with users, which determines user and their
expectation of the proposed system. Cost of incorporating changes required by the user is
very
less at this stage, which steeply increases as development advances.

2.2System Workflow

2.3 Study of the System

2.4. Hardware & Software Requirement

Hardware Requirement
 Core i5(Processor
 4 GB RAM
 3 MB Cache memory
 Hard Disk 10 GB
Software requirements
 Operating System: Windows xp
 Windows 10
 WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)
 Visual Studio .Net 2005 Enterprise Edition
 Internet Information Server 5.0 (IIS)
 Visual Studio .Net Framework (Minimal for Deployment)
 SQL Server 2000 Enterprise Edition
2.5 Proposed System
The main purpose for preparing this document is to give a general insight into the analysis
and requirements of the existing system or situation and for determining the operating
characteristics of the system.

2.6 Input & Output

INPUTS:

Head operator enters his or her user id and password.

Operators enter his or her user id and password.
Technicians enter his or her user id and password.
Sub technicians enter his or her user id and password.
User requests the reports.
User requests the search.
Head operator can edits the personal details and so on.

OUTPUTS:

1 Head operator receives personal details.

1 Operator receives the personal details.
2 Technicians receive personal and technical details.
3 Users receive requested reports.
4 5 Displays search result.

2.7 Process Model

1.2 Need of the Project:

The aim of this project is to develop an vehicle showroom details and managing system. To
produce a web based system that allow the company to effectively manage their vehicle
business.

1.3 Product Scope

We all know the importance of computerization. The world is moving ahead at lightning
speed and everyone is running short of time. One always wants to get the information and
perform a task he/she/they desire(s) within a short period of time and too with amount of
efficiency and accuracy. The application areas for the computerization have been selected on
the basis of following factors:
 Minimizing the manual records kept at different locations.

 There will be more data integrity.

 Facilitating desired information display, very quickly, by retrieving information from

users.

 Facilitating various statistical information which helps in decision-making?

 To reduce manual efforts in activities that involved repetitive work.

 Updating and deletion of such a huge amount of data will become easier.
 CHAPTER 2- SRS
1. Introduction

4.1 Purpose
The main purpose for preparing this document is to give a general insight into the analysis
and requirements of the existing system or situation and for determining the operating
characteristics of the system.

1.2 Document Conventions

When writing this SRS for the Vehicle showroom management system, the following
terminologies and standards are used:

● Application Program Interface (API): Set of programming instructions and

standards for accessing a Web based software application or Web tool.
● Application : a software or program which is designed for use by an end-user for specific
operations.
1.3 Product Scope
This Document plays a vital role in the development life cycle (SDLC) and it describes the
complete requirement of the system. It is meant for use by the developers and will be the basic
during testing phase. Any changes made to the requirements in the future will have to go through
formal change approval process. viii
2. Overall Description

2.1 Product Perspective

A strategy where we architect, integrate and manage technology services and solutions - we call
it AIM for success.
A robust offshore development methodology and reduced demand on customer resources.
A focus on the use of reusable frameworks to provide cost and times benefits.
They combine the best people, processes and technology to achieve excellent results -
consistency. We offer customers the advantages of:
They understand the importance of timing, of getting there before the competition. A rich
portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested
methodology ensures that we follow a predictable, low - risk path to achieve results. Our track
record is testimony to complex projects delivered within and evens before schedule.
Our teams combine cutting edge technology skills with rich domain expertise. What’s equally
important - they share a strong customer orientation that means they actually start by listening to
the customer. They’re focused on coming up with solutions that serve customer requirements
today and anticipate future needs.

2.2 Product Functions

As far as the project is developed the functionality is simple, the objective of the proposal is to
strengthen the functioning of Audit Status Monitoring and make them effective and better. The
entire scope has been classified into five streams knows as Coordinator Level, management
Level, Auditor Level, User Level and State Web Coordinator Level. The proposed software will
cover the information needs with respect to each request of the user group viz. accepting the
request, providing vulnerability document report and the current status of the audit. ix
2.3 User Classes and Characteristics
The initial users of our application front end will be health and/or fitness conscious individuals
who are familiar with operating application .Health and/or fitness conscious individuals that may
use this application include (but are not limited to), personal trainers, athletes, dieters, and people
looking to live a healthy life. This software application will not be focused on meeting the needs
of people not interested in personal health.

3. System Features

3.1 Functional Requirements

As far as the project is developed the functionality is simple, the objective of the proposal is to
strengthen the functioning of Audit Status Monitoring and make them effective and better. The
entire scope has been classified into five streams knows as Coordinator Level, management
Level, Auditor Level, User Level and State Web Coordinator Level. The proposed software will
cover the information needs with respect to each request of the user group viz. accepting the
request, providing vulnerability document report and the current status of the audit.

INPUT AND OUTPUT

The main inputs, outputs and major functions of the system are as follows
4. Other Requirements and Concerns

4.1 Nonfunctional Requirements

Preliminary investigation examine project feasibility, the likelihood the system will be useful to
the organization. The main objective of the feasibility study is to test the Technical, Operational
and Economical feasibility for adding new modules and debugging old running system. All
system is feasible if they are unlimited resources and infinite time. There are aspects in the
feasibility study portion of the preliminary investigation:
1 Technical Feasibility
2 Operation Feasibility
3 Economical Feasibility

Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes the
following:
1 Does the necessary technology exist to do what is suggested?
2 Do the proposed equipments have the technical capacity to hold the data required to use the
new system?
3 Will the proposed system provide adequate response to inquiries, regardless of the number or
location of users?
4 Can the system be upgraded if developed?
5 Are there technical guarantees of accuracy, reliability, ease of access and
data security?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System’.
The current system developed is technically feasible. It is a web based user interface for audit
workflow at NIC-CSD. Thus it provides an easy access to the users. The database’s purpose is to
create, establish and maintain a workflow among various entities in order to facilitate all
concerned users in their various capacities or roles. Permission to the users would be granted
based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability
and security. The software and hard requirements for the development of this project are not
many and are already available in-house at NIC or are available as free as open source. The work
for the project is done with the current equipment and existing software technology. Necessary
bandwidth exists for providing a fast feedback to the users irrespective of the number of users
using the system.

Operational Feasibility

Proposed projects are beneficial only if they can be turned out into information system. That will
meet the organization’s operating requirements. Operational feasibility aspects of the project are
to be taken as an important part of the project implementation. Some of the important issues
raised are to test the operational feasibility of a project includes the following: -
1 Is there sufficient support for the management from the users?
2 Will the system be used and work properly if it is being developed and
implemented?
3 Will there be any resistance from the user that will undermine the possible application
benefits?

This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the
management issues and user requirements have been taken into consideration. So there is no
question of resistance from the users that can undermine the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer resources and
would help in the improvement of performance status.

Economic Feasibility

A system can be developed technically and that will be used if installed must still be a good
investment for the organization. In the economical feasibility, the development cost in creating
the system is evaluated against the ultimate benefit derived from the new systems. Financial
benefits must equal or exceed the costs. xii
The system is economically feasible. It does not require any addition hardware or software. Since
the interface for this system is developed using the existing resources and technologies available
at NIC, There is nominal expenditure and economical feasibility for certain.
4.2 Security and Confidentiality Requirements
SYSTEM SECURITY refers to the technical innovations and procedures applied to the
hardware and operation systems to protect against deliberate or accidental damage from a defined
threat.
DATA SECURITY is the protection of data from loss, disclosure, modification and destruction.
SYSTEM INTEGRITY refers to the power functioning of hardware and programs, appropriate
physical security and safety against external threats such as eavesdropping and wiretapping.
PRIVACY defines the rights of the user or organizations to determine what information they are
willing to share with or accept from others and how the organization can be protected against
unwelcome, unfair or excessive dissemination of information about it.
CONFIDENTIALITY is a special status given to sensitive information in a database to
minimize the possible invasion of privacy. It is an attribute of information that characterizes its
need for protection.
4.3 Safety Concerns
System security refers to various validations on data in form of checks and controls to avoid the
system from failing. It is always important to ensure that only valid data is entered and only valid
operations are performed on the system. The system employees two types of checks and controls:
Technology Used: ASP.net
Operating System Used: Windows 10 / 8 xiii

Front-End:
As we know that such computer language can be use in software development, which must have
the following criteria
 Convenient in coding
 Lesser input provides larger output
 Highly efficient and productive
 Compatibility with other language and other tools

User Interface:
USER INTERFACE DESIGN
It is essential to consult the system users and discuss their needs while designing the user
interface: xiv
USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS:
1. User initiated interface the user is in charge, controlling the progress of the user/computer
dialogue. In the computer-initiated interface, the computer selects the next stage in the
interaction.
2. Computer initiated interfaces

In the computer initiated interfaces the computer guides the progress of the user/computer
dialogue. Information is displayed and the user response of the computer takes action or displays
further information.
USER_INITIATED INTERGFACES
User initiated interfaces fall into two approximate classes:
1. Command driven interfaces: In this type of interface the user inputs commands or queries
which are interpreted by the computer.
2. Forms oriented interface: The user calls up an image of the form to his/her screen and fills in
the form. The forms oriented interface is chosen because it is the best choice.
xv
CHAPTER-3
3.1 ER diagram for project:
Fig(1)
3.2 UML diagram : xvi xvii
3.3 DFD DIAGRAM
Level 0: xviii
Level 1: xix
Level 2: xx
3.4 System sequence diagram for the project xxi
CHAPTER-4
Methodology
Model View Controller or MVC as it is popularly called, is a software design pattern for
developing web applications. A model View Controller pattern is made up of the following three
parts:
 Model - The lowest level of the pattern which is responsible for maintaining data.
 View – This is responsible for displaying all or a portion of the data to the user.

 Controller – Software Code that controls the interactions between the model and view.

MVC is popular as it isolates the application logic from the user interface layer and supports
separation of concerns. Here the controller receives all request for the application and then
works with the model to prepare any data needed by the view. The View then uses the data
prepared by the controller to generate a final presentable response. The MVC abstraction can
be graphically represented as follows.