1

CHAPTER 1

INTRODUCTION

1.1 COMPANY PROFILE

Agriya is a 14 years old custom web development company based out of Chennai,
India employing over 200+ developers across a range of disciplines which include
php, web development, web designing, search engine optimization experts. It has
been recognized throughout the world as a cutting edge web development and mobile
development company.

They specialize in creating extremely user friendly and SEO friendly websites
and web applications in a variety of domains which include crowd sourcing, crowd
funding, clone scripts, marketplace type of sites for B2B and B2C. Their skills and
offshore location mean that they can often provide maximum cost savings to
businesses around the world on custom web development and mobile development
projects.

They are a leading edge web development company who focus on the latest
technologies and platforms to create websites and applications for small, medium,
large enterprises and startup entrepreneurs. They always adopt the trends and
approaches which give businesses maximum return on their investments. They
embraced open source technology like PHP, Java and so on

Each customer is assigned to a dedicated client relationship manager in their

point of contact with the company. These people are technically trained as well as
having excellent communication skills. They will make themselves available to a
schedule that suits your way of working and will ensure your project gets completed
on time and without any problems.
 2

1.2 OBJECTIVE

The objective of this project is to implement the RFID technology in license

verification, fitness certificate Verification, RC, permit type, tax details and all to
provide easy access in the immigration places. Special electronic RFID code is to
verify authorized user details. Automated systems have less manual operations,
flexibility, reliability and accurate. Due to this demand of less manual controlling,
every one prefers automated control systems. Radio Frequency identification is one
such technology which can be used to design automated systems.

The data which are stored is unchangeable and fraudulent activities might be
avoided by giving the electronic card verification to the user. All the manual process
is reduced in proposed system and can be easily avoided by performing customized
consumer travel verification through electronic card.
 3

CHAPTER 2

SYSTEM ANALYSIS

System Analysis is a problem solving technique that decomposes a system in to

its component pieces for the purpose of studying how well those component parts
work and interact to accommodate their purpose. Presumably system analysis is done
in order to subsequently perform a system design. System design is a complementary
problem solving technique that reassembles a system component pieces back in to a
complete system which is an improved system.

2.1 EXISTING SYSTEM

The existing system is not providing secure registration and profile management
properly. In previous system all the data about RTO are recorded manually. So the
system takes long time to verify the license. Vehicle and its owner details are not
maintained properly. It gives very less security for saving data and some data may be
lost due to mismanagement. Time consuming is high in this system for employee and
customer.

Drawbacks:

Data are entered manually.

It can be erased or edited by the consumers.
Manual payment entry
Vehicles waiting in queue
Data integrity is not provided.
No proper authentication of individuals through proper evidence
 4

2.2 PROPOSED SYSTEM

In the proposed system, fraudulent activities might be avoided by giving the

electronic card verification to the user. Here, propose a smart card where each and
every user card holder has an individual have RFID tag. The customer details are
stored along with the smart card details into the database server. All the manual
process is reduced and can be easily avoided by performing customized consumer
travel verification through electronic card.

Smart cards are becoming increasingly more popular for security and personal
identification applications. Smart cards have one or more microcontrollers embedded
in them which manage access to, and storage of, sensitive data that is actually stored
in memory devices on the smart card. The smart chip included on a smart card
provides a means for secured electronic transactions and a means for identification.

The integrated chip is embedded in the smart card and operates to process
specific transactions. The smart card uses a serial interface and receives its power
from an external source such as a smart card reader. Through this RFID CARD
license and the case details with the fine amount paid are easily entered and verified.

Advantages:

Special electronic RFID code to verify authorized user details.

Illegal actions cannot be done.
Very flexible and increasing storage capacity.
Reducing the risk of transaction fraud more durable
 5

CHAPTER 3

SYSTEM SPECIFICATIONS

3.1 HARDWARE REQUIREMENTS

RAM : 1 GB

Hard Disk Drive : 80 GB

Monitor : 17 Color Monitor

Key board, Mouse : Logitech Multi media.

Processor : Pentium dual core

3.2 SOFTWARE REQUIREMENTS

Front End/GUI Tool : Microsoft Visual studio 2008

Operating System : Windows XP

Language : VB.NET

Back end : Sql Server 2005

 6

CHAPTER 4

SOFTWARE DESCRIPTION

4.1 FRONTEND SOFTWARE

Microsoft .Net

Microsoft .net is a set of micro soft software technologies for rapidly building
and integrating xml web services, micro soft windows-based applications, and web
solutions. The .net framework is a language-neutral platform for writing programs
that can easily and securely interoperate. Theres no language barrier with .net: there
are numerous languages available to the developer including managed c++, c#, visual
basic and java script.

The .net framework provides the foundation for components to interact

seamlessly, whether locally or remotely on different platforms. It standardizes
common data types and communications protocols so that components created in
different languages can easily interoperate. .net is also the collective name given to
various software components built upon the .net platform. These will be both products
(visual studio.net and windows.net server, for instance) and services (like passport,
.net my services, and so on).

The .NET Framework

Microsoft designed C# from the ground up to take advantage of its new .NET
Framework. Because C# is a player in this new .NET world, you should have a good
understanding of what the .NET Framework provides and how it increases your
productivity.
The .NET Framework is made up of four parts, as shown in the Common
Language Runtime, a set of class libraries, a set of programming languages, and the
ASP.NET environment. The .NET Framework was designed with three goals in mind.
 7

First, it was intended to make Windows applications much more reliable, while also
providing an application with a greater degree of security. Second, it was intended to
simplify the development of Web applications and services that not only work in the
traditional sense, but on mobile devices as well. Lastly, the framework was designed
to provide a single set of libraries that would work with multiple languages. The
following sections examine each of the .NET Framework components.

Web Development
The .NET Framework was designed with one thing in mind: to fuel Internet
development. This new fuel to add to Internet development is called Web Services.
You can think of Web Services as a Web site that interacts with programs, rather than
people. Instead of delivering Web pages, a Web Service takes a request formatted as
XML, performs a particular function, and then returns a response to the requester as
an XML message.
Note XML or eXtensible Markup Language is a self describing language
much like that of HTML. XML on the other hand has no predefined tags thus
allowing it great flexibility in representing a wide variety of objects.

4.2 BACKEND SOFTWARE

SQL Server 2005 is the successor to SQL Server 2000. It included native
support for managing XML data, in addition to relational data. For this purpose, it
defined an xml data type that could be used either as a data type in database columns
or as literals in queries. XML columns can be associated with XSD schemas. XML
data being stored is verified against the schema. XML is converted to an internal
binary data type before being stored in the database.

Specialized indexing methods were made available for XML data. XML data
is queried using XQuery. Common Language Runtime (CLR) integration was a main
feature with this edition, enabling one to write SQL code as Managed Code by the
CLR. SQL Server 2005 added some extensions to the T-SQL language to allow
embedding XQuery queries in T-SQL. In addition, it also defines a new extension to
XQuery, called XML DML that allows query-based modifications to XML data.
 8

SQL Server 2005 also allows a database server to be exposed over web
services using Tabular Data Stream (TDS) packets encapsulated within SOAP
(protocol) requests. When the data is accessed over web services, results are returned
as XML. For relational data, T-SQL has been augmented with error handling features
(try/catch) and support for recursive queries with CTEs (Common Table
Expressions). SQL Server 2005 has also been enhanced with new indexing
algorithms, syntax and better error recovery systems.

Managing Services
SQL Server
SQL Server Agent
SQL Server Browser
SQL Server Integration Services
SQL Server Analysis Services

SQL Server Management Studio

This tool is a new feature in SQL Server 2005. It replaces Enterprise Manager
and Query Analyzer from earlier versions. It has been developed using a Visual
Studio shell as a base. It follows the paradigm of Visual Studio, in which most tools
are organized as tabbed, dock able or floating windows.

The registered servers pane allows viewing and managing parameters for
connecting to servers. The tool includes both script editors and graphical tools which
work with objects and features of the server. A central feature of SQL Server
Management Studio is the Object Explorer, which allows the user to browse, select,
and act upon any of the objects within the server.
 9

CHAPTER 5

PROJECT DESCRIPTION

5.1 PROBLEM IDENTIFICATION

In the existing system the overall process is carried out manually. The time
consuming is high in this system. The data can be erased or edited by the consumers
and manual payment entry is required. Data integrity is not provided. Maintaining
document is so difficult. It takes more time. Database is not maintained properly and
may have a chance of human errors. So in order to overcome these issues and make
the RTO process so efficiently RTO management system is introduced.

5.2 OVERVIEW OF PROJECT

The RTO Management system is to implement the RFID technique in license

verification, fitness certificate Verification, RC, permit type, tax details to provide
easy access in the immigration places. There is no chance to make duplicate RFID
card and cannot make duplicate license. So the project is used to improve the
performance in the immigration places and also save time.

The RTO Management System project was developed for RTO office to
maintain all the records like two and four wheeler registration, learning and driving
license, changing of address, Tax collection form, permits section, inspection and
many more in systematically. This software application is developed with fully
computerized method to manage all the data .In Existing system, all the records are
maintained manually

In existing, every system is automated in order to face new requirements,

automated systems have less manual operations, flexibility, reliability and accurate.
Due to this demand of less manual controlling, every one prefers automated control
 1
0

systems. Radio Frequency identification is one such technology which can be used to
design automated systems.

Radio-frequency identification (RFID) is the use of a wireless non-contact

system that uses radio-frequency electromagnetic fields to transfer data from a tag
attached to an object, for the purposes of automatic identification and tracking. The
tag contains electronically stored information which can be read. In this project RFID
reader and RFID tags (vehicle RC book, driving license) are used. Whenever the tag
is shown to the RFID reader, it read the data from the RFID tag. This is used validate
the data easily.

The main objective of the project is to design an automated system which can
perform tasks like vehicle RC book and driving license verification and all using
RFID.

5.3 MODULE DESCRIPTION

Authentication

In authentication module, the administrator who is authorizing user to access

the systems enters into the system using their appropriate user name and password
issued to them. Admin enters the card details into the system using client/customer
issued card number in order to do processing of the RFID users. The admin also
responsible to verify the users validation of card details and data enters into the
system using client/customer appropriate card number.

User details

The card issued under an order or authority of the company, as per the Public
Distribution System.

A RFID card is a company-issued that certifies the identity of its holder for the
purpose of travel. The elements of identity contained in all standardized card include
information about the holder, including name, mobile, gender, aathar number and
place. In user profile module, the user specifies their details like the name, age,
location, address, so on.
 1
1

Vehicle Registration details

This module is used to enter the vehicle Registration details like Transport,
Non-Transport, Temporary Registration, Re-Registration, Transfer of Ownership,
Change of address, Clearance Certification, vehicle owner, Registration date and
renewal of Registration and related works

Tax details

This module is used to enter the records of tax. The tax like one-time tax,
lump sum tax (LST), Road tax/Special Road Tax. Non-Transport and Transport are
under one-time tax .Mandatory and Optional are under lump sum tax.

Driving License details

This module is used to enter the details of record like leaner license, driving
license, international driving permit, conductor license and renewal of license. The
data entered can be modified by the admin.

Inspection wing details

This module has a record about fitness certificate, renewal of fitness

certificate, vehicle inspection for new registration and accident inspection detail and
so on.

Case details

In this module admin enters the case details of vehicle owner and also the fine
paid by the corresponding person based on the RFID card number. This can be
modified by admin.

RFID verification

In card verification module, the card is being validated by the RFID reader
whether the appropriate users are valid. From this card holders license details and the
cases filed on him are verified from RFID card.
 1
2

Reports

Various reports are generated from this project .They are.

User Report
Verification Report
Case details

5.4 DATA FLOW DIAGRAM

The Data Flow Diagram (DFD) is a graphical representation of the flow of data
through an information system, modeling its process aspects. A DFD is often used as
a preliminary step to create an overview of the system, which can later be elaborated.
DFD can also be used for the visualization of data processing.

The DFD shows what kind of information will be input to and output from the
system, where the data will come from and go to, and where the data will be stored. It
does not show information about the timing of process or information about whether
processes will operate in sequence or in parallel.

Level 0

RTO Reports
Admin/User Managem
ent system

Figure 5.4.1 Data Flow Diagram Level 0

Level 1

Figure 5.4.2 Data Flow Diagram Level 1

Level 2

Login
Admin

Viewin
Case
g User Details
details
detail
s

RFI
D
Scannin
g

Verific
a
tion

Authorized
card

Figure 5.4.3 Data Flow Diagram Level 2

 5.5 ENTITY RELATIONSHIP DIAGRAM

Address
Cardn
uname nam o
pwd e Mob

Vn
Updat o User details
Admin
es

vna
Case_no
Cardno
date
finamt

RFID Case details

scanning

Secret no Card no

Hnam
e
RFID CARD Verifi
es

Figure 5.5.1 Entity Relationship Diagram

5.6 DATABASE DESIGN

Database design is the process of producing a detailed data model of a

database. This logical data model contains all the needed logical and physical design
choices and physical storage parameters needed to generate a design in a Data
Definition Language, which can then be used to create a database.

Table 5.6.1 User Details

Primary key: Vehicle no

This table describes about the card user details.

S.No. Field Data type Description

1 Cardno Varchar(15) Card number of the user

2 Name Varchar(15) Name of user

3 Address Varchar(50) Address of user
4 Mob Varchar(15) Mobile no of user
5 Email Varchar(15) Email id of user
6 Vehno Varchar(15) Vehicle number of user
7 Vehicle name Varchar(25) Vehicle name of user
8 Type Varchar(15) Type of vehicle
9 Permit type Varchar(18) Type of permit
10 License no Int(25) License number
 Table 5.6.2 Case Details

Primary key: Case number

Foreign key: Vehicle number

This table describes about the case details.

S.No. Field Data type Description

1 Caseno Int(10) Case number of holder

2 Cardno Int(15) Card number of holder

3 Name Varchar(15) Name of user

4 Date Date/time Travel date

5 Vehno Varchar(10) Vehicle number

6 Vehiclename Varchar(25) Vehicle name

7 FineAmt Numeric Fine amount

Table 5.6.3 Card Details

Primary key: User card number

This table describes about the user card details.

S.No. Field Data type Description

1 User card no Int(15) User identification number

2 Password Varchar(30) Password

 Table 5.6.4 License Details

Primary key: license no

This table describes about the user license details

S.No. Field Data type Description

1 Lic_no Int(20) License no of user
2 Name Varchar(15) Name of user

3 Address Varchar(50) Address of user

4 Mob Int(10) Mobile no of user
5 Aathar_no Int(25) Aathar no of user
6 Start_date Date/time Start date of license
7 Expiry_date Date/time Expiry date of license

8 Period Int(15) Time period of license

Table 5.6.5 Vehicle Registration Details

Primary key: RC number

This table describes about the Vehicle Registration details

S.No. Field Data type Description

1 RC_no Int(20) RC no of vehicle
2 Name Varchar(15) Name of user
3 Address Varchar(50) Address of user
4 Mob Int(10) Mobile no of user

5 Type Varchar(15) Type of vehicle

6 Veh_name Varchar(25) Name of vehicle
7 Veh_no Varchar(15) Vehicle number
8 Veh_color Int(15) Color of vehicle
 Table 5.6.6 Fitness Certificate Details

Primary key: FC number

This table describes about the Vehicle Registration details

S.No. Field Data type Description

1 FC_no Int(20) FC no of vehicle

2 Name Varchar(15) Name of user

3 Expiry_date Varchar(15) Expiry date of fc

4 Start_date Int(10) Start date of fc

5 Type Int(15) Type of vehicle

6 Veh_name Varchar(25) Name of vehicle

7 Veh_no Int(15) Vehicle number

8 Ren_date Date/time Renewal date

5.7 INPUT DESIGN
Input design is the process of converting user-originated inputs to a computer-
based format. Input design is one of the most expensive phases of the operation of
computerized system and is often the major problem of a system. Input design is a
part of overall design, which requires careful attribute. In a c c u r a t e i n p u t d a t
a arethe most common cause of errors in data proces
s i n g. The g o a l o f designing input data is to make data entry as easy, logical
and free from errors. In t h e s ys t e m d e s i gn p h a s e i n p u t d a t a a r e c
o l l e c t e d a n d o r g a n i z e d i n t o gr o u p s o f similar data.

Figure 5.7.1 Input Screen

5.8 OUTPUT DESIGN
Output design generally refers to the results and information that are generated
by the system for many end-users. Output is the main reason for developing the
system and the basis on which they evaluate the usefulness of the application.
Computer output is the most important and direct source of information to the user.
Output design is very important phase because the output will be in an interactive
manner. The output will be in such a way that the user can see it from the screen and
can take a hard copy from the printer.

In output design the admin can view the reports for user details, case details,
license details and so on.

Figure 5.8.1 Output Screen

 CHAPTER 6

SYSTEM TESTING

The most important phase in system development life cycle is system testing.
The number and nature of errors in a newly designed system depends on the system
specifications and the time frame given for the design.

A newly designed system should have all the subsystems working together,
but in reality each subsystems work independently. During this phase, all the
subsystems are gathered into one pool and tested to determine whether it meets the
user requirements.

Testing is done at two levels .Testing of individual modules and testing the
entire system. During the system testing, the system is used experimentally to ensure
that the software will run according to the specifications and in the way the user
expects. Each test case is designed with the intent of finding errors in the way the
system will process it.

6.1 UNIT TESTING

Unit testing is the first level of testing. The different modules are tested
against the specifications produced during the integration. This is done to test the
internal logic of each module. Those resulting from the interaction between modules
are initially avoided. The input received and output generated is also tested to see
whether it falls in the expected range of values. Unit testing is performed from the
bottom up, starting with the smallest and lowest modules and proceeding one at a
time.

The units in a system are the modules and routines that are assembled and
integrated to perform a specific function. The programs are tested for correctness of
logic applied and detection of errors in coding. Each of the modules was tested and
errors are rectified. They were then found to function properly.

For example, in RTO Management System user enters the username and
password to login. The validation is performed to identify the valid user. After the
validation is successful the system allows the user to enter into the RTO Management
System.

6.2 INTEGRATION TESTING

Integration testing is testing in which, the tested modules are combined into
sub-systems, which are then tested. The goal of integration testing to check whether
the modules can be integrated properly emphasizing on the interfaces between
modules. The different modules were linked together and integration testing done on
them.

After unit testing all the forms are integrated to the respective pages. While
integrating, the application developer checked whether the integrated forms are
working properly or not. The pages like new lead adding and editing, Project, General
settings, etc. are integrated with the system. These programs were tested individually
at last all these programs were combined together by creating another program.

6.3 VALIDATION TESTING

The objective of the validation test is to tell the user about the validity and
reliability of the system. It verifies whether the system operates as specified and
the integrity of important data is maintained. User motivation is very important for the
successful performance of the system.

In validation testing, each fields like card no, license no, name, email, gender,
contact number, etc. for example, the validation is mainly for login page and
registration page. The user name must contain an alphabet. Password is alpha
numeric. The user contact number must contain numbers (0-9) only. The user name
must contain only alphabets. The login id and password field must not be blank. Card
no must be unique.
6.4 OUTPUT TESTING

After performing validation testing the next step is output testing of the
proposed system. Since the system cannot be useful if it does not produce the required
output. Asking the user about the format in which the system is required tests output
displayed or generated by the system user consideration. And the output comes
according to the specifications requested by the user.

In output testing, the reports are verified and tested by the admin. User reports,
Case reports, License reports, are the main reports generated in this application. For
example, blank and empty reports are not allowed to generate.

6.5 USER ACCEPTENCE TESTING

User acceptance is a type of testing performed by the Client to certify the

system with respect to the requirements that was agreed upon. This testing happens in
the final phase of testing before moving the software application to Market or
Production environment.

The steps taken for User Acceptance Testing typically involve one or more of
the following:

User Acceptance Test (UAT) Planning

Designing UA Test Cases
Selecting a Team that would execute the (UAT) Test Cases
Executing Test Cases
Documenting the Defects found during UAT
Resolving the issues/Bug Fixing
Sign Off

For example, to ensure an effective User Acceptance Testing Test cases are
created for RTO Management System. These Test cases can be created using various
use cases identified during the Requirements definition stage. The Test cases ensure
proper coverage of all the scenarios during testing.
 CHAPTER 7

SYSTEM IMPLEMENTATION

The project entitled RTO Management System is implemented to user

environment as new system replacing the older version. This project is provided as a
new release to the client with the required features enhanced. Implementation is the
most crucial stage in achieving a successful system and giving the users confidence
that the new system is effective and workable

The project execution was checked with live environment and the user
requirements are satisfied. Proper implementation is essential to provide a reliable
system to meet the organization requirements.
 CHAPTER 8
CONCLUSION AND FUTURE ENHANCEMENT

8.1 CONCLUSION
The project RTO Management System was successfully designed and
developed as per the requirements and specification. It is concluded that the
application works well. The application is tested very well and errors are properly
debugged. The application is simultaneously accessed from more than one system.
Simultaneous login from more than one place is tested.

This system is user friendly so everyone can use easily. Proper documentation
is provided. The end user can easily understand how the whole system is implemented
by going through the documentation. The system is tested, implemented and the
performance is found to be satisfactory. All necessary output is generated. Thus, the
project is completed successfully.

8.2 FUTURE ENHANCEMENT

Further enhancement will be made to application, so the functions become

very attractive and useful manner than the present one. The smart card technique for
the RTO Management System will be enhanced to android mobile application and it
will be developed for mobile applications like iPhone and Blackberry, which used
different operation systems, such as IOS and BBOS.

The finger print technique will be implemented to the project for the efficient
data retrieval. The speed of the transactions will become more effective.
 APPENDIX 1

A.1 SOURCE CODE

LOGIN FORM

Imports System.Data.SqlClient
Public Class Form1
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
cn.Open()
Dim cmd As New SqlCommand("select * from tbl_user where user_name='" &
TextBox1.Text & "' and password='" & TextBox2.Text & "' ", cn)
Dim dr As SqlDataReader = Nothing
dr = cmd.ExecuteReader()
If dr.Read() Then
main.MenuStrip1.Enabled = True
Me.Hide()
Else
MessageBox.Show("Enter Correctly..!")
End If
dr.Close()
cn.Close()
End Sub
End Class

MAIN FORM

Imports System.Windows.Forms
Public Class main
Private m_ChildFormNumber As Integer
Private Sub main_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
 Form1.MdiParent = Me
Form1.Show()
End Sub

Private Sub ExitToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e

As System.EventArgs) Handles ExitToolStripMenuItem.Click
End
End Sub

Private Sub LicenseDetailsToolStripMenuItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles
LicenseDetailsToolStripMenuItem.Click
licensedet.MdiParent = Me
licensedet.Show()
End Sub

Private Sub ToolStripMenuItem1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles ToolStripMenuItem1.Click
user.MdiParent = Me
user.Show()
End Sub

Private Sub CaseDetailsToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles CaseDetailsToolStripMenuItem.Click
casedetail.MdiParent = Me
casedetail.Show()
End Sub

Private Sub VerificationToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles VerificationToolStripMenuItem.Click
verification.MdiParent = Me
verification.Show()
End Sub
Private Sub UserReportToolStripMenuItem_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles UserReportToolStripMenuItem.Click
rep_user.MdiParent = Me
rep_user.Show()
End Sub

Private Sub LicenseReportToolStripMenuItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles
LicenseReportToolStripMenuItem.Click
rep_license.MdiParent = Me
rep_license.Show()
End Sub

Private Sub CaseReportToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles CaseReportToolStripMenuItem.Click
rep_case.MdiParent = Me
rep_case.Show()
End Sub
End Class

USER FORM

Imports System.Data.SqlClient
Public Class user
Private Sub vehicle_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
fillgrid()
fun1()
TextBox1.Visible = False
End Sub
Public Sub fun1()
Try
 cn.Open()
Dim da As New SqlDataAdapter("select cardno from tbl_license", cn)
Dim dt As New DataTable
Dim dr As DataRow
da.Fill(dt)
cn.Close()
For Each dr In dt.Rows
ComboBox1.Items.Add(dr.Item(0))

Next
Catch ex As Exception
MsgBox(ex.ToString())
End Try
End Sub
Private Sub button6_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles button6.Click
clr()
End Sub
Public Sub clr()
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
textBox6.Text = ""
textBox7.Text = ""
textBox8.Text = ""
End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click
Try
If cn.State = ConnectionState.Closed Then cn.Open()
 cmd = New SqlCommand("insert into tbl_userdet values('" &
ComboBox1.Text & "','" & TextBox2.Text & "','" & TextBox3.Text & "','" &
TextBox4.Text & "','" & TextBox5.Text & "','" & textBox6.Text & "','" &
textBox7.Text & "','" & textBox8.Text & "','" & DateTimePicker1.Text & "')", cn)
cmd.ExecuteNonQuery()
MsgBox("Successfully Saved", MsgBoxStyle.Exclamation)
cn.Close()
Catch ex As Exception
MsgBox(ex.Message, MsgBoxStyle.Critical)
End Try
fillgrid()
End Sub
Private Sub fillgrid()
Dim da As New SqlDataAdapter("select * from tbl_userdet", cn)
If cn.State = ConnectionState.Closed Then cn.Open()
Dim ds As New DataSet
da.Fill(ds)
DataGridView1.DataSource = ds.Tables(0)
cn.Close()
End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button3.Click
Try
' Dim i As Integer = InputBox("Enter Id to Delete", "Delete")
If cn.State = ConnectionState.Closed Then cn.Open()
cmd = New SqlCommand("delete from tbl_userdet where cardno='" &
TextBox1.Text & "'", cn)
cmd.ExecuteNonQuery()
MsgBox("Deleted Successfully", MsgBoxStyle.Exclamation)
cn.Close()
fillgrid()
 Catch ex As Exception
MsgBox(ex.Message, MsgBoxStyle.Critical)
End Try
nd Sub

Dim iId As String

Private Sub DataGridView1_CellClick(ByVal sender As Object, ByVal e As
System.Windows.Forms.DataGridViewCellEventArgs) Handles
DataGridView1.CellClick
iId = DataGridView1.Rows(e.RowIndex).Cells(0).Value
Try
If cn.State = ConnectionState.Closed Then cn.Open()
cmd = New SqlCommand("select * from tbl_userdet where cardno='" & iId &
"'", cn)
Dim dr As SqlDataReader
dr = cmd.ExecuteReader
If dr.Read Then
TextBox1.Text = dr(0)
TextBox2.Text = dr(1)
TextBox3.Text = dr(2)
TextBox4.Text = dr(3)
TextBox5.Text = dr(4)
textBox6.Text = dr(5)
textBox7.Text = dr(6)
textBox8.Text = dr(7)
DateTimePicker1.Text = dr(8)
End If
cn.Close()
Catch ex As Exception
MsgBox(ex.Message, MsgBoxStyle.Critical)
End Try
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Try
If cn.State = ConnectionState.Closed Then cn.Open()
cmd = New SqlCommand("update tbl_userdet set name='" & TextBox2.Text
& "',addr='" & TextBox3.Text & "',mobile='" & TextBox4.Text & "',phone='" &
TextBox5.Text & "',email='" & textBox6.Text & "',aadhar='" & textBox7.Text &
"',blood='" & textBox8.Text & "',dob='" & DateTimePicker1.Text & "' where
cardno='" & TextBox1.Text & "'", cn)
cmd.ExecuteNonQuery()
MsgBox("Data are Successfully Updated", MsgBoxStyle.Exclamation)
cn.Close
MsgBox(ex.Message, MsgBoxStyle.Critical)
End Try
fillgrid()
End Sub

Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button5.Click
Me.Close()
End Sub
Private Sub ComboBox1_SelectedIndexChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles ComboBox1.SelectedIndexChanged
If cn.State = ConnectionState.Closed Then cn.Open()
Try
cmd = New SqlCommand("select name from tbl_license where cardno='" &
ComboBox1.Text & "' ", cn)
Dim dr As SqlDataReader = cmd.ExecuteReader()
If (dr.Read()) Then
TextBox2.Text = dr(0).ToString()
End If
Catch ex As Exception
End Try
 cn.Close()
End Sub
End Class

PASSWORD FORM

Imports System.Data.SqlClient
Public Class password
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
If TextBox2.Text = TextBox3.Text Then
cn.Open()
Dim cmd1 As New SqlCommand()
cmd1.CommandText = "update tbl_user set password='" & TextBox3.Text &
"'"
cmd1.Connection = cn cmd1.ExecuteNonQuery()
MessageBox.Show("Password Changed Successfully")
cn.Close()
Else
MessageBox.Show("Mismatch Password...Please Check..!")
End If
End Sub
End Class
 APPENDIX 2

A.2 SCREENSHOTS
MAIN PAGE

Figure A.2.1 Main Page

ADMIN LOGIN PAGE

Figure A.2.2 Admin Login Page

LICENSE DETAIL PAGE

Figure A.2.3 License detail page

LICENSE DETAILS SAVED PAGE

Figure A.2.4 License details saved page

USER DETAIL FORM

Figure A.2.5 User Detail Form

USER DETAILS SAVED FORM

Figure A.2.6 User Details saved Form

CASE DETAIL FORM

Figure A.2.7 Case Detail Form

VERIFICATION FORM

Figure A.2.8 Verification Detail Form

PASSWORD CHANGING PAGE

Figure A.2.9 Password changing page

USER REPORT

Figure A.2.10 User Report page

LICENSE REPORT

Figure A.2.11 License Report page

CASE REPORT PAGE

Figure A.2.12 Case Report page

 REFERENCES

BOOKS

1. Bill Hamilton, Programming SQL Server 2005, O'Reilly Media Publisher,

2006.
2. Elias M.Award,System Analysis and Design, Galgotia Publications, Second
Edition.
3. Daniel Solis, Illustrated C# 2008, Apress Publisher, 2008.
4. David B. Makofske, Michael J. Donahoo, Kenneth L. Calvert, TCP/IP
Sockets in C#, Academic Press Publishers, 2004.
5. Richard Blum, C# Network Programming, John Wiley & Sons Publishers,
2006.
6. Robin Dewson, Pro SQL Server 2005, Apress Publisher.
7. Roger S. Pressman,Software Engineering, Fourth Edition, 2005.

WEBSITE
1. http://www.dotnetspider.com
2. http://www.programersheaven.com
3. http://www.sql-server-performance.com
4. http://www.developerfusion.com
5. http://www.winsocketdotnetworkprogramming.com