PROBLEM STATEMENT

Aim :- To identify a problem and create a problem statement for Parking

Management System

Requirements:-
Clear idea on the project should be required to identify the problem.

Introduction:-
The three main problems that the increasing number of vehicles and the decreasing efficiency of
modern busy parking lots are:

        1. Valuable time wasted from inconvenient and inefficient parking lots

 On average, 3.5 - 12 minutes spent waiting for a spot in urban parking lots \

2. More fuel consumed while idling or driving around parking lots, leading to more CO2 emissions
being produced

 Average distance traveled looking for a spot = 1.2km

 Average CO2 produced per car per day = .14 kg CO2
 14kg for 1000 cars per day and 5110kg per year just for 1000 cars!!

3.Potential accidents caused by abundance of moving vehicles in disorganized parking

lots

 413 accidents occurred in public parking lots in Canada last year

 There were 788 parked car collisions, 5 being fatal
 2/3 of traffic accidents in parking lots involve only 1 moving vehicle
 Parking Structure Issue!

 1/3 of these accidents involved 2 moving vehicles

 Parking System Issue!

Advantages of E-parking Management System:-

 Optimized parking
 Reduced Traffic
 Reduced pollution
 Enhanced User Experience
 New Revenue Streams
 Integrated Payments
 Increased Safety
 Real-Time Data
 Decreased Management Costs
Conclusion:-
So, for this we can say that E-Parking Management System is more Secure and Efficient
Parking system especially in India. For every organization there is a lot of pros and
cons. But there is lot of improvements in Parking Management System. It serves every
people.
 SRS Document

AIM:
To prepare document of software requirements
specification. Designing SRS document for E-Parking
Management System.
Requirements:
To prepare SRS document we need to have
good knowledge on the project and also editor tools like MS
Word required to prepare it.

Table of Contents:-

1. Introduction

1.1 Purpose
1.2 Intended Audience
1.3 Product Scope
1.4 Glossary
2. Overall Description

2.1 Product Perspective

2.2 Product Functions
2.3 User Classes and Characteristics
2.4 Assumption and Dependencies
3. Requirement Specification

3.1Performance Requirements
 3.2Non- Functional Requirements

4. System Features
4.1Hardware Features
4.2Software Features

5.Testing Requirements

5.1 Integration Testing

5.2 Performance and Load Testing

5.3 Security Testing

6.References

1. Introduction
E-Parking management system for managing the records of the incoming and
outgoing vehicles in a parking house It’s an easy for Admin to retrieve the data if the
vehicle has been visited through number, he can get that data. Now days in many
public places such as malls, multiplex system, hospitals, offices, market areas there is
a crucial problem of vehicle parking. The vehicle parking area has many lanes/slots
for car parking. So, to park a vehicle one must look for all the lanes. Moreover, this
involves a lot of manual labor and investment. Instead of vehicle caught in towing
the vehicle can park on safe and security with low cost. Parking control system has
been generated in such a way that it is filled with many secure devices such as,
parking control gates, toll gates, time and attendance machine, car counting system
etc. These features are hereby very necessary nowadays to secure your car and to
evaluate the fee structure for every vehicle’s entry and exit The objective of this
project is to build a Vehicle Parking management system that enables the time
management and control of vehicles using number plate recognition. The system
 that will track the entry and exit of cars, maintain a listing of cars within the parking
lot, and determine if the parking lot is full or not. It will determine the cost of per
vehicle according to their time consumption.

1.1 Purpose
We can park our vehicle in our own slot by paying.
 Because of that there are no towing problems.
 And our vehicle has been parked as a secure condition.
 There is no risk for vehicle owner for parking the car.
 In case of any damages and problem of vehicle that will claim by parking
management.
 As the world is facing many threads daily, robberies are done easily
with no track to trace, bomb blasts occur with the use of vehicle, so if a proper
system is adopted each record can be saved and anyone can be track easily
therefore mainly is to make a better and fast software, most important user-
friendly
 Maintain records in short time of period.
 Determines the parking area is full or not.
 Enhances the visitor’s experience

1.2 Intended Audience

This document is intended for every aspect of people who live in cities
Mostly High Traffic Areas and busy roads. People Easily Book parking plots
and Save time . It leads to decrease in traffic challans.
Mostly who was parking in no parking Areas because of there don’t know
where there is a place to park.

1.3 Product Scope

In the modern age. Many people have vehicles. Vehicle is now a basic
need. Every place is under the process of urbanization. There are many
corporate offices and shopping centers, hospitals, schools, government
organizations etc. So, all these places need a parking space where people
can park their vehicles safely and easily. Every parking area needs a system
that records the detail of vehicles to give the facility. These systems might
be computerized or non-computerized. With the help of computerized
system, we can deliver a good service to customer who wants to park their
vehicle into the any organization’s premises. Vehicle parking management
system is an automatic system which delivers data processing in very high
speed in systematic manner. Development of this system is very useful in
this area of field. We can sell this system to any organization. By using our
 system, they can maintain records very easily. Our system covers every
area of parking management. In coming future there will be excessive
need of Vehicle parking management system. Its motivation is to tackle an
issue that truly annoys numerous sellers today for overseeing of parking
spaces inside a parking story. So, it gives you an exceptionally
oversimplified arrangement of overseeing leaving spaces which furnishes
you with making a passage of approaching and active vehicles. Parking
Management System close to overseeing openings

1.4 Glossary
This should define all technical terms and abbreviations used in this
document.
 API - Application programming Interface
 EPMS - E parking management system
 GUI - Graphical user interface
 IDE - Integrated development environment
 IT - Information technology
 OS - Operating system
 Availability - The quality of being able to be used or obtained.
 Book Chapter - A subdivision of a book or of some categories of
reference work; usually numbered and titled.
 Characteristics - A feature or quality belonging typically to a person,
place, or thing and serving to identify them.
 Component - A uniquely identifiable constituent part of a content
item composed Constraints A limitation or restriction.
 Database - A collection of electronically stored data or unit records
(facts, bibliographic data, texts) with a common user interface and
software for the retrieval and manipulation of data.
 Dependencies - The quality or state of being dependent especially
 Documentation - Material that provides official information or
evidence or that serves as a record.
 Hardware - The machines, wiring, and other physical components of
a computer or other electronic system.
 JAVA, C++ - Programming language
 Maintenance - The process of preserving a condition or situation or
the state of being preserved.
 Quality - attributes A property of a work product or goods by which
its quality will be judged by some stakeholder or stakeholders.
 Requirements - A thing that is compulsory; a necessary condition.
  Scope - The extent of the area or subject matter that something deals
with or to which it is relevant.
 Security - The state of being free from danger or threat
 Software - The programs and other operating information
 SQL - Structure query language
 System - A set of things working together as parts of a mechanism or
an interconnecting network

2 Overall Description:

2.1 Product Perspective

PMS ought to have the option to give an essential and simple exchange of data.
For example, It ought to have the option to eliminate the correspondence holes
between a representative and the client. It ought to be viable with every one of
the working frameworks.

2.2 Product Functions

The PMS login box ought to on the intranet.
 The secret key field ought to be secured
 By tapping on the dropdown box of the choices the worker ought to have
the option to see reports and accessible slots.
 Employee ought to have the option to change the passwords. There are a
lot of functions in E-PMS.
These functions can be placed into broader categories as follows:
 Security over performance
 Efficiency over functionality
 Accessibility in all aspects
 Lightweight and elegant

2.3 User Classes and Characteristics

A client can just have his/her worker ID number as username so assuming
he joins the parking MS then no one but he can login. This forestalls abuse,
unapproved access and hacking of the item.

2.4 Assumptions and Dependencies

PMS should work even at when the organization traffic is high. Server
ought to have a power reinforcement just as a data set reinforcement. The
 PMS ought to be viable with a large portion of the working frameworks for
example past and most recent one

3 Requirement Specification

All the requirements like Software and Hardware are explained here

3.1 Performance Requirements

Accessibility
Accessibility is one of the highest priority features of E-PMS. From
thorough analysis, this accessibility not only includes better UI
Lightweight and Elegant
One of the main or key difference of E-PMS offers least use of hardware
resources while keeping the device’s performance at maximum priority.
This can be achieved by keeping the OS lightweight and only require the
hardware when needed.
Interactive User Interface
The users of current E-PMS are not entirely satisfied with their user
interfaces, whether that be Android users or OS users. They always find
the UI of the other OS more interactive. The goal is to make the UI as
much accessible as possible, and simple at the same time. The OS will be
made more lightweight by providing simple UI as well.
Highly Customizable
The E-PMS is expected to be most customizable in terms of usability. The
different options will contain different sections to customize different
parts to customize information stored in SQL server at back end. it will
basically give the user ability to make the Operating System how they
want. This customization also includes Applications management, how
they should be allowed to use different options to alter data in SQL server
if required. Considering these, Customization is also among one of the
most important features of E-PMS.
3.2 Non- Functional Requirements
User Requirement
 Need for an application that makes communicating easy and
comfortable.
 An application that enables user to park a vehicle with safe and secure.
 Need for an application that is easy to use and widely available and
hence a web application
 Handling all functions done with organization in a computerized
manner.
 Allowing the user to park the vehicle directly.
Security Requirements
The system security problem can be divided into following relates issues.
They determine the file structure, data structure and access procedures.
system security an (operating) system is responsible for controlling access
to system resources, which will include sensitive data. The system must
therefore include a certain amount of protection for such data and must in
turn control access to those parts of the system that administer this
protection. System security is concerned with all aspects of these
arrangements.
Security:
The financial framework should be completely available to just genuine
client. It ought to require pin for passage to another climate Software
Requirements Specification for E-parking management system
System Integrity
State of a system where it is performing its intended functions without
being degraded or impaired by changes or disruptions in its internal or
external environments. That condition of a system wherein its mandated
operational and technical parameters are within the prescribed limits. The
state that exists when there is complete assurance that under all
conditions an IT system is based on the logical correctness and reliability of
the operating system, the logical completeness of the hardware and
software that implement the protection mechanisms and data integrity.
Reliability
The application ought to be profoundly dependable and it ought to create
all the refreshed data in right request.
Availability
Any data about the record ought to be rapidly accessible from any PC to
the approved client. The recently visited client's information should not be
cleared.
Maintainability
The application ought to be viable in such a way that assuming any new
prerequisite happens, it ought to be handily consolidated in an individual
module.
Portability:
The application ought to be versatile on any windows-based framework. It
 ought not be machine explicit.
Robustness:
This is a very critical requirement of any software. During development
stage, the developers will take into consideration all the possible system
failures and will make sure system copes with them, and at least does not
get crashed. Even if, under some circumstances, the OS shuts down
unexpectedly, it will be Kernel’s responsibility to restart the OS as soon as
possible.
System Maintenance and Evaluation:
System Maintenance is a modification of the software product after
delivery to accomplish one of the following objectives:
 Correct faults.
 Improve the performance or other attributes
 Adapt the product to the change environment

4.System Features

4.1Hardware Requirements
It deals with the hardware requirements like Ram size, Cache size,
Processor type, Internal Memory size etc.. required for the software
to run efficiently.
 Pentium IV or above for optimum performance.
 32GB of Internal Memory
 Minimum 2GB of Ram
 Cache 2MB
 Basic Keyboard and Touch Pad
 Standard color monitor

4.2 Software Requirements

 Operating System windows(any version like 7,8.1,10),
 VISUAL STUDIO 2016
 SQL SERVER 2008
The Systems should have Internet connection is secondary requirement. The
Software’s should have security, portability, Efficiency and Flexibility
5.Testing Requirements
In order to publish the project, software testing is one of the main aspects
that a project should undergo. It should be comprehensive and should be
carried out at each stage of development as well as implementation.

It includes integration testing, performance and load testing, security

testing(include penetration and vulnerability testing) etc..

5.1 Integration Testing:-

Integration of different modules is undertaken once they have been coded
and unit tested.

During the integration and system testing phase, modules are integrated
in a planned manner.

5.2 Performance and Load Testing:-

Parking System is very Important in Present days . So, we expect high
traffic and high Parking Slots .So, we need to maintain web server fields.
Because if we don’t maintain customers may face severe problems for
their Parking.
People don’t want to waste time for Parking ,So must and should it need
aa server and load Maintenance

5.3 Security Testing:-

● If the users want to do Parking they will provide their
personal details like phone number, Car Number, Mail
address and House Address.
● In the parking slot booking process users may provide their bank
account details to pay the money.
● So, we need to secure their information by providing some tools
in our website.
6.References
www.google.com
www.youtube.com
https://supportparclick.zendesk.com/hc/en-gb
www.studocu.com
www.SlideShare.com
www.codeproject.com

Conclusion:-
SRS document for E-Parking Management System is created successfully