ABSTRACT
Barcode License Plate Recognition (BLPR) is a system capable of recognising number plates by scanning their barcodes for various different uses. A sophisticated barcode reader and algorithm converts the barcodes, into identifiable data. This allows the capture of critical information such as the registration of every vehicle entering a site or crossing the red light at traffics. This information can be passed to the police to assist in the pursuit and identification of contraventions.
Visual proof of traffic contraventions with the corresponding time and date information can be provided as evidence and to avoid disputes. Using information supplied by the Driver Vehicle Licensing Authority (DVLA), because of our approved operator status, it is possible to identify the registered keeper of a vehicle and process the contravention automatically.
The BLPR is to help eradicate road accidents on our roads which has become a headache to the government since all efforts are proving futile.
It is been developed with Visual Basic.Net and Structured Query Language(SQL) Server using the Waterfall model.
All data gathered by the BLPR system is stored in a database for future analysis and reporting.
This project will provide an efficient way of combating crime and making the work of the MTTU easier.
ACKNOWLEDGEMENT

Our greatest and foremost thanks goes to God the Almighty Father. To Him be the glory for the great things he has done. It is just by His grace and guidance that has made this work a success and fruitful.

We would like to express our gratitude to the management of the Driver Vehicle
Licensing Authority (DVLA) and the Motor Traffic and Transport Unit (MTTU) for providing us with the information that made this project a success.

Our greatest appreciation goes to Mr. Yeboah Paul of the Faculty of Information and Communication Sciences and Technology, CUCG, for his encouragement, guidance, contribution and for editing this project. We are also grateful to Miss Asante Audrey for her contributions to this project. It would be a mistake if no mention is made of the entire members of the staff of the Faculty of Information and Communication Sciences and Technology.

1.2 Objectives of the Study
A workable ANPR is integral to the monitoring of the safety of road users i.e. drivers, motorcyclists and pedestrians.

1.3 Significance of the Study
ANPR is an internationally recognized tool that can significantly reduce the volume of crime, heighten patrol focus, increase detection rates, tackle cross border crime and provide vital intelligence for use in counter terrorist and serious crime work. It is a technology that captures registration images displayed on all types of vehicle and transfers them to a database for intelligence and analytical purpose.
The ANPR puts information of crime immediately on the finger tips of the MTTU officers and the police, thereby giving them knowledge and power when combating crime. This allows the speed with which the police respond to crimes to be much faster and more precise because they have all the information about the perpetrators of the crime and their address.
This project is to help the police avoid the errors that occur in allowing humans manually record the number plates of road user rules offenders and also ensure that the right people are charged with the right offences committed by them.
This project is also to help other students who have interest in delving deeper into this area or project to have a fair idea of what the BLPR which is part of the ANPR is all about.
1.4 Methodology
The Waterfall Model was used in the development of this system. It provided a sequential design process in which progress in the software development cycle was seen as flowing steadily downwards along the requirement capture and analysis phase to the implementation and testing phases.
The choice of this model was based on the fact that it offers a much cheaper and economical way of dealing with and fixing bugs noticed in an early stage than at a later stage. This eliminates the scrapping off of work done over several months due to broken design which would be discovered in the implementation phase. In addition, the documentations that are done in each stage of development proves to be informational to new developers when some developers leave before the completion of the work. Due to object oriented support in VB.NET, various concepts (like reusability, polymorphism, isolation etc.) are already there but for the efficient management of system components, Component based Software Engineering will also be exercised which will help in a resultant library of components, the benefit of which will be reusability and fast development. . Testing will begin from the lower levels of the system and will move towards higher level components, which will be based on design phase rather than coding phase.

1.5 Organisation of the Project
The first chapter of the project is the introduction which comprises the background of the study, problem statement, objectives of the study, significance of the study, methodology and the organization of the project, the subsequent chapter delves into the literature review, the theoretical framework of the whole project and the empirical evidence that accounts for works, thus existing systems. Chapter three talks about the system, the procedures used to gather the data for the study or project. While chapter four centers on the design specification and Implementation of the system, recommendation and conclusion sums up the project in chapter five.

CHAPTER TWO
LITERATURE REVIEW
2.0 Introduction
Automatic Number Plate Recognition is a mass surveillance method that uses optical character recognition on images to read vehicle registration plates. They are used by various police forces and as a method of electronic toll collection on pay-per-use roads and cataloging the movements of traffic or individuals. ANPR and Facial Recognition Systems have proven to be an effective way to combat crime and control reckless driving on roads in developed countries.[7]
2.1 Theoretical framework
2.1.1 History of Automatic Number Plate Recognition (ANPR)
Automatic Number Plate Recognition was invented in 1976 at the Police Scientific Development Branch in the UK. Prototype systems were working by 1979, and contracts were let to produce industrial systems, first at EMI Electronics, and then at Computer Recognition Systems (CRS) in Wokingham, UK. Early trial systems were deployed on the A1 road and at the Dartford Tunnel. The first arrest through detection of a stolen car was made in 1981.
Concerns about these systems have centered on privacy fears of government tracking citizens' movements, misidentification, high error rates, and increased government spending. On 11th March 2008, the Federal Constitutional Court of Germany ruled that some areas of the laws permitting the use of automated number plate recognition systems in Germany violated the right to privacy. More specifically, the court found that the retention of any sort of information (i.e. Number Plate data) which wasn't for any pre-destined use (e.g. for use tracking suspected terrorists or for enforcement of speeding laws) was in violation of German law. These systems were provided by Jenoptik Robot GmbH, and called TraffiCapture.
In Australia, several State Police Forces, and the Department of Justice (Victoria) utilise both fixed and mobile ANPR systems. The New South Wales Police Force Highway Patrol was the first to trial and use a fixed ANPR camera system in Australia in 2005. In 2009 they began a roll-out of a mobile ANPR system (known officially as MANPR) with three infrared cameras fitted to its Highway Patrol fleet. The system identifies unregistered and stolen vehicles as well as disqualified or suspended drivers as well as other 'persons of interest' such as persons having outstanding warrants.
Also, The UK has an extensive (ANPR) automatic number plate recognition camera network. Effectively, the police and security services track all car movements around the country and are able to track any car in close to real time. Vehicle movements are stored for two years in the National ANPR Data Center to be analyzed for intelligence and to be used as evidence.
In 1997 a system of one hundred ANPR cameras, codenamed GLUTTON was installed to feed into the automated British Military Intelligence Systems in Northern Ireland. Further cameras were also installed on the British mainland, including unspecified ports on the east and west coasts. [8]
2.1.2 Advantages of ANPR
The ability to automatically identify vehicles by their recognition numbers can be beneficial for several reasons since the ANPR aims to a. Reduce crime and terrorism. b. Reduce road traffic casualties. c. Increases the number of offences brought justice. d. Increase public perceptions of safety and confidence in the police. e. Make more efficient the resources of the police.
2.1.2 Disadvantages of ANPR
There are a number of possible difficulties that the software must be able to cope with. These include: a. Poor image resolution, usually because the plate is too far away but sometimes resulting from the use of a low-quality camera. b. Blurry images, particularly motion blur. c. Poor lighting and low contrast due to overexposure, reflection or shadows. d. An object obscuring (part of) the plate, quite often a tow bar, or dirt on the plate. e. A different font, popular for vanity plates (some countries do not allow such plates, eliminating the problem). f. Circumvention techniques. g. Lack of coordination between countries or states. Two cars from different h. countries or states can have the same number but different design of the plate.
2.1.3 History of Barcodes
Also, Barcode It has evolved from a punch card system, designed to speed the purchasing process, to the modern barcodes we see on every product imaginable. The original punch cards proved to be too expensive and the idea was abandoned by its inventor. More than a decade later the barcode as we know it took shape in its simplest form. The original or prototype system used ultraviolet ink but it had a propensity for fading and therefore not feasible; it was also fairly expensive and not economically viable.
The basic idea for the barcode came from Morse code but the dots where extended into lines that alternated black and white in a parallel fashion, and this is still the case today. The original method of scanning the barcode to identify the product was accomplished through high wattage light bulbs, 500 watts to start with, and was used in conjunction with a film industry photomultiplier. This increased the intensity of the light and made the scanning easier for the time being. As more and more companies needed to cut costs and wanted a system for inventory, more technology needed to be invented to make the system feasible.
As the barcode history progressed, more ideas and innovations were developed and implemented. The parallel lines we recognize as barcodes were not the only form of identification used in the development of barcodes. These are categorized as 2D barcodes or a matrix code. These complex codes were represented in patterns of dots, circles, and a variety and blending of geometric shapes. The complexity of the shapes allows this system to contain more data in a code, but wasn't used nearly as much as linear barcodes or 1D barcodes. These kinds of barcodes can be found in cellular phone applications such as encoding URLs and images, as well as purchased ticket information for movies and sporting events on a cellular phone.
It wasn't until the 1960s that barcodes were scanned with a laser, a helium neon laser to be exact. At first only a single laser was used to scan the barcode but soon the addition of other lasers at separate angles were added to make the process more efficient and easier to use. The laser interprets the width of the black lines; each number has its own specific width. The white spaces tell the laser were one number ends and the next begins. Any string of numbers in any order or length can be scanned against a database of information to account for inventory, sales and purchases. Today we use a standardized 11 digit code that identifies any unique product. This code is referred to as the UPC, or Universal Product Code.
This was put into practice in 1973 as a test by the Kroger Corporation and it used a system of "bull's eye" patterns instead of the parallel line patterns we are used to. The system proved unusable as the printed codes were often smeared and could not be read.
One year later the IBM system of barcode lines was adopted and the modern barcode history was born. These barcodes are now used for absolutely everything we purchase from virtually any industry from new cars to new computers - and from baseball tickets to surfing the web with our cellular phones and PDAs. There are few parts of our lives that are not touched by a barcode; they have become an integral part of our everyday lives.[17]

2.1.4 Advantages of Barcodes
Barcode systems provide an array of benefits, including operational efficiency, better customer service, and improved visibility of key business information to management. They also speed up work since the work that would have been by typing can be done within a second by just scanning the barcode.
They also help to avoid errors that arise from typing and provide high level of reliability.
2.1.5 Disadvantages of Barcodes
Despite all the advantages associated with barcodes, they have drawbacks i. System Failure may cost more delays. ii. Scratched or crumpled barcodes may cause problems. iii. Data must be coded in the barcode which will take time. iv. In laser scanning, durability and cost are the two disadvantages . 2.2 Empirical Evidence and Related Works
Many Software companies have developed ANPRs with different capabilities. Some of these companies and their ANPR software include
AASSET Visualisation and Management Software, GeoVision Car License Plate Recognition, HoneyWell Fusion ANPR, Geutebruck Car License Software, Artec Multieye-ANPR. It is hypothesized that ANPRs help to reduce the number of crimes and road accidents and the following five literature reviews attempt to demonstrate and support this hypothesis.
The AASSET Visualization and Management Software was developed by the AASSET Securities with the aim of reducing road accidents and car theft mainly in South Africa. The Software has the following features. It allows visualizing in real time and recording vehicle flow, searching by time slot, name or plate number, administration of vehicle and visitors access rights, Vehicle count (total and by section), Administration of authorized parking period. Visualizing in real time and recording vehicle flow helps to know the movement of all vehicles on the road since the cameras connected to this software are virtually everywhere. This therefore helps to trace vehicles especially vehicles being pursued by the police for committing crimes. Also, giving visitors and vehicle access rights helps to trace unregistered vehicles and vehicles on the roads without proper authorization. The capabilities of this software support the hypothesis that the ANPR helps to reduce crime and road accidents. One limitation to this software is that it runs only on Windows 2000 Professional or Windows XP Professional.[9]
Next is the GeoVision LPR system which is capable of identifying vehicles by their license plates. It uses access-control systems and CCTV (Closed Circuit Television) cameras to capture images of the plate. The CPR software when used for car parking management reads the license plate of vehicles, signals to the parking gate and keeps a time record on the entry or exit of the parking lot for automatic payment calculations. It has the following features. It is able to detect unauthorized plates and then send immediate alarm to guard or the police force to take immediate actions, records images in JPEG(Joint Photographic Experts Group) format, applies Digital Watermark Technology for legitimate record and support recycle and backup features. The features of this software also support our hypothesis. The only limitation to this software is that it only works with cameras. [10]
Also The Geutebruck Software License is an ANPR software that can capture multiple images and save them as channels. The picture data of the selected channel are analyzed for number plate information according to parameter settings and country code. If a number plate is recognized, the corresponding metadata are assigned to the image in the picture database for later analysis. Every available channel under GeViScope and reporter (analog or IP) can be used for the number plate analysis. The number plate data are stored in the system, categorized and saved in a black/white list. Configurable system actions can then be triggered depending on the category and black/ white list assignment of a recognized number plate. It can monitor roads 24hrs and with its country code, it is able to detect unregistered cars brought into a country from another country. This feature introduced aids in international car theft. This features that are incorporated into this software supports the hypothesis that the ANPR helps in combating crime especially on our roads. [11]

The Intertraff Plate Recognition Software is an ANPR Software which provides solutions for access control, security, law enforcement, traffic and parking applications using our number plate recognition software. The license plate recognition software applications are all based around Intertraff ANPR Engine, which locates the number plate in an image and extracts the registration number for further processing. It can read Latin characters as well as Arabic number plates. Some of the features of this software include the ability of being able to monitor contemporarily 5 lanes of traffic. It also uses cameras which work perfectly even in de worst conditions and helps in Intrusive and unintrusive vehicle detection technology, barrier controls which gives access to only known cars and plates in particular countries with specified number plates. Therefore any unknown vehicle plate number is not given free pass across barriers. This has helped in solving cases which involves car theft and removal of license plates. The features of this ANPR software describe and support the hypothesis that these software help in solving crimes related to vehicles. The limitation to this software is that it only runs on systems running a windows XP operating System. [12]

Lastly the ARTEC Multieye-ANPR Gate Software is an ANPR system which is used for the access control of vehicles. Access and exit controls are situated in front of barriers, car parks or the registration of supplier vehicles on company grounds. This software is used on company grounds to give access to authorized vehicles and also only allows authorized vehicles to exit the company grounds. This software can monitor two lanes. Number plates out of over 40 countries are recognized and registered safely and reliably. The concept behind this whole software is to make sure cars with plates been fed into the system are only allowed to reduce theft on company grounds. The software in one way or the other supports the hypothesis of our work that the ANPR system in a great way aids in combating crime.[13]

Taken together all the features and capabilities of these individual software, it indicates that the ANPR system plays a major role in controlling the use of our roads and aiding law enforcement agencies in their work. ANPR has led to thousands of arrests for offences including possessing offensive weapons, burglary and drug dealing, as well as the seizure of over many thousands of unsafe vehicles. ANPR targets criminals, not innocent law abiding motorists. ANPR does not only reduce crime but it is also used to reduce road deaths and serious injuries. It can be assumed from the above five literature reviews that the ANPR system cannot be put aside if law enforcement agencies have the aim of checking traffic light rule violations, unworthy road vehicles, car thefts, speeding and all sort of road and vehicle crimes.

CHAPTER THREE
METHODOLOGY OF THE PROPOSED SYSTEM
3.1 Introduction
This chapter contains in detail all the processes involved in developing this system. These processes include the ways in which information was gathered and analyzed, Modeling diagrams used, case tools used and other procedures employed.

3.2 The Proposed System
The Barcode License Plate Recognition (BLPR) System is developed to help the security agencies especially the MTTU department of the Police Service to fight crime and control road accidents. This system allows real time information on the owner of a vehicle to be provided to the police as and when a crime is committed by that fellow.
This system is built using VB.NET and SQL Server. A barcode reader is used to extract the information of the vehicle that causes the flouting of the road safety rule by scanning it's barcode.

3.3 Development Approach
A Software Development Life Cycle (SDLC) is essentially a series of steps, or phases, that provide a model for the development and lifecycle management of an application or piece of software. The methodology within the SDLC process can vary across industries and organisations. [16]

The Waterfall Model was used in the development of this program. This Methodology provides a sequential design process in which progress in the software development cycle is seen as flowing steadily downwards along the requirement capture and analysis phase to the implementation and testing phases.

Fig.11 Model Used
A. Requirement Analysis This is the phase where all the information needed for the development of the system were gathered. Most of the requirements were gathered through participatory observation of how the MTTU does their work especially how they control traffic. Interviews were also conducted to get information from the management of both the DVLA and the MTTU. The interview was done using the informal, conversational format which made the interview very broad and very informational. Through the interview, the types of crimes that were committed most by drivers and motorists, the amount of fine the police would want to charge in the case where some specific crimes are committed were all known. Also all the information required by the DVLA in order to register cars was also known.
The requirements captured were divided into two major parts: Functional and Non-functional requirements. The functional requirements show the functions and behaviour of the system whilst the non-functional requirements show requirement that are not concerned with specific functions of the system.
i. Functional Requirement
The specific functions of the system shows the services and tasks performed by the system. These include 1. Number plate capture 2. Barcode image to text conversion 3. Request information from the database 4. Update existing information in the database 5. Keep records of all persons and their activities.

ii. Non –Functional Requirements
Non-Functional Requirements show properties such as reliability, data storage capacity, space and performance as well as delivery requirements.

Non-functional requirements

External requirements
Product requirements
Organizational requirements

Interoperability requirement
Ethical requirements
Portability requirements
Reliability requirements
Efficiency requirements

Legislative requirements
Standard requirements
Implementation requirements
Delivery requirements

Usability requirementss

Safety requirements
Space requirements
Performance measure

Privacy requirements

Fig. 1 Non-functional requirement types

Table 3.1 Non-functional requirements of ANPR NON-FUNCTIONAL REQUIREMENTS | Product requirements | ANRP is;a. efficient and reliableb. maintainablec. robust since its able to recover user information | | Organizational requirements | ANRP will be used by the police to check law flaunters. only the administrator would have the access into creating an account for a new customer. | | External requirements | a. customers should be able to make payments themselves when billed.b. customers should be able to ask for proof of the offence they are being accused of. |

B. System Design
After gathering all the information needed from both the MTTU and DVLA, The system to be developed was designed on paper and this included the number of forms that were going to be needed to suit the requirements that had been gotten that is the overall structure of the system. How to set privileges, send bills when specific crimes are committed and also retrieve the information of cars and make available to other stations when drivers commit crimes.
Database Design

A good application always has a well-structured, normalized and secured database. The database for the BLPR was designed such that accessing data from the database would not be much of a problem. Redundancy in a database was a problem that was addressed in the creating of this database. This ensured that the database was free of information duplication.
The automatic number plate recognition system’s database was built to capture all the necessary data required about users and their activities. Below are models showing the components of the database

Fig.2 Database Design

Normalization
Normalization is a technique that can be used in reducing redundancies in tables in databases. There are many forms of normalization and we decided to use two of the many forms, the first and the second (1st, 2nd) normal forms.
First normal form (1NF): the first normal form is satisfied if all duplicative columns in the same table are eliminated and new tables created for each group of related data each row with a unique column or set of columns are identified. All tables in the system have been normalized in this form.
Second normal form (2NF): in the second normal form, all requirements for the 1NF are met and subsets of data that apply to multiple rows of the table are removed and placed in separate tables. Also relationships between these new tables and their predecessors are created through the use of foreign keys.

Entity Relationship Diagram
The entity relationship diagram shows all the entities in the database and their attributes. It also shows connections between some of these entities and the relationship between them.

Fig.3 Entity Relationship Diagram

The entity relationship diagram shown above shows how we connected all the entities in the database. In all, as it can be seen, we have 6 entities in the database.

The Car entity is used to store information of all registered cars and also store identity(ID's) of cars that have been registered and have either been stolen or have been used to commit a crime. The License plate number of the Car is used as the primary key in this table that is carID. The Car entity is linked with the Crime entity based on the CrimeID which is a primary key in the Crime entity and is a foreign key in the Car entity.
It is also linked with the Stolen Cars entity based on the stolenID which is a primary key in the Stolen Cars entity and is a foreign key in the Car entity.

Since registration of cars is based on information about the car and also the owner of the car, the Registration entity which is used to save information about the owner of the car is linked with the Car entity based on the License Plate Number of the car which is a primary Key in the cars table (carID) and is a foreign key in the Registration table.

The Stolen Cars entity is used to save all the information about cars that have been stolen and reported. An ID is automatically generated for a car that is been reported as stolen and this ID is used as a primary key in this table and sent to the Cars table or entity to be a foreign key in there. Therefore every registered Car that is been reported stolen automatically has a stolenID linked to it. This makes it easier to search for all registered cars that have been stolen. Also the same ID is sent to the Found table to be a foreign key if fortunately the Car is found after being reported stolen.

The Found Entity or table is used to store information of all cars that have been stolen and then later been found. All cars that were previously in the stolen cars table are moved to this table when they are found in a later date. An auto incremented count is used as a primary key in this table and this primary key just increases itself according to the number of entries made into this table. It is linked with the stolen cars entity or table based on the stolenID created for cars when they are reported stolen in the stolen cars table.

The crime table or entity is used to save all the information about cars that have been used to commit crimes and been captured by the camera or reported manually. A distinct ID is generated for each crime reported both manually or automatically and this ID is used as primary key in this table and is sent to both the Cars and Solved table as a foreign key.

The Solved entity or table is used to hold information about all crimes that have been reported and have been solved. An auto incremented count is used as the primary key. This primary key increases as per the number of entries made into this table. The crime that has been solved's ID is used to link the Solved entity to the crime entity.

The Security Entity or table is used to save all the information about the users who will be granted access to the software. The username they choose is the primary key in this table or entity.

Case Tools Employed
Different tools were used for different parts of this system, from designing the front end to the hard coding. This part shows most of the tools used in the development of this project.
Microsoft Visio 2007: Microsoft Visio is a diagramming tool that can be used to visually communicate technical as well as non-technical representations of ideas, processes, concepts, structures, layouts, software models, blueprints, etc. Microsoft Visio eliminates the laborious process of creating diagrams by providing the tools to create complex diagrams in a user friendly manner [15]. It is used in developing database models including the entity relationship diagram, relational model etc. This software was used in designing the entity relationship diagram of the database used for ANRP.
Visual Basic.NET (VB.NET)
The VB.NET is an object-oriented computer programming language that can be viewed as an evolution of the classic Visual Basic (VB), implemented on the VB.NET Framework.
Visual Basic.NET offers the most productive and easiest language and it acts as a tool for rapidly building web and Windows applications. It offers a powerful integrated development environment, increased application performance and enhanced visual designs.
Data access scenario can be easily tackled with ActiveX Data Object(ADO) and ActiveX Data Object.Net(ADO.NET) data access. The flexibility of ADO.NET enables binding of data to any database as well as arrays, collections and classes and offers true Extensible Markup Language( XML) representation of data. With the help of ADO.NET, VB.NET can gain access to Microsoft access, Oracle, Microsoft Structured Query Language (MS SQL) Server, etc. with high speed.
With the help of VB.NET coding can be done effectively at a faster pace. A multitude of enhancements to the code editor, including background compiler of real-time notification of syntax errors, smart list of code and enhance IntelliSense transforms into a rapid application development coding machine.
Apart from the above-mentioned features and uses, VB.NET offers other advantages like direct access to the platform, full object-oriented construction, XML Web services, mobile applications, COM interoperability, reuse existing investment, upgrade wizard, etc.
Microsoft SQL Server There are at least a dozen different editions of Microsoft SQL Server aimed at different audiences and for different workloads (ranging from small applications that store and retrieve data on the same computer, to millions of users and computers that access huge amounts of data from the Internet at the same time). Its primary query languages are T-SQL and American National Standard Institute (ANSI) SQL.
SQL Server 7.0 and SQL Server 2000 included modifications and extensions to the Sybase code base, adding support for the IA-64 architecture. By SQL Server 2005 the legacy Sybase code had been completely rewritten.
SQL Server is one of the world's most flexible and complex database that offers a variety of administrative tools that makes development of database, maintenance and administration easy. Its primary query language, SQL Server is an application that is used to create computer databases for Microsoft windows family of server operating systems. It would serve as the backend. This was chosen because it has the ability to withstand multiple hits at any point in time without crashing. This capability allows our safety critical system to remain operational during peak hours where there is much traffic and the possibilities of lots of traffic offences may be committed.
C. Deployment After doing our integration test and realising that everything worked perfectly, we then decided to see how the whole system works in a user environment. So we got a barcode scanner and a few barcodes to see if after registering the barcodes as license plate numbers, and then scanning them with the barcode reader, the system will be able to retrieve it's information, update other networked stations and then send a bill into the mail of the offender.

The choice of this model was based on the fact that it offers a much cheaper and economical way of dealing and fixing bugs noticed in an early stage than at a later stage.
Also the choice of the waterfall model was based on the fact that it is easy to use and implement and also easy to manage due to the rigidity of the model that is each phase has specific deliverables and a review process.
It helps to avoid starting work done over several months due to broken design which would be discovered in the implementation phase. In addition, the documentations that are done in each stage of development proves to be informational to new developers when some developers leave before the completion of the work. Due to object oriented support in VB.NET, various concepts (like reusability, polymorphism, isolation etc.) are already there but for the efficient management of system components, Component based Software Engineering was exercised which helped in a resultant library of components, the benefit of which was reusability and fast development. Testing was done from the rudimentary levels of the system and moved towards higher level components, which was based on design phase rather than coding phase Words.

4.3 System Testing and Implementation
a. Implementation
After having all the design structure on paper, the system was developed in bits that is the coding of the system was started. Development of the log in page which holds the key to the security of the software was done first. This is where all privileges set as to which type of users have access to which parts of the system. The homepage which was going to be the main navigational part of the system was then developed. Giving users access to perform specific kind of tasks. The individual tasks the system was going to perform were developed afterwards until the last stage where the user logs out and ends his or her session was done with. All these individual parts of the system were developed after each part or unit was developed, tested and seen as been complete.

b. Integration and Testing
Every system upon completion has to be tested to ensure there are no bugs, errors or mistakes in the program that is why BLPR was very well tested. This system was tested using the divide and conquer method of testing. This method of testing requires that the system be divided into modules or units and tested accordingly before bringing together every module to form the entire system.

After developing the individual components of the system, they were brought together to see how they will function and then get to know the errors that were going to arise after they were been integrated. Each unit was tested for syntax, logical and semantic errors and measures were put in place to reduce user errors. Feedback features were also added to the application such that users would not be stuck on a particular error message and not know what to do in handling such messages. Input errors on the part of the user were taken into consideration during the validation of input boxes and other places user input is required. Validations were also checked to make sure that even after integrating them, they still worked.

After testing the system, bugs were found and all of them were dealt with to make sure the system was bug or error free.
4.4 Maintenance
The BLPR system has been designed in such a way that, making changes to its functionalities will be easy. Maintaining it is therefore not much of a problem. The codes written for the functionalities have been commented to enable the understanding of the codes by different programmers; that makes the maintenance of this system very easy. The system is one that checks the daily activities of road users; therefore it would have to be updated as and when something new that has got to do with road users pops up. This would ensure that the BLPR system stays functional meeting the needs of the changing time.

CHAPTER 5
CONCLUSION AND RECOMMENDATIONS
5.1 Introduction
The project on its completion has been evaluated and some recommendations were made. The conclusion and recommendations for this project are shown in this chapter. It is necessary that the outcome of this project compares to the objectives set for the project. The evaluation of the methodologies used in the development of this project is done in this chapter as well.

5.2 Evaluation of Project
The development of this project has been a success since the most important objective of the project, the capability of the MTTU to be able to prevent reckless driving on the road has been met. The system is very efficient since it is able to process information at a very fast rate and also generate reports based on certain specifications by the administrator.

5.3 Architecture
The 3-tier architecture was employed in the development of this project where the presentation layer, application layer and the storage are separate from each other. The user of the network only gets to see the presentation and storage layer enabling a fast connection to the database, and with the use of a computer that has the software installed on it, one with a unique and valid user id can have access to report crimes as well as know the perpetrators of crimes. The storage (database) however, can be on a different computer (server) and managed by the administrator.

5.4 Technology Used
The major tool used in the creation of the BLPR system is visual basic.net. This was a very adequate tool in terms of the interface design and coding. It helped in the design of the project interfaces and also in generating some of the codes that we used.