Professional Documents
Culture Documents
Final Project Report: Vehicle Number Plate Recognition
Final Project Report: Vehicle Number Plate Recognition
Project Supervisor
Noor Rahman Mahsud
Submitted By
In our opinion, it is satisfactory and up to the mark and therefore fulfills the
requirements of BS in Computer Sciences.
___________________
(Signature)
___________________
(Signature)
Accepted By:
_____________
(For office use)
EXORDIUM
In the name of Allah, the Compassionate, the
Merciful.
CHAPTER NO. 1
GATHERING & ANALYZING INFO...................................................10
1.1 INTRODUCTION
1.2 PURPOSE
1.3 SCOPE
2.1 INTRODUCTION
2.2 PURPOSE
2.3 SCOPE
CHAPTER NO.3
DEVELOPMENT.............................................................................13
3.1 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM)
CHAPTER 1
Gathering & Analyzing Info
1.1 INTRODUCTION
1.2 PURPOSE
1.3 SCOPE
System
Input Image of Number Plate must be given to System
System should have a template of alphanumeric values.
The template should be consisting of all alphanumeric (A to Z, a to z
and 0 to 9) images.
System should detect vehicle number plate.
System should be able to read number plate characters from the detected
number plate
Read number plate character must be stored in database
System should be able to match detected number plate characters with
corresponding template characters
System should be able to display the final detected number plate
characters from the input image in a notepad file
System should keep record for all cars with corresponding time and date
System will track record of each car from database.
Security:
Performance Requirements:
Accessibility Requirements:
It will be ensured that system is accessible all the time to its users.
This application will be available 24/7 and multiple users can access
this application at the same time.
User friendly:
Flexibility:
Maintainability:
Compatibility:
Exception handling:
Data Security:
The damage of the hard drive is one of threat factors for data
security. A hard drive physical damage means loss of data. Loss
of equipment operation, storage media failure, in order to ensure
data security, redundant arrays of inexpensive disks (RAID),
1.6 USE CASES AND USAGE SCENARIOS
template of alphanum
values
<<include>>
<<extend>>
read number
plate characters
System Database
store in database
<<extend>>
match detected no
plate characters
In this use case diagram the system should read image of number plate as input from
webcam for further processing.
Pre-Conditions:
Run the program
Post Conditions:
- Integrated Camera will execute to take picture
Authority:
User – System
Modification history: 1.0
In this use case diagram System should be able to detect the number plate of vehicle
from the given input image.
Pre-Conditions:
1. Run the program
2. Give image of vehicle as input
Task Sequence Exceptions
1. System take image as input
2. Detect the number plate from the given image
Post Conditions:
1. Number plated detected successfully and ready for further processing.
Authority:
User – System
Modification history: 1.0
Use Case Title System should read number plate character
Use Case Id VNPR-004
Description:
In this use case System should be able to read vehicle number plate character from
detected number plate image.
Pre-Conditions:
Run the program
Detect the number plate
Task Sequence: Exceptions
1. Detect the number plate from the given input image
2. Read the character of detected number plate
3. Store in the database
Post Conditions:
1. Character stored in the database successfully
Authority:
User - System
Modification history: 1.0
Post Conditions:
1. The search result display.
Authority:
System
Modification history: 1.0
Requirements
Specification s
Op eration a nd
Maintena n ce
Acceptance
1.7.2 Reasons for Chosen Methodology
The reason for selecting this model is its hybrid nature. It is the
combination of waterfall and spiral model. As a VU study project our
activities will be sequential in nature waterfall model, and we analyze each
phase with regard to the end product. So, it will become an un- sequential
iteration. The VU Process Model is a documentation-driven model. It
therefore generates complete and comprehensive documentation and hence
makes the maintenance task much easier because the feedback of user must
fulfill on each phase of development. VU Process model diagram is
pictorially described below.
1.6.1
Usability: An interface should be easy to learn how to use and
easy to remember how to use. Users/Visitors should
not be required to consult a manual each time they
need to use the website.
Usability Requirements for an interface design
should support "Efficiency of use", "Intuitiveness"
and "Low perceived workload" from the perspective
of its primary users.
1.6.2
Reliability: The system is to be designed as a robust and
dependable operational system which is tolerant
to operator errors and which will recover cleanly
from power cuts or other disasters.
The system must function reliably, with few or
no interruptions in its operation and fewer still
thereafter.
The system must give stable and reproducible
results.
1.6.3
Supportability The system must be maintainable and
extensible.
The system must provide solutions/rules
regarding data encoding problems such as
supporting different character sets, name
truncation rules, name matching in case of
misspelling, etc.
1.6.4
System Operating System: Windows 10 64bit
Requirements: Browsers: Chrome
MySQL Database
Software: XAMPP Server version v3.2.4 and
Sublime
CHAPTER 2
Designing the Project
2.1 INTRODUCTION
2.2 PURPOSE
2.3 SCOPE
User
M anagem ent
Security
Business Layer
Data Layer
Database
2.6 DYNAMIC MODEL: SEQUENCE DIAGRAMS
EXTRACT VEHICLE INFO
Start streaming()
Activated
Extract_info()
Alternative
Info extracted
If web cam working
Save_into_db()
Else
error
Fetch img
detecnum_plate()
detect num_Plate
detected
detected
Save()
Saved()
Saved Successfully
Fetch img
detecnum_plate()
detect num_Plate
detected
detected
Save()
Saved()
Saved Successfully
Return
Character Matched
saved successfully
Saved in db
2.7 Object Model/Logical Model: Class Diagram
Manage Capture Image
system
Camra Vehicle
-System-ID
-Username -Camera_id -vechicle_id
-Password -Resolution -Vechile_brand
+Open_webcam() -Camera_size -Vechicle Number
+Read_inputimg() +Capture_image() -Vechicle Color
+detect_numberplate() +Save_into_db() -Vechile_model
+detect_numberPlate_char() +View_items()
+save_readcharacter() Take image as input +View_Category()
+get_template() +Make_Transaction()
+matchCharacter() +Search()
detect number plate
+DisplayFinal_Result()
has has
display
Match character
Vehicle_model
vehicle_color
PK template_id PK NumberPlate_id
Image
template_name Vehicle_no
PK Image_id
Alphanumeric_values Vehicle_color
image_resolution
Final Result
City_code
numberPlate_Character
PK Result_id
City_code
Result_name
Result_details
2.9 GRAPHICAL USER INTERFACES
CHAPTER 3
Development
3.1 DEVELOPMENT PLAN (ARCHITECTURE DIAGRAM)
User
Presentation Layer
Com m unication
M anagem ent
Security
Business Layer
Data Layer
Database
REFERENCES
Handouts of CS403 Database Management Systems
Handouts of CS504 Software Engineering - I
Handouts of CS604 Operating Systems
Handouts of CS408 Human Computer Interaction
Handouts of CS506 Web Design and Development
Handouts of CS510 Software Requirements and Specifications
Handouts of CS605 Software Engineering -II
Handouts of CS603 Software Architecture and Design
Handouts of CS608 Software Verification and Validation
Handouts of CS615 Software Project Management
APPENDIX
Use case diagrams are visual
representations of written use case
Use Case Diagrams:
scenarios.