100% found this document useful (1 vote)
2K views37 pages

Car Parking Management System

This document presents a parking management system based on image processing that was developed by Muhammad Naqash and Sufyan Nazir. The system aims to help drivers easily find empty parking spots through image processing techniques. It analyzes images taken of the parking lot to identify vacant spots rather than having drivers waste time searching. The system was developed in software and makes the parking process more efficient for both drivers and administrators. It includes chapters on the existing system analysis, proposed new system, system design, and implementation details.

Uploaded by

hafeez ahmed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
2K views37 pages

Car Parking Management System

This document presents a parking management system based on image processing that was developed by Muhammad Naqash and Sufyan Nazir. The system aims to help drivers easily find empty parking spots through image processing techniques. It analyzes images taken of the parking lot to identify vacant spots rather than having drivers waste time searching. The system was developed in software and makes the parking process more efficient for both drivers and administrators. It includes chapters on the existing system analysis, proposed new system, system design, and implementation details.

Uploaded by

hafeez ahmed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 37

CAR PARKING MANAGEMENT SYSTEM BASED ON IMAGE

PROCESSING

Submitted By:

Name Registration No

Muhammad Naqash 2015-UKT-001565

Sufyan Nazir 2015-UKT-001551

Supervised By:

Mam Sundas Iftikhar

Department of CS & IT

Faculty of Computing & Engineering

University of Kotli Azad Jammu & Kashmir


APPROVAL CERTIFICATE

It is certified that the project work presented in this report entitled “Parking Management

System based on Image Processing” submitted by Sufyan Nazir (2015-UKT-001551),M

Naqash (2015-UKT-001565), of Session (2015-19) supervised by Mam Sundas. Our

opinion is fully adequate in scope and quality of Bachelor of Science (Computer

Science).

Examination Committee
Internal Supervisor Mam. Sundas Iftikhar

Lecturer,

Department of CS & IT

Faculty of Computing and Engineering

University of Kotli Azad Jammu and Kashmir. Signature:

External Examiner: Signature:

ii
ABSTRACT
Enrollments into the university have been increasing steadily. As the number increases,
various problems arise. One such problem is to find a parking spot at the university. To
make things easier for the students, faculty and the staff, it is important to have a parking
management with image processing system. This system can help reduce the time to find
an empty parking spot. We can give the total number of empty slots and also where exact
the empty parking slot is. This helps drivers to find parking easily. This Paper aims to
present a smart parking solution using image processing technique. By having this image,
the particular car park vacant can be known rather than wasting time to find one. This
proposed system has been developed in software platform. This parking system makes the
whole process of parking cars more efficient and less complex for both drivers and
administrators. Keywords: Smart parking, Image processing, intelligent parking, time
saving parking.

iii
UNDERTAKING
We declare that this system, neither as a whole nor as a part has been copied from any
other source. It is further declared that we have completed. our project entirely on the
basis of our personal effort made under the sincere guidance of our teachers. No
portion of the work presented in this report has been submitted in support of any
application for any other degree or qualification of this or any other university or institute
of learning. If any part of this project and write up is proved to be copied out or there is any
duplication of code then I will be responsible for the consequences.
We declare that research/project work titled “Car parking management system based on
image processing” is my own work. The work has not been presented elsewhere for
assessment. Where material has been used from other sources it has been properly
acknowledged / referred.

Muhammad Naqash:

Sufyan Nazir:

iv
ACKNOWLEDGEMENTS
All the praise to Allah, who has blessed us with the courage and knowledge to achieve my
goal. We can never thank Him enough for His countless blessings upon me. Salam to
Prophet Mohammad (S.A.W), who is and will always be a source of guidance and
knowledge for humanity.
For us, a milestone of this nature would never have been possible to achieve without the
support of galaxy of some truly loving and kind people in my life. No words can fully
describe my feelings of respect and gratitude for my affectionate parents, supporting
sibling and friends, whose love, encouragement and prayers invariably buoyed me up.
Their concern, love and support can never be paid back.
We owe a lot of sincere gratitude to my respected supervisor Madam Sundas Iftikhar,
whose true guidance, positive criticism and sincere encouragement made me to get to my
destination. She became a source of inspiration for me and kept me moving in the right
direction towards my goal.

Muhammad Naqash
Sufyan Nazir

v
Contents
APPROVAL CERTIFICATE ................................................................................................ii
ABSTRACT ..........................................................................................................................iii
UNDERTAKING .................................................................................................................. iv
ACKNOWLEDGEMENTS ................................................................................................... v
Chapter 1 ................................................................................................................................ 1
1 INTRODUCTION ............................................................................................................... 1
1.1 Problem Statement ........................................................................................................ 1
1.2 Objectives: .................................................................................................................... 1
1.3 How will it work? ......................................................................................................... 2
1.4 Benefits and Feasibility ................................................................................................ 2
1.5 Scope: ........................................................................................................................... 2
1.6 Definition and terms ..................................................................................................... 3
1.6.1 Conceptual Definition ............................................................................................ 3
1.7 Operational Definition .................................................................................................. 5
Chapter 02 .............................................................................................................................. 6
2 EXISTING SYSTEM ANALYSIS ..................................................................................... 6
2.1 Introduction................................................................................................................... 6
2.2 Technical Feasibility..................................................................................................... 6
2.3 Financial Feasibility...................................................................................................... 6
2.4 Resource Feasibility...................................................................................................... 6
2.5 Design and Implementation Constraints ....................................................................... 7
2.6 User Documentation ..................................................................................................... 7
2.7 Assumptions and Dependencies ................................................................................... 7
Chapter 3 ................................................................................................................................ 8
3 PROPOSED SYSTEM ........................................................................................................ 8
3.1 Functional Requirements .............................................................................................. 9
3.2 Non-functional Requirement ........................................................................................ 9
3.3 User Requirements........................................................................................................ 9
3.4 Operating Environment ................................................................................................ 9
3.5 External Interface Requirements ................................................................................ 10
3.5.1 User Interfaces ..................................................................................................... 10
3.5.2 Hardware Interfaces ............................................................................................. 10
3.6 System Features .......................................................................................................... 10
3.7 System Requirements ................................................................................................. 10
vi
Chapter 4 .............................................................................................................................. 11
4 SYSTEM DESIGN............................................................................................................ 11
4.1 System Design ............................................................................................................ 11
4.2 Design Approach ........................................................................................................ 12
4.3 Use Cases .................................................................................................................... 12
4.3.1 Use Case Diagrams .............................................................................................. 12
4.4 Data Flow Diagram..................................................................................................... 13
Chapter 5 .............................................................................................................................. 15
5 SYSTEM IMPLEMENTATION ...................................................................................... 15
5.1 SQL Store procedure .................................................................................................. 15
5.1.1 Benefits of using stored procedures ..................................................................... 15
5.2 Form Coding ............................................................................................................... 15
5.3 Row Coding ................................................................................................................ 17
5.4 Data Access Layer ...................................................................................................... 19
5.5 Main form data ........................................................................................................... 20
Chapter 6 .............................................................................................................................. 22
6 SYSTEM TESTING AND EVALUATION ..................................................................... 22
6.1 Testing and Debugging ............................................................................................... 22
6.1.1 Verification .......................................................................................................... 22
6.1.2 Validation ............................................................................................................. 22
6.2 Basics of Software Testing ......................................................................................... 22
6.2.1 Black box testing .................................................................................................. 22
6.2.2 White box testing ................................................................................................. 22
6.3 Functional and Non-Functional Testing ..................................................................... 23
6.3.1 Functional testing ................................................................................................. 23
6.3.2 Non-functional testing.......................................................................................... 23
6.4 Aim of Testing ............................................................................................................ 23
6.4.1 Unit Testing.......................................................................................................... 23
Chapter 7 .............................................................................................................................. 26
7 FUTURE EXTENSION .................................................................................................... 26
7.1 Introduction................................................................................................................. 26
7.2 Discussion ................................................................................................................... 26
REFERENCES ..................................................................................................................... 27

vii
LIST OF FIGURES
Figure 1. 1: Arduino UNO ..................................................................................................... 3
Figure 1. 2 LPR Camera ......................................................................................................... 4
Figure 1. 3: IR Motion Detector Sensor ................................................................................. 4
Figure 1. 4: Servo Motor ........................................................................................................ 4
Figure 3. 1: Overview of Car Management System ............................................................... 8
Figure 4. 1: Use Case Diagram for Car Parking Management System ................................ 21
Figure 4. 2 Data Flow Diagram for System ......................................................................... 22

viii
LIST OF TABLES
Table 1: Financial Feasibility .........................................................................................................15

ix
Chapter 1

1 INTRODUCTION
This document is a proposal for the design and development of a Vehicle Parking
management system. Parking management system for managing the records of the incoming
and outgoing vehicles in an 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. The vehicle parking area has many lanes/slots for car parking. So to park a
vehicle one has to look for all the lanes. Moreover, this involves a lot of manual labour 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.
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 Problem Statement


Now a days in parking like valet parking they maintain just with the tokens and they have
records the vehicle details in books so that during some critical situations like police enquiry
of terrorist car or vehicle roberrer that case it is difficult to find the details of particular
vehicle but in this case is easy to find in 1to 2 seconds
By parking the vehicle in public place the vehicle can be claimed by towing person but in this
case there is no towing problems and no need to give fine for anything we can park our
vehicle with securely.

1.2 Objectives:
• 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.
• Maintain records in short time of period.
• Determines the parking area is full or not.
• Enhances the visitor’s experience.

1
1.3 How will it work?
As the system is a data base system, so it will save record of the vehicles. Admin will be able
to add records, update records, search records, delete records, and lot of other functions
related to University’s purpose. The system will cover all the aspects of the Automatic
system with some extra and advanced features facilitating the targeted users.

1.4 Benefits and Feasibility


➢ Benefits
• Maintain records in short time of period.
• Determines the parking area is full or not.
• enhances the visitor’s experience.
➢ Feasibility: -
Many metropolitan areas have seen explosive growth in the number of visitors and
patrons due to urban revitalization, extension of transit services into suburban areas, and
the general trend toward increased mobility of our society. As a result, Vehicle parking is
becoming a major Concern. Development of Computerized Vehicle parking system will
be essential in this field.

1.5 Scope:
Vehicle is now a basic need. There are many administration offices and other departments
etc. There is also a canteen place where student used to go for refreshment. 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. Parking is a growing need of the time. 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 the every area
of parking management. In coming future there will be excessive need of Vehicle parking
management system.

2
1.6 Definition and terms
This section includes important or key terms that should be clearly defined.
Definitions of terms
may be of two categories:
• Conceptual Definition.
• Operational Definition.
1.6.1 Conceptual Definition
These are words usually taken from the dictionary and having universal meaning to
understand by people.

Arduino UNO: A sketch is a program written in a high-level language to run the Arduino
Uno. A sketch is written which makes compatibility among the microcontroller, it can
provide the AC to other microcontrollers. It has a storage capacity to save the program
about what happened with the other microcontroller that are connected to the Arduino.

Figure 1. 1: Arduino UNO

Camera:
License plate capture cameras, also known as license plate recognition / LPR cameras, are
a specialized type of video surveillance camera designed to capture numbers and letters of
license plates on still or moving vehicles. LPR cameras are designed with built-in
software and hardware that compensates for speed, weather, and headlight glare. Regular
security cameras typically can not compensate for these variables to capture a usable
video that identifies license plate numbers. This page contains analog CCTV, HD-over-
Coax, network IP LPR cameras.

3
Figure 1. 2 LPR Camera

IR Motion Detector Sensor: A PIR sensor or passive sensor is an electronic sensor that measures
infrared light radiating and motion from objects in its field. It has powerful functions and low cost
advantages that’s why it is commonly used in automation projects.

Figure 1. 3: IR Motion Detector Sensor


Servo Motor: A servo motor is an electrical device which can push or rotate an object with
great precision. If you want to rotate and object at some specific angles or distance, then you
use servo motor. It is just made up of simple motor which run through servo mechanism. If
motor is used is DC powered then it is called DC servo motor, and if it is AC powered motor
then it is called AC servo motor. We can get a very high torque servo motor in a small and
light weight packages. Doe to these features they are being used in many applications like toy
car, RC helicopters and planes, Robotics, Machine etc.

Figure 1. 4: Servo Motor

4
LCD GSM 16*2: LCD modules form a very important part in many arduino based embedded
system designs. So the knowledge on interfacing LCD module to arduino is very essential in
designing embedded systems. JHD162A is a 16×2 LCD module based on the HD44780
driver from Hitachi. The JHD162A has 16 pins and can be operated in 4-bit mode (using
only 4 data lines) or 8-bit mode (using all 8 data lines).

1.7 Operational Definition


Operational definition words express the meaning of the terms as used in a specific field of study.

• Arduino UNO controls the behavior of the device on the actions performed by
user.
• Cameras used for checking the number plates
• IR Motion Detector Sensor provides the security alarm by just detecting the
motion in his range.
• Servo Motors is used for barriers
• LCD is used to check the parking slots available or not

5
Chapter 02
2 EXISTING SYSTEM ANALYSIS
2.1 Introduction
This Feasibility Study had been used to provide an analysis of the objectives, requirements,
and system concepts of the proposed system, including justification, schedule, and end products.
During this analysis, the objectives of the system are defined based on the needed functions
described previously. Included in these system objectives are the high-level functional and
performance objectives and any assumptions and constraints. When the system objectives have
been identified, the various alternatives for satisfying those objectives are determined. For each
alternative, the costs in time and resources are estimated. A determination is then made as to the
most feasible development alternative.
An overall study of the project has been carried out and the findings have been listed in this
report. The feasibility of “Car Parking Management System” can be ascertained on the following
assessments:

2.2 Technical Feasibility


Feasibility of technological aspects and data set, e.g. the databases/APIs needed etc.

2.3 Financial Feasibility


Feasibility of financial aspects e.g. pricing and source of availability and financing of
tools and other resources required for the project. Provide a tabulated information in the
given format:
Resource Name Price Source
Arduino UNO 1500 Locally available
Cameras 1500 Locally available
PIR Sensor 1200 Locally available
Servo Motors 1500 Locally available
Other components 3000 Locally available
Sponsors/Funding Self-Support
sources
Table 1: Financial Feasibility

2.4 Resource Feasibility


Availability and way of acquisition of resources (both hardware and software) from local market
or online purchase (if any).

6
2.5 Design and Implementation Constraints
➢ This is a complex system, so we have a limited timeframe to complete this project.
This is a major constraint.
➢ There is a huge problem of electricity, so it is a main constraint for our system to
implement.
➢ We are also facing some financial problems as we have to complete the project in the
limited finance.

2.6 User Documentation


A user manual is finally delivered to the target users along with the system so that they could
easily understand how to use the system.

2.7 Assumptions and Dependencies


➢ One activity depends on the other activity as far as the development of the project is
concern if we slip the schedule of one activity it might affect the whole project.

➢ If we cannot complete the project on schedule it will affect the overall project.
➢ We are depending on the network if it is properly functioning then our user can achieve
all functionality else it cannot work properly.
➢ The computer systems must be functioning properly if they are not functioning then our
project will not work properly so it is dependent on the computer systems.

7
Chapter 3
3 PROPOSED SYSTEM
System requirements are more detailed descriptions of the software system’s functions,
services, and operational constraints. The system requirements document (sometimes called a
functional specification) should define exactly what is to be implemented. It may be part of
the contract between the system buyer and the software Product Perspective

The system for “Car parking management system based on image processing” is completely
Automatic. The advantages of computerized over Automatic systems are obvious and
unbeatable. Currently most of the systems are moved towards computerized system to have a
compatibility with current generation and trends of evolving technologies and working
techniques.

Figure 3. 1: Overview of Car Management System

The following picture gives an overview of how this system is going to work. The
system administrator of the Car Parking Management system has the ability to add a new
appliance or delete an existing one.

8
3.1 Functional Requirements
These are statements of services the system should provide, how the system should react to
particular inputs, and how the system should behave in particular situations. In some cases,
the functional requirements may also explicitly state what the system should not do. The
functional requirements for a system describe what the system should do.

• Admin need to enter all details for registration.


• Admin need to insert all details about customer and vehicle.
• Admin need to save all the details of customer and vehicle.
• Admin can retrieve the details of customer.
• Admin must generate a report for payment.

3.2 Non-functional Requirement


• Usability: It has appropriate user interface and adequate information to guide the user
in order to use the system.
• Flexibility: It is very flexible
• Security: This system provides user and authentication so that only the legitimate
user are allowed to use the system.
• Maintainability: This system is capable to secure the data and easily retrieve the
data.
• Scalability: This system can further modified in future.

3.3 User Requirements


• 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.

3.4 Operating Environment


• Microsoft windows 10
• MATLAB
• C
• Design and Implementation Constraints

9
3.5 External Interface Requirements
3.5.1 User Interfaces
UI will be designed, using MATLAB
3.5.2 Hardware Interfaces
Client server architecture will be used.
3.5.3 Software Interfaces
MATLAB

3.6 System Features


• Image processing
• Registration of new vehicles
• Vehicles management System
3.7 System Requirements
These requirements are broad system requirements derived from policies and procedures in
the customer’s and developer’s organization. Examples include operational process
requirements that define how the system will be used, development process requirements that
specify the programming language, the development environment or process standards to be
used, and environmental requirements that specify the operating environment of the system.
[Sommerville-2009]

For development, we are using these tools:

Database Tool: MATLAB

Development Tools: MATLAB

Programming Language: C

10
Chapter 4
4 SYSTEM DESIGN
4.1 System Design
Design is the first step in the development phase for any engineered product or system. The
designer’s goal is to produce a model or representation of a class that will later be built.
Beginning, once system requirement has been specified and analyzed, system design is the
first of the three technical activities -design, code and test that is required to build and verify
software. This document details out the overall software design.
The importance can be stated with a single word “Quality”. Design is the place where quality
is fostered in software development. Design provides us with representations of software that
can assess for quality. Design is the only way that we can accurately translate a customer’s
view into a finished software product or system. Software design serves as a foundation for
all the software engineering steps that follow. Without a strong design, we risk building an
unstable system that will be difficult to test, one whose quality cannot be assessed until the
last stage.
During design, progressive refinement of data structure, program structure, and procedural
details are developed reviewed and documented. System design can be viewed from either
technical or project management perspective. From the technical point of view, design is
comprised of four activities – architectural design, data structure design, interface design and
procedural design.
The development team devises a high-level strategy, the system architecture, for solving the
application problem. They also establish policies that will serve as a default for the
subsequent, more detailed portions of design. The system designer must decide what
performance characteristics to optimize, choose a strategy of attacking the problem, and make
tentative resource allocations. For example, the system designer might decide that changes to
the workstation screen must be fast and smooth, even when windows are moved or erased,
and choose an appropriate communications protocol and memory buffering strategy.
We find it useful to model a system from three related but different perspectives, each
capturing important aspects of the system, but all required for a complete description. The
class model represents the static, structural, “data” aspects of a system. The state model
describes the temporal, behavioral, “control” aspects of a system. The interaction model
represents the collaboration of individual objects, the “interaction” aspects of a system. A
typical software incorporates all the three aspects: it uses data structures (class model), it

11
sequences operations in time (state model), and it passes data and control among objects
(interaction model). [Balaha M, Rumbaugh J-2005]
4.2 Design Approach
Design approach for this software is conventional, that is, database model used is relational
and on the other side Object Modeling Technique (OMT) is used.

4.3 Use Cases


A use case is a coherent piece of functionality that a system can provide by interacting
with various actors. Each use case involves one or more actors as well as the system itself.
The actor needs not all be the persons.
A use case involves a sequence of messages among the system and its actors. Some
use cases have a fixed sequence of messages. More often, however, the message sequence
may have some variations. [Balaha M, Rumbaugh J-2005]
4.3.1 Use Case Diagrams
A system involves a set of use cases and a set of actors. Each use case represents a slice of
the functionality the system provides. The set of use cases shows the complete functionality
of the system at some level of detail. Similarly, each actor represents one kind of object for
which the system can perform behavior. The set of actors represents the complete set of
objects that the system can serve. Objects accumulate behaviour from all the systems with
which they interact as actors. [Balaha M, Rumbaugh J-2005]
The system involves a set of use cases like add record, search record, update record, delete
record and some other mention in use diagram with actors like Administrator and User.
Simply use cases define; in how many ways a system can be used or in how many ways a
system can act. Use cases show the complete functionality of the system that it provides. Use
case summaries briefly describe the purpose and working of each use case. Figure given
below presents a use case summary for PMSIP. Use case diagram is used to capture the
dynamic nature of a system. It consists of use cases, actors and their relationships. It is used
at a high level design to capture the requirements of a system.

12
Figure 4. 1: Use Case Diagram for Car Parking Management System

4.4 Data Flow Diagram


A sequence diagram shows the interaction of a system with its actors to perform all or part of
use case.

13
Figure 4. 2 Data Flow Diagram for System

14
Chapter 5
5 SYSTEM IMPLEMENTATION
Implementation is the carrying out, execution, or practice of a plan, a method, or any design,
idea, model, specification, standard or policy for doing something. As such, implementation
is the action that must follow any preliminary thinking in order for something to actually
happen.
5.1 SQL Store procedure
A stored procedure is a set of Structured Query Language (SQL) statements with an assigned
name, which are stored in a relational database management system as a group, so it can be
reused and shared by multiple programs. Stored procedures can access or modify data in
a database, but it is not tied to a specific database or object, which offers a number of
advantages.
5.1.1 Benefits of using stored procedures
A stored procedure provides an important layer of security between the user interface and the
database. It supports security through data access controls because Admin may enter or
change data. A stored procedure preserves data integrity because information is entered in a
consistent manner. It improves productivity because statements in a stored procedure only
must be written once. The store procedure of generate ad are given below.

5.2 Form Coding


using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
using Zen.Barcode;
namespace Car
{
public partial class Form1 : Form
{

15
Model.carEntities1 db = new Model.carEntities1();
public Form1()
{
InitializeComponent();
}
private void button1_Click(object sender, EventArgs e)
{
if (txt_vname.Text == "" || txt_model.Text == "" || txt_number.Text == "" ||
txt_phone.Text == "" || txt_vcname.Text == ""|| txt_cnic.Text=="")
{
MessageBox.Show("Please Enter Full Information");
}
else
{
Model.carInformation carInformation = new Model.carInformation();
carInformation.Model = txt_model.Text;
carInformation.OwnerName = txt_vname.Text;
carInformation.OwnerNic = txt_cnic.Text;
carInformation.OwnerPhone = txt_phone.Text;
carInformation.VacleName = txt_vcname.Text;
carInformation.VacleNumber = txt_number.Text;
db.carInformations.Add(carInformation);
db.SaveChanges();
dataGridView1.DataSource = db.carInformations.ToList();
txt_model.Text ="";
txt_vcname.Text ="" ;
txt_cnic.Text ="" ;
txt_phone.Text ="" ;
txt_vcname.Text ="" ;
txt_number.Text ="" ;
}
}
private void Form1_Load(object sender, EventArgs e)
{

16
button3.Visible = false;
dataGridView1.DataSource = db.carInformations.ToList();
}
private void txt_number_TextChanged(object sender, EventArgs e)
{
try
{
Zen.Barcode.Code128BarcodeDraw br =
Zen.Barcode.BarcodeDrawFactory.Code128WithChecksum;
pictureBox1.Image = br.Draw(txt_number.Text, 50)
}
catch (Exception l)
{

5.3 Row Coding


private void Form1_Load(object sender, EventArgs e)
{
button3.Visible = false;
dataGridView1.DataSource = db.carInformations.ToList();

private void txt_number_TextChanged(object sender, EventArgs e)


{
try
{
Zen.Barcode.Code128BarcodeDraw br =
Zen.Barcode.BarcodeDrawFactory.Code128WithChecksum;
pictureBox1.Image = br.Draw(txt_number.Text, 50);

}
catch (Exception l)
{

17
// throw;
}
}

private void button2_Click(object sender, EventArgs e)


{
SaveFileDialog dialog = new SaveFileDialog();
if (dialog.ShowDialog() == DialogResult.OK)
{
int width = Convert.ToInt32(pictureBox1.Width);
int height = Convert.ToInt32(pictureBox1.Height);
Bitmap bmp = new Bitmap(width, height);
pictureBox1.DrawToBitmap(bmp, new Rectangle(0, 0, width, height));
bmp.Save(dialog.FileName);
}
}

private void dataGridView1_Click(object sender, EventArgs e)


{

private void dataGridView1_CellContentClick(object sender,


DataGridViewCellEventArgs e)
{

if (MessageBox.Show("Do you want to Delet or Update Data?", "Confirmation",


MessageBoxButtons.YesNoCancel) == DialogResult.Yes)
{
txt_vname.Text = dataGridView1.Rows[e.RowIndex].Cells[2].Value.ToString();
txt_phone.Text = dataGridView1.Rows[e.RowIndex].Cells[1].Value.ToString();
txt_vcname.Text=dataGridView1.Rows[e.RowIndex].Cells[3].Value.ToString();
txt_model.Text = dataGridView1.Rows[e.RowIndex].Cells[4].Value.ToString();
txt_model.Text = dataGridView1.Rows[e.RowIndex].Cells[3].Value.ToString();

18
5.4 Data Access Layer
A data access layer in computer software, is a layer of a computer program which provides
simplified access to data stored in persistent storage of some kind, such as an entity-relational
database. This acronym is prevalently used in Microsoft environments. The code of data
access layer are given below.

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;

namespace Car
{
public partial class login : Form
{
Model.carEntities1 db = new Model.carEntities1();
public login()
{
InitializeComponent();
}

private void button1_Click(object sender, EventArgs e)


{
var data = db.admins.Where(o => o.password == txt_password.Text && o.username
== txt_username.Text).Count();
if(data>0)
{

Main m = new Main()


;

19
m.Show();
this.Hide(); }
else
{
MessageBox.Show("In valid Cridenciles"
);
}

private void login_Load(object sender, EventArgs e)


{

}
}
}

5.5 Main form data


using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;

namespace Car
{
public partial class Main : Form
{
public Main()
{
InitializeComponent();

20
}

private void floorSetupToolStripMenuItem_Click(object sender, EventArgs e)


{
FloorFome floorFome = new FloorFome();
floorFome.Show();
}

private void carParkingToolStripMenuItem1_Click(object sender, EventArgs e)


{
Parking
parking = new Parking();
parking.Show();

private void floorRowSetupToolStripMenuItem_Click(object sender, EventArgs e)


{
FloorRowsForms f = new FloorRowsForms()
;
f.Show();

private void slotSetupToolStripMenuItem_Click(object sender, EventArgs e)


{
FloorRowsSlots l = new FloorRowsSlots();
l.Show();
}

private void carInformationToolStripMenuItem1_Click(object sender, EventArgs e)


{
Form1 k = new Form1();
k.Show();

21
Chapter 6

6 SYSTEM TESTING AND EVALUATION


6.1 Testing and Debugging
Testing is the process of testing and evaluation a system’s item to detect differences
between given input and it’s expected output. It is used to assess the functionalities of the
system item. Testing allow us to ensure the quality of the product. Software testing
should be done during the development process after implementation of the system. In
simple words software testing is used for both verification and validation of system.
6.1.1 Verification
Verification is a process in which we ensure that our product satisfies the conditions imposed
at start of the development process. In other words, to ensure that are we developing the right
product.

6.1.2 Validation
Validation is to ensure that product satisfies customer specified requirements at the last of the
development process. In simple words, are we developing the product is right.

6.2 Basics of Software Testing


In testing method, the first factor is needs of system we tend to area unit developing. The
capability of the software system will be calculated by executing the source code and
inspecting the code totally different conditions like testing the software system by
subjecting it to different sources as input and examining the results with relevance the
inputs. There are two types of software testing: - black box testing and white box testing.
6.2.1 Black box testing
It is a testing technique which ignores the internal interaction or mechanism of the system
and we are focusing on the output result generated against different input and executed
on that system. It is also called functional testing.
6.2.2 White box testing
It is a testing technique that concerns with the internal mechanism of a system. It is also
called structural testing and glass box testing. Black box testing is also used for validation
and white box testing is used for verification.

22
6.3 Functional and Non-Functional Testing
6.3.1 Functional testing
Defines the desired function of a selected code within the program. This kind of testing
provides us a brief description concerning the program’s performance and security within
the numerous functional areas.
6.3.2 Non-functional testing
Defines the capabilities of system like its log knowledge etc. it's opposite to functional
testing so won't describe the specifications like security and performance. The performance
of the specific program not depends on errors in coding only. The errors within the code is
noticed throughout execution, however other different errors will have an effect on the
program performance like once the program is developed supported one platform which will
not perform well and give errors executed on different platform. So, compatibility is another
problem that reduces the system performance.

6.4 Aim of Testing


The main purpose of testing is to investigate the performance and to evaluate and monitor
the errors that occur once the program executed with completely different input sources
and running indifferent operative environments. The different types of testing technique
are;
• Unit testing
• Validation testing
Integration testing
• User acceptance testing
• Output testing
• Black box and white box testing.
6.4.1 Unit Testing
This is the technique of taking a small part of testable component and execute it by
keeping in mind our requirements and testing the component behavior. Unit testing is for
identifying the defects that occur throughout execution. When an algorithm is executed,
the integrity must have to maintain by the data structures. This testing is use for testing
the functionality of every algorithm during execution. Unit testing reduces the anomaly
within the units. In proposed system, we have developed application by using different
processes, such as encryption, decryption, embed, de-embed, send file or receiver file

23
etc., and all module are test at least five time to ensure that error handling, control
structure are as it is as we want.

6.4.1.1 Limitations of Unit Testing


Unit testing is limited to test, it only the functionality of the units. It is not able to identify
integration errors and performance issues and system problems. It can show the errors
occur in the units during testing execution. It doesn’t not display the errors which are not
present in current module.

6.4.1.2 Validation Testing


Validation is about finding that our product is develop correct or not. The product that
should be designed in such a way that should fulfil the requirements and according to
user expectations. Validation is carried out developing or at the final stage of
development process to determine whether it is satisfies the specified requirements of
user.

6.4.1.3 Output Testing


After completion of validation testing the next process is output testing. Output testing is
the process of testing the output generated by the application for the specified inputs.
This process checks weather the application is producing the required output as per the
user’s specification or not. The “output testing” can be done by considering mainly by
updating the test plans, the behavior of application with different type of inputs and with
produced outputs, making the best use of the operating capacity and considering the
recommendations for fixing the issues.

6.4.1.4 Integration Testing


This is an extension to unit testing, after unit testing the units are integrated with the
logical program. The integration testing is the process of examining the working behavior
of the particular unit after embedding with program. This procedure identifies the
problems that occur during the combination of units. The integration testing can be
normally done in three approaches;

• Top-down approach
• Bottom-up approach
• Umbrella approach

24
6.4.1.5 Top-down approach
In the top-down approach the highest-level module should be considered first and
integrated. This approach makes the high-level logic and data flow to test first and reduce
the necessity of drivers. One disadvantage with top-down approach is its poor support
and functionality is limited.
6.4.1.6 Bottom-up approach
Bottom-up approach is opposite to top-down approach. In this approach, the lowest level
units are considered and integrated first. Those units are known as utility units. The
utility units are tested first so that the usage of stubs is reduced. The disadvantage in this
method is that it needs the respective drivers which make the test complicated, the
support is poor and the functionality is limited.
6.4.1.7 Umbrella approach
The third approach is umbrella approach, which makes use of both the top –bottom and
bottom top approaches. This method tests the integration of units along with its functional
data and control paths. After using the top -bottom and bottom-top approaches, the
outputs are integrated in top bottom manner.

The advantage of this approach is that it provides good support for the release of
limited functionality as well as minimizing the needs of drivers and hubs. The main
disadvantage is that it is less systematic than the other two approaches.

6.4.1.8 User Acceptance Testing


This is the process of obtaining the c confirmation from the user that the system meets
the set of specified requirements. It is the final stage of project; the user performs various
tests during the design of the applications and makes further modifications according to
the requirements to achieve the final result. The user acceptance testing gives the
confidence to the clients about the performance of system.

25
Chapter 7
7 FUTURE EXTENSION
7.1 Introduction
To complete this project properly, it’s necessary to discuss the achievements realized in
relation to the objectives of the project so as to answer the research questions as well as
limitations encountered during the project’s timeline. This chapter compasses the
interpretation of the finding resulting from this study as well as the discussion on the
development of the system.

7.2 Discussion
It’s an easy for Admin to retrieve the data if the vehicle has been visited through number he
can get that data. The vehicle parking area has many lanes/slots for car parking. So to park a
vehicle one has to look for all the lanes. Moreover, this involves a lot of manual labour 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.
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.
Vehicle is now a basic need. There are many administration offices and other departments
etc. There is also a canteen place where student used to go for refreshment. 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. Parking is a growing need of the time. 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.

26
REFERENCES

1. [Sommerville-2009] Somerville I. (2009). Software Engineering. United States of

America. Boston Massachusetts. Pearson Education.

2. [Balaha M, Rumbaugh J-2005] Balaha M, Rumbaugh J. (2005).Object Oriented

Modeling and Design with UML 2.0:UML2. State of India.Noida.Dorling Kindersley

(India) Pvt. Ltd.

3. [1] http://en.wikipedia.org/wiki/systems architectures

[Access Date: 17-8-2019& Time, 13:15]

4. [2] https://www.youtube.com/watch?v=hN9xemJYwos

[Access Date: : 17-8-2019 & Time, 1:15]

5. [3] http://www.omg.org/spec/UML/2.0/

[Access Date: : 17-8-2019 & Time, 3:15]

6. [4] https://www.youtube.com/watch?v=kEcenFwdads

[Access Date: : 17-8-2019 & Time, 3:15]

27

You might also like