0% found this document useful (0 votes)

7 views67 pages

E Rto

The E-RTO Management System aims to automate the functions of the Road Transport Department (RTO) in India, addressing issues related to vehicle registration and license issuance through a mobile application. It streamlines processes, reduces paperwork, and enhances efficiency by allowing users to access and manage their vehicle and driver information online. The proposed system is designed to minimize corruption, save time, and improve the overall experience for both RTO officials and vehicle owners.

Uploaded by

nazar

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

7 views67 pages

E Rto

Uploaded by

nazar

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

E-RTO Management System

Abstract

With the increasing importance of corruption has become a major factor to be considered as a

result the number of vehicles and rapid development of population are growing in our

everyday life. The process of developing ERTO Management, Automation of Road Transport

Department through Cellular Network has gained major attention by traffic police, RTO

officers and public. Now a day’s population has become a major factor to be considered as a

result the number vehicles are growing with increasing problems of vehicle registration

management, license registration, emission, insurance etc for RTO departments and to handle

user and vehicle document verification by traffic police officers. Now a day’s many people

are purchasing two wheelers, four wheelers etc. So the RTO employees having lot of work

burden of making registration, License issue, transfer etc., which required lot of paper work.

As a result people cannot get the things done in right time, which waste the time, energy.

Similarly the vehicle owner sometimes forgets to carry the license, and forgets the insurance

date at the time of enquiry.

Introduction

ERTO is an Automation of Road Transport Department through Cellular Network and our
ERTO is a step in the era of Mobile computing by using adobe flex and visual studio which
will make it easy for RTO professionals to manage and administrate internal office data and
also access it on field during enquiry via Mobile applications. Our paper work allows in
office data entry professionals not only to key in the data but to also edit, update, delete and
print information via Graphical interactive forms and on mobile flash web enabled
application. It also enables officers to pay fine which generates fine amount automatically
with status such license type, date, paid or unpaid status forms and display vehicle license,
registration, emission details on just a click of the button. On the other hand it also provides
the on field officials to access data from the Database on server by just using a php based
interface by flash enabled mobile application which will fetch data from a server that is
physically present on the server with device and location independence. This means that the
user with a mere knowledge of operating a mobile can access information at his fingertips
within a few seconds without physically visiting or accessing the data from the RTO database
server present on server. ERTO is an advanced ERTO management system which is designed
keeping in view to make the existing registration and insurance system easier and faster. It
includes the entire registration and insurance procedure starting from the initial phase of
entering till the results. It is more reliable, accurate, time saving and free from any misuse.
The system provides information regarding the RTO application and its status. The tedious
jobs such as verifying all the records of the applicant, confirming all the personal details are
furnished, submission of qualification documents, driving license, registration details, etc.,
are done in the most convenient way to the administrator. Also security is being provided in
the most proficient way. All the intermediate stages starting from receiving of the application
form to revealing the applicant number along with the expiry date of the license are being
dealt. This technology enables the traffic police to be more effective in controlling repeat
violators of traffic rules. Traffic Police have the database of registration numbers as well as
the history of driving license holders. When a traffic policeman would enter the details of any
vehicle caught violating traffic rules, it would give the complete details of that particular
vehicle including the name and address of owner and the make, model and other details of the
vehicle. Not only this, the details of the driving license holder would also be available.
Therefore enhanced penalties would be imposed for repetition of violation of traffic rules.
Fake registration plates, if any, would be detected immediately.
Regional Transport Office (RTO) is an Indian government bureau which is responsible for the
registration of vehicles and issue of Driver’s License in India. RTO management will be
having lot of work regarding registration of vehicles and issue of driver’s license. Similarly
the vehicle owner sometimes forgets to carry the license, and forgets the insurance at the time
of enquiry. This paper proposed an approach to solve such problems that is by storing all the
information related to vehicle and driver at database by RTO administrator. E-RTO is an
advanced “ERTO management System“ which is design keeping in a view to make the
existing registration and insurance system easier and faster. It includes the entire registration
and insurance procedure starting from the initial phase of entering till the result. It is a more
reliable, accurate, time saving and free from any misuse. the system provide information
regarding the RTO Application and its status the TDER job such as verifying All the records
of the applicant , confirming all the personal detail are furnish, submission of qualification
documents, driving license , registration details, etc. are done in the most convenient way to
the administrator. Also security is being provided in the most proficient way of the
intermediate stages starting from the receiving of the application form to revealing the
applicant number along with the expiry date of license are being dealt. Advantages of this
application are-Considerably reduce the corruption in transport department. Keep the license
documents safely. In case of accidents helps to identify the injured person and also helps to
find out stolen vehicle effectively. To offer the drivers to be independent of vehicle related
papers. ERTO is an advanced ”ERTO Management System” which is designed keeping in
view to make the existing registration and insurance system easier and faster. It includes the
entire registration and insurance procedure starting from the initial phase of entering till the
results. It is more reliable, accurate, time saving and free from any misuse. Smart
Environment.

With relation to car registration and licence issuance, RTO management will be quite busy. Similar to
this, the owner of the vehicle may occasionally forget to have their licence or insurance with them
when asked. In order to address these issues, the report suggested that RTO administrators save all
relevant data about the vehicle and the driver in a database. RTO is a sophisticated "RTO management
System" that was created with the goal of making the existing registration process and the issuance of
information about licences faster and easier. It starts with the complete registration and insurance
process and from the beginning of entry until the conclusion. It is more trustworthy, accurate, time-
saving, and misuse-free. The system offers details on the RTO Application.
Existing System

Existing RTO Office work is very complex, waste of time & much more Real-life problem
for example if a person wants to make driving license then he or she first goes to RTO office
and then they give work to the agent and then agent complete their work by taking a lot of
money. The system gives details on the status of the RTO application. The administrator is
given the most convenient approach to complete the tiresome tasks, which include checking
all of the applicant's records, making sure all of the personal information are provided, and
submitting qualifying papers like a driver's licence and registration information. Additionally,
security is offered in the best possible manner. Every point in between, from receiving the
application to disclosing the applicant number, along with the expiry date of the license are
being dealt. The traffic police can now more effectively manage regular traffic rule offenders
thanks to technology. The database of registration numbers and the history of drivers licence
holders are both in the possession of the traffic police. When a traffic police officer enters
information on a car that has been observed breaking traffic laws, it provides the full specifics
of that specific vehicle, including the owner's name and address as well as the make, model,
and other information about the vehicle. Additionally, the information on the holder of the
driver's licence would be accessible. Therefore, increased fines would be applied to repeat
offenders of traffic laws. Any fake licence plates would be discovered right away. Existing
RTO Office job is extremely complicated, a time waster, and more. Taking a driving licence
as an example, a person must first visit the RTO office, where they assign the task to an
agent, who then completes it while collecting a sizable fee. In this method, passing his or her
car number, that vehicle's insurance, etc., takes a long time. Additionally, everyone is in a
rush these days, therefore we developed a web application that addresses this issue and finds
a solution quickly by assessing and taking into account these issues.

Disadvantages

 Existing system is very complex, waste of time & many more

Real-life problem.

 Many employees are needed to handle current system.

 It is more expensive process.

 Immediate responses to the queries are difficult.

 Lots of times are consumed for each report generation.

 So, require to build new Website according to RTO office

Infrastructure and Facilities.

 So that all the people can get information about the e-RTO.

Proposed System

Being that we're creating a web application for RTO, we will provide a quick summary of our
project below. To create a familiar environment is allowing the less fortunate user to access
this site for workrelated RTO purposes. First, the user must fill out a registration form so that
we can authenticate him. After that, the user can select the option of his choice, for example,
if he chooses to get a driving licence, in which case we will give him information about the
requirements and an available date so that he can come on that date and take the test right
away, saving both his time and money. We make it possible for customers who purchase new
vehicles to register on our website, fill out all the necessary information, and send their
information straight to the RTO office so that the process may be completed quickly and the
customer can simply obtain their number template. Additionally to managing the RTO
database and all processes, the administrator also serves as a means of authentication. He has
the power to authorise the number for a temporary or permanent licence, a car registration
number, etc. The administrator provides facilities. It is needed to construct another site as per
RTO office framework and facilities. so that everything individuals can get the data about the
interaction to be helded in the RTO office. The principle reason for this venture is to assemble
an application program to diminish the manual work for dealing with the vehicle, registration,
taxes etc. It tracks every one of the insights regarding the client vehicle. we have utilized
[Link] and SQL worker innovation to make solid and got data set availability. .It can cause
the day by day exercises to run proficiently to and give quick reaction to recover and store the
[Link] the board framework can likewise go about as a main mechanical
instrument for the simplicity of RTO capacities, for example registration, learner's license,
and wellness etc. By his framework public can save their significant time and money. It
additionally encourages the labourers to finish their work effectively.
Advantages

 By using this system we can get Information about RTO.

Information like Driving License, Learning License and all the
RTO service online.
 This system helps to solve the time related problem.
 System helps customer to find his/her requirement in various
RTO Information online.
 It also Provide Online RTO tests.
 We can get the information at any time by using this system about.
 This system reduces all the paper work.

System Requirements
Hardware Requirements:
System : Pentium IV 2.4 GHz.
Hard Disk : 240 GB.
Monitor : 14’ Colour Monitor.
Mouse : Optical Mouse.
Ram : 2 GB.

Software Requirements:
Operating system : Windows 7 Ultimate.
Coding Language : [Link] with C#
Front-End : Visual Studio 2010 Professional.
Data Base : SQL Server 2008.

Software Description:
.NET Frame Work
The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet. The .NET
Framework is designed to fulfil the following objectives:
 To provide a consistent object-oriented programming environment whether object
code is stored and executed locally, but Internet-distributed, or executed remotely.
 To provide a code-execution environment that guarantees safe execution of code,
including code created by an unknown or semi-trusted third party.
 To provide a code-execution environment that eliminates the performance problems
of scripted or interpreted environments.
 To make the developer experience consistent across widely varying types of
applications, such as Windows-based applications and Web-based applications.
 To build all communication on industry standards to ensure that code based on
the .NET Framework can integrate with any other code.
The .NET Framework has two main components: the common language
runtime and the .NET Framework class library. The common language runtime is the
foundation of the .NET Framework. One can think of the runtime as an agent that
manages code at execution time, providing core services such as memory
management, thread management, and remoting, while also enforcing strict type
safely and other forms of code accuracy that ensure security and robustness.
In fact, the concept of code management is a fundamental principle of the
runtime. Code that targets the runtime is known as managed code, while code that
does not target the runtime is known as unmanaged code.
The class library, the other main component of the .NET Framework, is a
comprehensive, object-oriented collection of reusable types that you can use to
develop applications ranging from traditional command-line or graphical Voter
interface (GUI) applications to applications based on the latest innovations provided
by [Link], such as Web Forms and XML Web services.
The .NET Framework can be hosted by unmanaged components that load the
common language runtime into their processes and initiate the execution of managed
code, thereby creating a software environment that can exploit both managed and
unmanaged features.
The .NET Framework not only provides several runtime hosts, but also
supports the development of third-party runtime hosts.
The .NET Framework is a multi-language environment for building,
deploying, and running XML Web services and applications. It consists of three main
parts:

[Link]
[Link] is more than the next version of Active Server Pages (ASP); it is a
unified web development platform that provides the services necessary for developers
to build enterprise-class Web applications. While [Link] is largely syntax
compatible with ASP, it also provides a new programming model and infrastructure
for more secure, scalable and stable applications. You can feel free to augment your
existing ASP application by incremental adding [Link] functionality to them.
[Link] is a compiled, .NET-based environment; you can author
applications in any .NET compatible language, including Visual Basic .NET, and
Jscript .NET. Additionally, the entire .NET Framework is available to any [Link]
application. Developers can easily access the benefits of these technologies, which
include the managed common language runtime environment, type safely, inheritance,
and so on.
[Link] has been designed to work seamlessly with WYSIWYG HTML
editors and other programming tools, including Microsoft Visual Studio .NET. Not
only does this make Web development easier, but it is also provides all the benefits
that these tools have to offer, including a GUI that developers can use to drop server
controls onto a Web page and fully integrated debugging support.
Developers can use Web Forms or XML Web services when creating an
[Link] application, or combine these in any way they see fit. Each is supported by
the same infrastructure that allows you to use authentication schemes; caches
frequently used data, or customize your application’s configuration, to name only a
few possibilities.
Web Forms allow you to build powerful forms-based Web pages. When
building these pages, you can use [Link] server controls to create common UI
elements, and program them for common tasks. These controls allow you to rapidly
build a Web Form out of reusable built-in or custom components, simplifying the
code of a page.
An XML Web service provides the means to access server functionality
remotely. Using XML Web services, businesses can expose programmatic interfaces
to their data or business logic, which in turn can be obtained and manipulated by
client and server applications.
An XML Web services enable the exchange of data in client-server or server-
server scenarios, using standards like HTTP and XML messaging to move data across
firewalls. XML Web services are not tied to a particular component technology or
object-calling convention. As a result, programs written in any language, using any
component model, and running on any operating system can access XML Web
services. Each of these models can take full advantage of all [Link] features, as
well as the power of the .NET Framework and .NET Framework common language
runtime. These features and how you can use them are outlined as follows.
If you have ASP development skills, the new [Link] programming model
will seem very familiar to you. However, the [Link] Object model has changed
significantly from ASP, making it more structured and object-oriented. Unfortunately
this means that [Link] is not fully backward compatible; almost all existing ASP
pages will have to be modified to some extent in order to run under [Link].
In addition, major changes to Visual Basic .NET means that existing ASP
pages written with Visual Basic Scripting Edition typically will not port directly to
[Link]. In most cases, though, the necessary changes will involve only a few lines
of code. Accessing databases from [Link] Applications is an often-used technique
for displaying data to Web site visitors. [Link] makes it easier than ever to access
databases for this purpose it also allows you to manage the database from your code.
[Link] provides a simple model that enables Web developers to write logic
that runs at the application level. Developers can write this code in the Global .asax
text file or in a compiled class deployed as an assembly. This logic can include
application-level events, but developers can easily extend this model to suit the needs
of their Web application.
[Link] takes advantage of performance enhancements found in the .NET
Frame work and common language run time. Additionally, it has been designed to
offer significant performance improvements over ASP and other Web development
platforms. All [Link] code is compiled ,rather than interpreted, which allows early
binding, strong typing, and just-in-time (JIT) compilation to native code, to name only
a few of its benefits. [Link] is also easily factorable, meaning that developers can
remove modules (a session model, for instant) that are not relevant to the application
they are developing.
[Link] offers the Trace context class, which allows you to write custom
debug statements to your pages as you develop them. They appear only when you
have enabled tracing for a page or entire application. Enabling tracing also appends
details about a request to the page, or, if you so specify, to a custom trace viewer that
is stored in the root directory of your application.
The .NET Framework and [Link] provide default authorization and
authentication schemes for Web applications. You can easily remove, add to, or
replace these schemes, depending upon the needs of your application.
[Link] configuration settings are stored in XML-based files, which are
human readable and writable. Each of your applications can have a distinct
configuration file and you can extend the configuration scheme to suit your
requirements.
Applications are said to be running side by side when they are installed on the
same computer but use different versions of the .NET Framework. IS 6.0 uses a new
process model called worker process isolation mode, which is different from the
process model used in previous versions of IIS. [Link] uses this process model
default when running on windows server 2003.
[Link]:
[Link] provides consistent access to data sources such as Microsoft SQL
server, as well as data sources exposed through OLE DB and XML. Data-sharing
consumer applications can use [Link] to connect to these data source and retrieve,
manipulate update data.
[Link] cleanly factors data access from data manipulation into discrete
components that can be used separately or in tandem. [Link] includes .NET
Framework data providers for connecting to a database, executing commands and
retrieving results. Those results are either processed directly, or placed in an
[Link] Data Set object in order to be exposed to the used in an ad-hoc manner,
combined with data from multiple sources, or remote between tiers.
The [Link] classes are found in System. [Link], and are integrated with
the XML classes found in [Link]. When compiling code that uses the
system. Data namespace, reference both [Link] and [Link].
Data processing has traditionally relied primarily on a connection-based, two-
tier model. As data processing increasingly uses multi-tier architecture, programmers
are switching to a disconnected approach to provide better scalability for their
application.

Microsoft SQL 2008

Microsoft SQL is very fast reliable and flexible Database Management
System. It provides a very high performance and it is multi threaded and multi Voter
Relational Database Management System.
Microsoft SQL is one of the most popular Relational Database Management
System on the web. The Microsoft SQL Database has become the world's most
popular open source Database, because it is free and available on almost all the
platforms. The Microsoft SQL can run on UNIX, Window, and Mac OS. Microsoft
SQL is used for the internet applications as it provides good speed and is very secure.
Microsoft SQL was developed to manage large volumes of data at very high speed to
overcome the problems of existing solutions. Microsoft SQL a be used for verity of
applications but it is mostly used for the web applications on the internet.

Microsoft SQL Features:

 Microsoft SQL is very fast and much reliable for any type of application.
 Microsoft SQL is very Lightweight application.
 Microsoft SQL command line tool is very powerful and can be used to run SQL
queries against database.
 Microsoft SQL supports indexing and binary objects.
 It is allow changes to structure of table while server is running.
 Microsoft SQL has a wide Voter base.
 It is a very fast thread-based memory allocation system.
 Microsoft SQL Written in C and C++ language.
 Microsoft SQL code is tested with different compilers.
 Microsoft SQL is available as a separate program for use in a client/server network
environment.

SQL Server

 Microsoft and Sybase released version 1.0 in 1989.

 However, the partnership between these two ended in the early 1990s.
 Microsoft maintained ownership rights to the name SQL Server.
 Since the 1990s, subsequent versions of SQL Server have been released including SQL Server
2000, 2005, 2008, 2012, 2014, 2016, 2017, and 2019

SQL Server Editions Following editions are available

SQL Server Enterprise: It is used in the high end, large scale and mission Critical busi-
ness. It provides High-end security, Advanced Analytics, Machine Learning, etc.

SQL Server Standard: It is suitable for Mid-Tier Application and Data marts. It includes basic
reporting and analytics.

SQL Server WEB: It is designed for a low total-cost-of-ownership option for Web hosters. It
provides scalability, affordability, and manageability capabilities for small to large scale Web
properties.
SQL Server Developer: It is similar to an enterprise edition for the non-production environ-
ment. It is mainly used for build, test, and [Link] Server Express: It is for small scale ap-
plications and free to [Link] SQL Server as Client-Server Architecture

Let's have a look at the below early morning conversation between Mom and her Son, Tom.

Key Components and Services of SQL Server

Database Engine: This component handle storage, Rapid transaction Processing, and Securing
Data.

SQL Server: This service starts, stops, pauses, and continues an instance of Microsoft SQL
Server. Executable name is [Link].

SQL Server Agent: It performs the role of Task Scheduler. It can be triggered by any event or
as per demand. Executable name is [Link].

SQL Server Browser: This listens to the incoming request and connects to the desired SQL
server instance. Executable name is [Link].

SQL Server Full-Text Search: This lets user running full-text queries against Character data in
SQL Tables. Executable name is [Link].

SQL Server VSS Writer: This allows backup and restoration of data files when the SQL server
is not running. Executable name is [Link].

SQL Server Analysis Services (SSAS): Provide Data analysis, Data mining and Machine
Learning capabilities. SQL server is integrated with R and Python language for advanced analyt-
ics. Executable name is [Link].

SQL Server Reporting Services (SSRS): Provides reporting features and decision-making ca-
pabilities. It includes integration with Hadoop. Executable name is ReportingServicesSer-
[Link]

SQL Server Integration Services (SSIS): Provided Extract-Transform and Load capabilities of
the different type of data from one source to another. It can be view as converting raw informa-
tion into useful information. Executable name is [Link]
SQL Server Instances

SQL Server allows you to run multiple services at a go, with each service having separate lo-
gins, ports, databases, etc. These are divided into two:

 Primary instances
 Named instances.

There are two ways through which we may access the primary instance. First, we can use the
server name. Secondly, we can use its IP address. Named instances are accessed by appending a
backslash and instance name.

For example, to connect to an instance named xyx on the local server, you should use [Link]\
xyz. From SQL Server 2005 and above, you are allowed to run up to 50 instances simultane-
ously on a server.

Note that even though you can have multiple instances on the same server, only one of them
must be the default instance while the rest must be named instances. One can run all the in -
stances concurrently, and each instance runs independent of the other instances.

Importance of SQL Server Instances

The following are the advantages of SQL Server instances:

1. For installation of different versions on one machine

You can have different versions of SQL Server on a single machine. Each installation works in-
dependently from the other installations.

2. For cost reduction

Instances can help us reduce the costs of operating SQL Server, especially in purchasing the
SQL Server license. You can get different services from different instances, hence no need for
purchasing one license for all services.

3. For maintenance of development, production and test environments separately

This is the main benefit of having many SQL Server instances on a single machine. You can use
different instances for development, production and test purposes.

4. For reducing temporary database problems

When you have all services running on a single SQL Server instance, there are high chances of
having problems with the problems, especially problems that keep on recurring. When such ser-
vices are run on different instances, you can avoid having such problems.

5. For separating security privileges

When different services are running on different SQL Server instances, you can focus on secur-
ing the instance running the most sensitive service.

6. For maintaining a standby server

A SQL Server instance can fail, leading to an outage of services. This explains the importance
of having a standby server to be brought in if the current server fails. This can easily be
achieved using SQL Server instances.

Summary:

 SQL Server is defined as a relational database management system (RDBMS) developed by

Microsoft
 T-SQL means Transact-SQL, a propriety Language by Microsoft
 Microsoft and Sybase released version 1.0 in 1989
 Various Editions of SQL Server are Enterprise, Standard, Web, Developer, and Express
 Critical components of SQL Server are Database Engine, SQL Server, SQL Server Agent, SQL
Server Browser, SQL Server Full-Text Search, etc.
 You can run multiple instances of SQL Server the same on the same machine.

C# History

History of C# language is interesting to know. Here we are going to discuss brief history of
C# language.
C# is pronounced as "C-Sharp". It is an object-oriented programming language provided by
Microsoft that runs on .Net Framework.

Anders Hejlsberg is known as the founder of C# language.

It is based on C++ and Java, but it has many additional extensions used to perform
component oriented programming approach.

C# has evolved much since their first release in the year 2002. It was introduced with .NET
Framework 1.0 and the current version of C# is 5.0.

C# Features

C# is object oriented programming language. It provides a lot of features that are given be-
low.

1. Simple
2. Modern programming language
3. Object oriented
4. Type safe
5. Interoperability
6. Scalable and Updateable
7. Component oriented
8. Structured programming language
9. Rich Library
10. Fast speed

1) Simple

C# is a simple language in the sense that it provides structured approach (to break the prob-
lem into parts), rich set of library functions, data types etc.
2) Modern Programming Language

C# programming is based upon the current trend and it is very powerful and simple for build-
ing scalable, interoperable and robust applications.

3) Object Oriented

C# is object oriented programming language. OOPs makes development and maintenance

easier where as in Procedure-oriented programming language it is not easy to manage if code
grows as project size grow.

4) Type Safe

C# type safe code can only access the memory location that it has permission to execute.
Therefore it improves a security of the program.

5) Interoperability

Interoperability process enables the C# programs to do almost anything that a native C++ ap-
plication can do.

6) Scalable and Updateable

C# is automatic scalable and updateable programming language. For updating our application
we delete the old files and update them with new ones.

7) Component Oriented

C# is component oriented programming language. It is the predominant software develop-

ment methodology used to develop more robust and highly scalable applications.

8) Structured Programming Language

C# is a structured programming language in the sense that we can break the program into
parts using functions. So, it is easy to understand and modify.
9) Rich Library

C# provides a lot of inbuilt functions that makes the development fast.

10) Fast Speed

The compilation and execution time of C# language is fast.

C# Example: Hello World

In C# programming language, a simple "hello world" program can be written by multiple

ways. Let's see the top 4 ways to create a simple C# example:

o Simple Example

o Using System

o Using public modifier

o Using namespace

C# Simple Example
1. class Program
2. {
3. static void Main(string[] args)
4. {
5. [Link]("Hello World!");
6. }
7. }

Output:

Hello World!
Description

class: is a keyword which is used to define class.

Program: is the class name. A class is a blueprint or template from which objects are cre-
ated. It can have data members and methods. Here, it has only Main method.

static: is a keyword which means object is not required to access static members. So it saves
memory.

void: is the return type of the method. It does't return any value. In such case, return state-
ment is not required.

Main: is the method name. It is the entry point for any C# program. Whenever we run the C#
program, Main() method is invoked first before any other method. It represents start up of the
program.

string[] args: is used for command line arguments in C#. While running the C# program, we
can pass values. These values are known as arguments which we can use in the program.

[Link]("Hello World!"): Here, System is the namespace. Console is

the class defined in System namespace. The WriteLine() is the static method of Console class
which is used to write the text on the console.

C# Example: Using System

If we write using System before the class, it means we don't need to specify System names-
pace for accessing any class of this namespace. Here, we are using Console class without
specifying [Link].

C# operators

An operator is simply a symbol that is used to perform operations. There can be many types
of operations like arithmetic, logical, bitwise etc.

There are following types of operators to perform different types of operations in C# lan-
guage.

o Arithmetic Operators

o Relational Operators

o Logical Operators
o Bitwise Operators

o Assignment Operators

o Unary Operators

o Ternary Operators

o Misc Operators

Precedence of Operators in C#

The precedence of operator specifies that which operator will be evaluated first and next. The
associativity specifies the operators direction to be evaluated, it may be left to right or right to
left.

Let's understand the precedence by the example given below:

int data= 10+ 5*5

The "data" variable will contain 35 because * (multiplicative operator) is evaluated before +
(additive operator).
C# Keywords

A keyword is a reserved word. You cannot use it as a variable name, constant name etc.

In C# keywords cannot be used as identifiers. However, if we want to use the keywords as

identifiers, we may prefix the keyword with @ character.

A list of Reserved Keywords available in C# programming language is given below:

<td< td="" style="color: rgb(0, 0, 0); font-family: verdana, helvetica, arial, sans-serif; font-
size: 13px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-
weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-
transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-
width: 0px; background-color: rgb(255, 255, 255); text-decoration-style: initial; text-
decoration-color: initial;"></td>

Modules

 RTO Module
 User Application Module
 Court Module

Module Description
R.T.O module

This is the first module of our paper. It is mainly used to maintain Vehicle and Driver
information. It contains information regarding Drivers License, Vehicle Registration,
Insurance and Emission information. It is an integration of several modules. It consists of
four sub-modules namely License Registration, Vehicle Registration, Insurance and
Emission. It also provides a facility to generate fine on the same system. The main advantage
of this module is that the fine details are stored in the court module immediately when the
fine is generated. It also sends an sms to the registered contact no. of the vehicle. It consists
of three modules namely Check License, Check Vehicle and Generate Fine. The RTO module
consists of the following submodules:

1. The License module includes all the information regarding applicants personal details like
Name, DOB, Address, Contact no. Identity marks, Photo and also license details such as Type
of license, License status and Validity of the license. It is also responsible for adding and
managing license related records to the database.

2. The Vehicle module includes all the information regarding Vehicle details like Vehicle
Registration no., Manufacturer Name, Model Name, Purchase Date, Fuel Type and so on. It
also includes the Vehicle Owner details like Name, Address, Contact no, It is also responsible
for adding and managing vehicle related records to the database.

3. The Insurance module includes all the information regarding Vehicle details like Vehicle
Registration no., Manufacturer Name, Model Name, Purchase Date, Fuel Type and so on. It
also includes the Vehicle Owner details like Name, Address, Contact no.. It also includes
Insurance related information like Company Name, Policy no., Validity. It is also responsible
for adding and managing insurance related records to the database.

4. The Emission module includes all the information regarding Vehicle details like Vehicle
Registration no., Manufacturer Name, Model Name, Engine Capacity, Fuel Type and so on. It
also includes the Emission details like Center Name, Emission Id and Validity. It is also
responsible for adding and managing emission related records to the database.

User application Module

This is the second module of our paper. The main advantage of this module is that the fine
details are stored in the court module immediately when the fine is generated. It also sends a
sms to the registered contact no. of the vehicle. It consists of three modules namely Check
License, Check Vehicle, and Generate Fine. The Check License module takes a License no.
as an input and returns the respective License information like Name, Photo, Type of license,
License status and Validity of the license. Incase if the record doesn't exist it shows a
respective message indicating that a record doesn't exist. The Check Vehicle module takes a
Vehicle Registration no. as an input and returns the respective Vehicle information like
Vehicle Registration no., Manufacturer Name, Model Name, Purchase Date, Fuel Type, Type
of vehicle and so on. It also includes the Vehicle Owner details like Name, Address, Contact
no. The Generate Fine module mainly focuses on generating fines for the offences
committed. It provides for selecting a variety of offences from a set of given offences for
which the fine amount is auto-generated. The user (R.T.O officer) needs to enter other
information related to Officer like Officer id and Other important Vehicle information. This
overall process requires internet for data transfer between the client and the server and the
data is stored on server.

Court Modules

This is the third module of our project. It is mainly used to maintain fine related information.
This is the module which receives the information from the flex module. It retrieves the fine
related information from the database and it can also be updated. Here we have also provided
a facility for payment of fine in Court. After the payment the registered contact number with
the associated vehicle registration no. receives an sms of the fine payment from the court
through the sms gateway.

Data Flow Diagram

Flow diagram is a collective term for a diagram representing a flow or set of dynamic
relationships in a system. The term flow diagram is also used as a synonym for flowchart, and
sometimes as a counterpart of the flowchart. Example of a flow diagram of a nuclear
submarine propulsion system. A data flow diagram shows the way information flows through
a process or system. It includes data inputs and outputs, data stores, and the various sub
processes the data moves through.
Implementation

<%@ Page Language="C#" MasterPageFile="~/[Link]" AutoEventWireup="true" CodeFile="Registra-

[Link]" Inherits="Default2" Title="Registration" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];

using [Link];

public partial class Default2 : [Link]

{
SqlConnection conn = new SqlConnection();
SqlCommand cmd = new SqlCommand();
string str = @"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\[Link];Integrated Secur-
ity=True;User Instance=True";

string sql = "";

string temp;
string photo;

protected void Page_Load(object sender, EventArgs e)

{
conn = new SqlConnection(str);
}
protected void Button1_Click(object sender, EventArgs e)
{

if ([Link])
{
[Link]([Link]("~/Document/" + [Link]));
temp = [Link] + "";
}

if ([Link])
{
[Link]([Link]("~/photo/" + [Link]));
photo = [Link] + "";
}

sql = "insert into

Registration(Username,Password,F_Name,L_Name,Address,City,Mobile,E_mail,Sec_Que,Sec_Ans,Status,temp,phot
o)values('" + [Link] + "','" + [Link] + "','" + [Link] + "','" + [Link] + "','" + Text-
[Link] + "','" + [Link] + "'," + [Link] + ",'" + [Link] + "','" + [Link] + "','"
+ [Link] + "','" + [Link] + "','" + temp + "','" + photo + "')";
cmd = new SqlCommand(sql,conn);
[Link]();
int i = [Link]();
[Link]();

if (i > 0)
{
[Link] = "record inserted...";
}
else
{
[Link] = "record not inserted...";
}
}

protected void Button2_Click(object sender, EventArgs e)

{
[Link]("~/[Link]");
}
}

<%@ Page Language="C#" MasterPageFile="~/[Link]" AutoEventWireup="true"

CodeFile="User_Login.[Link]" Inherits="_Default" Title="User_login" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" runat="Server">

</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" runat="Server">
<center>
<table>
<tr>
<td rowspan="7">
<img src="Imageicon/[Link]" alt="Image" height="210px" width="150"/>
</td>
<td align="center" colspan="3">
<h2>
User Login</h2>
</td>
</tr>
<tr>
<td>
Username:
</td>
<td>
<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
</td>
<td>
 
</td>
</tr>
<tr>
<td>
Password:
</td>
<td>
<asp:TextBox ID="TextBox2" runat="server" TextMode="Password"></asp:TextBox>
</td>
<td>
 
</td>
</tr>
<tr>
<td align="center" colspan="3">
<asp:Label ID="Label1" runat="server"></asp:Label>
</td>
</tr>
<tr>
<td align="center" colspan="3">
<asp:Button ID="Button1" runat="server" Text="Login" OnClick="Button1_Click" />
 
<asp:Button ID="Button2" runat="server" Text="Cancel" onclick="Button2_Click" />
</td>
</tr>
<tr>
<td colspan="3">
<asp:HyperLink ID="HyperLink1" runat="server" NavigateUrl="~/[Link]"
Font-Size="Medium" ForeColor="Red">New Registration</asp:HyperLink>
</td>
</tr>
<tr>
<td colspan="3">
<asp:HyperLink ID="HyperLink2" runat="server" NavigateUrl="~/User_Forgot.aspx"
Font-Size="Medium" ForeColor="Red">Forgot Password</asp:HyperLink>
</td>
</tr>
</table>
</center>
</asp:Content>

using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];

using [Link];

public partial class _Default : [Link]

string sql = "";

int Reg_id;

protected void Page_Load(object sender, EventArgs e)

{
conn = new SqlConnection(str);
}
protected void Button1_Click(object sender, EventArgs e)
{

sql = "select Reg_id from Registration where Username = '" + [Link] + "' and Password ='" + Text-
[Link] + "' ";
//[Link] = sql;

cmd = new SqlCommand(sql, conn);

[Link]();
object c = [Link]();
[Link]();

if (c != null)
{
int reg_id = [Link]([Link]());
Session["user"] = [Link];
Session["reg_id"] = Reg_id.ToString();
[Link]("~/user/[Link]");
}
else
{
[Link] = "wrong user or password...";
}

}
protected void Button2_Click(object sender, EventArgs e)
{
[Link]("~/[Link]");
}
}

RTO Test

<%@ Page Language="C#" MasterPageFile="~/[Link]" AutoEventWireup="true" CodeFile="RTO

[Link]" Inherits="_Default" Title="RTO Test" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

</td>
</tr>
<tr>
<td>
<table style="width:700px" border="0px" cellpadding="5">
<tr>
<td>
<asp:Label ID="Label1" runat="server" Text="Que." Font-Bold="True"
Font-Size="Medium" ForeColor="Black"></asp:Label></td>
<td colspan="2">
<asp:Label ID="lbl_que" runat="server" Font-Bold="True" Font-Size="Medium"
ForeColor="Red" Text="The Following sign represent"></asp:Label>
<br />
<asp:Label ID="lbl_que_g" runat="server" Font-Bold="True" Font-Size="Medium"
ForeColor="Red" Text="The Following sign represent"></asp:Label>
</td>
<td rowspan="2" style="width:130px">
<asp:RadioButton ID="opteng" runat="server" GroupName="lang" Text="English"
Font-Bold="True" AutoPostBack="True" Checked="True"
oncheckedchanged="opteng_CheckedChanged" />
 <br />
<asp:RadioButton ID="optguj" runat="server" GroupName="lang" Text="Gujarati"
Font-Bold="True" AutoPostBack="True" oncheckedchanged="optguj_CheckedChanged" />
<br />
<asp:RadioButton ID="optboth" runat="server" GroupName="lang" Text="Both"
Font-Bold="True" AutoPostBack="True"
oncheckedchanged="optboth_CheckedChanged" />
</td>
</tr>
<tr>
<td style="width:100px" >
</td>
<td style="width:500px">
 </td>
<td style="width:100px">
</td>
</tr>
<tr>
<td align="center">
1</td>
<td>
<asp:Label ID="lbl_ans1" runat="server" Text="stop"></asp:Label>
<br />
<asp:Label ID="lbl_ans1_g" runat="server" Text="stop"></asp:Label>

</td>
<td align="center">
<asp:RadioButton ID="opt1" runat="server" GroupName="opt" />
</td>
<td rowspan="3" align="center">

<asp:Image ID="Image1" runat="server" Height="100px"

ImageUrl="~/Traffic_img/1_1.png" Width="100px" />
</td>
</tr>
<tr>
<td align="center">
2</td>
<td >
<asp:Label ID="lbl_ans2" runat="server" Text="No Parking"></asp:Label>
<br />
<asp:Label ID="lbl_ans2_g" runat="server" Text="stop"></asp:Label>
</td>
<td align="center">
<asp:RadioButton ID="opt2" runat="server" GroupName="opt" />
</td>
</tr>
<tr>
<td align="center">
3</td>
<td>
<asp:Label ID="lbl_ans3" runat="server" Text="Hospital ahead"></asp:Label>
<br />
<asp:Label ID="lbl_ans3_g" runat="server" Text="stop"></asp:Label>
</td>
<td align="center">
<asp:RadioButton ID="opt3" runat="server" GroupName="opt" />
</td>
</tr>
<tr>
<td align="center">
 </td>
<td align="center">
<asp:Label ID="lblTime" runat="server" Font-Bold="True" Font-Size="Medium"
Text="40"></asp:Label>
</td>
<td>
 </td>
<td>
<asp:Label ID="lbl_c_ans" runat="server" Text="Label"></asp:Label>
</td>
</tr>

</table>
</td>
</tr>
<tr>
<td>
 </td>
</tr>

</table>

};

function redirect() {
[Link]();
}
</script>
</asp:Content>

using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];

using [Link];
//using [Link];
public partial class _Default : [Link]
{
string strCn = @"Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\[Link];Integrated Se-
curity=True;User Instance=True";

string sql = "";

SqlConnection conn;
SqlDataAdapter dap;
DataTable dt;

int q_n = 0;

protected void Page_Load(object sender, EventArgs e)

{

conn = new SqlConnection(strCn);

if (!IsPostBack)
{

sql = "SELECT TOP (15) q_id, q_name, opt_1, opt_2, opt_3, ans, image FROM rto ORDER BY NEWID()";

dap = new SqlDataAdapter(sql, strCn);

dt = new DataTable();
[Link](dt);
[Link] = dt;
[Link]();

lbl_no_of_que.Text = "0";

Show_Que();

}
else
{
chk_ans();
Show_Que();
}

//[Link]("counter", "0");
}
protected void Button1_Click(object sender, EventArgs e)
{
//int a=0;
chk_ans();
//Session["counter"] = [Link](Session["counter"].ToString());
// while(a<[Link](Session["counter"].ToString()))
// {

// }
//if ([Link][0].Text == "1")
//{
// [Link] = [Link];
//}
//else if ([Link][0].Text == "0")
//{
// [Link] = [Link];
//}
//else
//{
//}
//if ([Link][1].Text == "1")
//{
// [Link] = [Link];
//}
//else if ([Link][1].Text == "0")
//{
// [Link] = [Link];
//}
//else
//{
//}

Show_Que();

}
public void Show_Que()
{

q_n = [Link](lbl_no_of_que.Text);

// For English
lbl_que.Text = [Link][q_n].Cells[1].Text;
lbl_ans1.Text = [Link][q_n].Cells[2].Text;
lbl_ans2.Text = [Link][q_n].Cells[3].Text;
lbl_ans3.Text = [Link][q_n].Cells[4].Text;
[Link] = "~/Traffic_img/" + [Link][q_n].Cells[6].Text;
lbl_c_ans.Text = [Link][q_n].Cells[5].Text;

//===============================================
//For Gujarati
//BT_rto1 b1 = new BT_rto1();

sql = "select * from rto1 where q_id = " + [Link][q_n].Cells[0].Text;

dt = new DataTable();
MyClass my = new MyClass();
dt = my.Get_TABLE(sql);

lbl_que_g.Text = [Link][0][1].ToString();
lbl_ans1_g.Text = [Link][0][2].ToString();
lbl_ans2_g.Text = [Link][0][3].ToString();
lbl_ans3_g.Text = [Link][0][4].ToString();
/////////////////////////////////////////

//Show Que. No.......

lbl_no_of_que.Text = [Link](q_n + 1);
[Link] = "Que. : " + lbl_no_of_que.Text;
////////////
[Link] = false;
[Link] = false;
[Link] = false;
/////////////
//Display opt wise Guj-Eng Que/Ans....
Show_OPT();

}
public void Show_OPT()
{
if ([Link] == true)
{
lbl_que.Visible = true;
lbl_ans1.Visible = true;
lbl_ans2.Visible = true;
lbl_ans3.Visible = true;

lbl_que_g.Visible = false;
lbl_ans1_g.Visible = false;
lbl_ans2_g.Visible = false;
lbl_ans3_g.Visible = false;

}
if ([Link] == true)
{
lbl_que.Visible = false;
lbl_ans1.Visible = false;
lbl_ans2.Visible = false;
lbl_ans3.Visible = false;

lbl_que_g.Visible = true;
lbl_ans1_g.Visible = true;
lbl_ans2_g.Visible = true;
lbl_ans3_g.Visible = true;

}
if ([Link] == true)
{
lbl_que.Visible = true;
lbl_ans1.Visible = true;
lbl_ans2.Visible = true;
lbl_ans3.Visible = true;

lbl_que_g.Visible = true;
lbl_ans1_g.Visible = true;
lbl_ans2_g.Visible = true;
lbl_ans3_g.Visible = true;

}
}
public void chk_ans()
{

if ([Link] == true)
{
if (lbl_c_ans.Text == "opt_1")
{

[Link]("1");
}
else
{
[Link]("0");

}
}
else if ([Link] == true)
{
if (lbl_c_ans.Text == "opt_2")
{

[Link]("1");
}
else
{
[Link]("0");

}
}
else if ([Link] == true)
{
if (lbl_c_ans.Text == "opt_3")
{

[Link]("1");

}
else
{
[Link]("0");

}
}
else
{
[Link]("0");
}
set_color();

private void set_color()

{
for (int i = 0; i < [Link]; i++)
{
switch (i)
{
case 0:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];
}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 1:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];
}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 2:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 3:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 4:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 5:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 6:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 7:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 8:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 9:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 10:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 11:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 12:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 13:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
case 14:
if ([Link][i].Text == "1")
{
[Link] = [Link];
[Link] = [Link];

}
else
{
[Link] = [Link];
[Link] = [Link];
}
break;
}

protected void opteng_CheckedChanged(object sender, EventArgs e)

{
Show_OPT();

}
protected void optguj_CheckedChanged(object sender, EventArgs e)
{
Show_OPT();
}
protected void optboth_CheckedChanged(object sender, EventArgs e)
{
Show_OPT();
}

Result

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Result_Form.[Link]" Inherits="Default3"

Title="Result_Form" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"[Link]
<html xmlns="[Link]
<head runat="server">
<title>Untitled Page</title>
</head>
<body>
<center>
<form id="form1" runat="server">
<asp:DataList ID="DataList1" runat="server" DataKeyField="Reg_id"
DataSourceID="SqlDataSource1" BackColor="#DEBA84" BorderColor="#DEBA84"
BorderStyle="None" BorderWidth="1px" CellPadding="3" CellSpacing="2"
GridLines="Both">
<FooterStyle BackColor="#F7DFB5" ForeColor="#8C4510" />
<ItemTemplate>
<br />

<table style="width:100%;">
<tr>
<td>
Name :</td>
<td>
<a href="#">
<asp:Label ID="Expr1Label" runat="server" Text='<%# Eval("f_name") %>' />
</a> <a href="#"><asp:Label ID="Expr2Label" runat="server"
Text='<%# Eval("l_name") %>' />
</a>
</td>
<td rowspan="6">
<asp:Image ID="Image1" ImageUrl='<%# "~/photo/"+ Eval("photo") %>' runat="server"
Width="100px" />
</td>
</tr>
<tr>
<td>
 Address :
</td>
<td>
<a href="#">
<asp:Label ID="Expr3Label" runat="server" Text='<%# Eval("address") %>' />
</a>
</td>
</tr>
<tr>
<td>
City :</td>
<td>
<a href="#">
<asp:Label ID="Expr4Label" runat="server" Text='<%# Eval("city") %>' />
</a>
</td>
</tr>
<tr>
<td>
Mobile :</td>
<td>
<a href="#">
<asp:Label ID="Expr5Label" runat="server" Text='<%# Eval("mobile") %>' />
</a>
</td>
</tr>
<tr>
<td>
E-mail :</td>
<td>
<a href="#">
<asp:Label ID="Expr6Label" runat="server" Text='<%# Eval("e_mail") %>' />
</a>
</td>
</tr>
<tr>
<td>
 </td>
<td>
 </td>
</tr>
</table>
<br />
</ItemTemplate>
<ItemStyle BackColor="#FFF7E7" ForeColor="#8C4510" />
<SelectedItemStyle BackColor="#738A9C" Font-Bold="True" ForeColor="White" />
<HeaderStyle BackColor="#A55129" Font-Bold="True" ForeColor="White" />
</asp:DataList>
<asp:SqlDataSource ID="SqlDataSource1" runat="server"
ConnectionString="<%$ ConnectionStrings:DatabaseConnectionString1 %>"
SelectCommand="SELECT F_Name, L_Name, Address, City, Mobile, E_mail, photo, Reg_id FROM Registra-
tion WHERE (Reg_id = @id)">
<SelectParameters>
<asp:QueryStringParameter DefaultValue="1" Name="id" QueryStringField="id" />
</SelectParameters>
</asp:SqlDataSource>

<asp:Label ID="lblScore" runat="server" Font-Bold="False"

ForeColor="Black">lblScore</asp:Label>

</form>
</center>
</body>
</html>
using System;
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];
using [Link];

System Testing And Validation

Testing

The various levels of testing are

1. White Box Testing

2. Black Box Testing
3. Unit Testing
4. Functional Testing
5. Performance Testing
6. Integration Testing
7. Objective
8. Integration Testing
9. Validation Testing
10. System Testing
11. Structure Testing
12. Output Testing
13. User Acceptance Testing

White Box Testing

White-box testing (also known as clear box testing, glass box testing, transparent
box testing, and structural testing) is a method of testing software that tests internal struc-
tures or workings of an application, as opposed to its functionality (i.e. black-box testing). In
white-box testing an internal perspective of the system, as well as programming skills, are
used to design test cases. The tester chooses inputs to exercise paths through the code and de-
termine the appropriate outputs. This is analogous to testing nodes in a circuit, e.g. in-circuit
testing (ICT).

While white-box testing can be applied at the unit, integration and system levels of
the software testing process, it is usually done at the unit level. It can test paths within a unit,
paths between units during integration, and between subsystems during a system–level test.
Though this method of test design can uncover many errors or problems, it might not detect
unimplemented parts of the specification or missing requirements.

White-box test design techniques include:

 Control flow testing

 Data flow testing
 Branch testing
 Path testing
 Statement coverage
 Decision coverage

White-box testing is a method of testing the application at the level of the source code.
The test cases are derived through the use of the design techniques mentioned above: control
flow testing, data flow testing, branch testing, path testing, statement coverage and decision
coverage as well as modified condition/decision coverage. White-box testing is the use of
these techniques as guidelines to create an error free environment by examining any fragile
code.

These White-box testing techniques are the building blocks of white-box testing, whose
essence is the careful testing of the application at the source code level to prevent any hidden
errors later on. These different techniques exercise every visible path of the source code to
minimize errors and create an error-free environment. The whole point of white-box testing is
the ability to know which line of the code is being executed and being able to identify what
the correct output should be.

Levels

1. Unit testing. White-box testing is done during unit testing to ensure that the code is
working as intended, before any integration happens with previously tested code.
White-box testing during unit testing catches any defects early on and aids in any de-
fects that happen later on after the code is integrated with the rest of the application
and therefore prevents any type of errors later on.
2. Integration testing. White-box testing at this level are written to test the interactions of
each interface with each other. The Unit level testing made sure that each code was
tested and working accordingly in an isolated environment and integration examines
the correctness of the behavior in an open environment through the use of white-box
testing for any interactions of interfaces that are known to the programmer.
3. Regression testing. White-box testing during regression testing is the use of recycled
white-box test cases at the unit and integration testing levels.

White-box testing's basic procedures involve the understanding of the source code that
you are testing at a deep level to be able to test them. The programmer must have a deep un -
derstanding of the application to know what kinds of test cases to create so that every visible
path is exercised for testing. Once the source code is understood then the source code can be
analysed for test cases to be created. These are the three basic steps that white-box testing
takes in order to create test cases:

1. Input, involves different types of requirements, functional specifications, detailed de-

signing of documents, proper source code, security specifications. This is the prepara-
tion stage of white-box testing to layout all of the basic information.
2. Processing Unit, involves performing risk analysis to guide whole testing process,
proper test plan, execute test cases and communicate results. This is the phase of
building test cases to make sure they thoroughly test the application the given results
are recorded accordingly.
3. Output; prepare final report that encompasses all of the above preparations and re-
sults.
Black Box Testing

Black-box testing is a method of software testing that examines the functionality of

an application (e.g. what the software does) without peering into its internal structures or
workings (see white-box testing). This method of test can be applied to virtually every level
of software testing: unit, integration, system and acceptance. It typically comprises most if
not all higher level testing, but can also dominate unit testing as well

Test procedures

Specific knowledge of the application's code/internal structure and programming

knowledge in general is not required. The tester is aware of what the software is supposed to
do but is not aware of how it does it. For instance, the tester is aware that a particular input
returns a certain, invariable output but is not aware of how the software produces the output
in the first place.

Test cases

Test cases are built around specifications and requirements, i.e., what the application
is supposed to do. Test cases are generally derived from external descriptions of the software,
including specifications, requirements and design parameters. Although the tests used are pri-
marily functional in nature, non-functional tests may also be used. The test designer selects
both valid and invalid inputs and determines the correct output without any knowledge of the
test object's internal structure.

Test design techniques

Typical black-box test design techniques include:

 Decision table testing

 All-pairs testing
 State transition tables
 Equivalence partitioning
 Boundary value analysis
Unit testing

In computer programming, unit testing is a method by which individual units

of source code, sets of one or more computer program modules together with associated con-
trol data, usage procedures, and operating procedures are tested to determine if they are fit for
use. Intuitively, one can view a unit as the smallest testable part of an application. In proce-
dural programming, a unit could be an entire module, but is more commonly an individual
function or procedure. In object-oriented programming, a unit is often an entire interface,
such as a class, but could be an individual method. Unit tests are created by programmers or
occasionally by white box testers during the development process.

Ideally, each test case is independent from the others. Substitutes such as method
stubs, mock objects, fakes, and test harnesses can be used to assist testing a module in isola-
tion. Unit tests are typically written and run by software developers to ensure that code meets
its design and behaves as intended. Its implementation can vary from being very manual
(pencil and paper)to being formalized as part of build automation.

Testing will not catch every error in the program, since it cannot evaluate every exe-
cution path in any but the most trivial programs. The same is true for unit testing. Addition-
ally, unit testing by definition only tests the functionality of the units themselves. Therefore,
it will not catch integration errors or broader system-level errors (such as functions performed
across multiple units, or non-functional test areas such as performance).

Unit testing should be done in conjunction with other software testing activities, as
they can only show the presence or absence of particular errors; they cannot prove a complete
absence of errors. In order to guarantee correct behaviour for every execution path and every
possible input, and ensure the absence of errors, other techniques are required, namely the ap-
plication of formal methods to proving that a software component has no unexpected behav-
iour.

Software testing is a combinatorial problem. For example, every Boolean decision statement
requires at least two tests: one with an outcome of "true" and one with an outcome of "false".
As a result, for every line of code written, programmers often need 3 to 5 lines of test code.

This obviously takes time and its investment may not be worth the effort. There are
also many problems that cannot easily be tested at all – for example those that are nondeter-
ministic or involve multiple threads. In addition, code for a unit test is likely to be at least as
buggy as the code it is testing. Fred Brooks in The Mythical Man-Month quotes: never take
two chronometers to sea. Always take one or three. Meaning, if two chronometers contradict,
how do you know which one is correct?

Another challenge related to writing the unit tests is the difficulty of setting up realis-
tic and useful tests. It is necessary to create relevant initial conditions so the part of the appli -
cation being tested behaves like part of the complete system. If these initial conditions are not
set correctly, the test will not be exercising the code in a realistic context, which diminishes
the value and accuracy of unit test results.

To obtain the intended benefits from unit testing, rigorous discipline is needed
throughout the software development process. It is essential to keep careful records not only
of the tests that have been performed, but also of all changes that have been made to the
source code of this or any other unit in the software. Use of a version control system is essen-
tial. If a later version of the unit fails a particular test that it had previously passed, the ver-
sion-control software can provide a list of the source code changes (if any) that have been ap -
plied to the unit since that time.

It is also essential to implement a sustainable process for ensuring that test case fail-
ures are reviewed daily and addressed immediately if such a process is not implemented and
ingrained into the team's workflow, the application will evolve out of sync with the unit test
suite, increasing false positives and reducing the effectiveness of the test suite.

Unit testing embedded system software presents a unique challenge: Since the soft-
ware is being developed on a different platform than the one it will eventually run on, you
cannot readily run a test program in the actual deployment environment, as is possible with
desktop programs.

Functional testing

Functional testing is a quality assurance (QA) process and a type of black box test-
ing that bases its test cases on the specifications of the software component under test. Func-
tions are tested by feeding them input and examining the output, and internal program struc-
ture is rarely considered (not like in white-box testing). Functional Testing usually de-
scribes what the system does.
Functional testing differs from system testing in that functional testing "verifies a program by
checking it against ... design document(s) or specification(s)", while system testing "vali-
date a program by checking it against the published user or system requirements" (Kaner,
Falk, Nguyen 1999, p. 52).

Functional testing typically involves five steps .The identification of functions that the
software is expected to perform

1. The creation of input data based on the function's specifications

2. The determination of output based on the function's specifications
3. The execution of the test case
4. The comparison of actual and expected outputs
Performance testing

In software engineering, performance testing is in general testing performed to de-

termine how a system performs in terms of responsiveness and stability under a particular
workload. It can also serve to investigate, measure, validate or verify other quality at-
tributes of the system, such as scalability, reliability and resource usage.

Performance testing is a subset of performance engineering, an emerging computer

science practice which strives to build performance into the implementation, design and ar-
chitecture of a system.

Testing types

Load testing

Load testing is the simplest form of performance testing. A load test is usually con-
ducted to understand the behaviour of the system under a specific expected load. This load
can be the expected concurrent number of users on the application performing a specific
number of transactions within the set duration. This test will give out the response times of all
the important business critical transactions. If the database, application server, etc. are also
monitored, then this simple test can itself point towards bottlenecks in the application soft-
ware.

Stress testing

Stress testing is normally used to understand the upper limits of capacity within the
system. This kind of test is done to determine the system's robustness in terms of extreme
load and helps application administrators to determine if the system will perform sufficiently
if the current load goes well above the expected maximum.

Soak testing

Soak testing, also known as endurance testing, is usually done to determine if the sys -
tem can sustain the continuous expected load. During soak tests, memory utilization is moni-
tored to detect potential leaks. Also important, but often overlooked is performance degrada-
tion. That is, to ensure that the throughput and/or response times after some long period of
sustained activity are as good as or better than at the beginning of the test. It essentially in-
volves applying a significant load to a system for an extended, significant period of time. The
goal is to discover how the system behaves under sustained use.

Spike testing

Spike testing is done by suddenly increasing the number of or load generated by,
users by a very large amount and observing the behaviour of the system. The goal is to deter -
mine whether performance will suffer, the system will fail, or it will be able to handle dra -
matic changes in load.

Configuration testing

Rather than testing for performance from the perspective of load, tests are created to
determine the effects of configuration changes to the system's components on the system's
performance and behaviour. A common example would be experimenting with different
methods of load-balancing.

Isolation testing

Isolation testing is not unique to performance testing but involves repeating a test exe-
cution that resulted in a system problem. Often used to isolate and confirm the fault domain.

Integration testing

Integration testing (sometimes called integration and testing, abbreviated I&T) is

the phase in software testing in which individual software modules are combined and tested
as a group. It occurs after unit testing and before validation testing. Integration testing takes
as its input modules that have been unit tested, groups them in larger aggregates, applies tests
defined in an integration test plan to those aggregates, and delivers as its output the integrated
system ready for system testing.
Purpose

The purpose of integration testing is to verify functional, performance, and reliabil-

ity requirements placed on major design items. These "design items", i.e. assemblages (or
groups of units), are exercised through their interfaces using black box testing, success and
error cases being simulated via appropriate parameter and data inputs. Simulated usage of
shared data areas and inter-process communication is tested and individual subsystems are
exercised through their input interface.

Test cases are constructed to test whether all the components within assemblages in-
teract correctly, for example across procedure calls or process activations, and this is done af-
ter testing individual modules, i.e. unit testing. The overall idea is a "building block" ap-
proach, in which verified assemblages are added to a verified base which is then used to sup-
port the integration testing of further assemblages.

Some different types of integration testing are big bang, top-down, and bottom-up.
Other Integration Patterns are: Collaboration Integration, Backbone Integration, Layer Inte-
gration, Client/Server Integration, Distributed Services Integration and High-frequency Inte-
gration.

Big Bang

In this approach, all or most of the developed modules are coupled together to form a
complete software system or major part of the system and then used for integration testing.
The Big Bang method is very effective for saving time in the integration testing process.
However, if the test cases and their results are not recorded properly, the entire integration
process will be more complicated and may prevent the testing team from achieving the goal
of integration testing.

A type of Big Bang Integration testing is called Usage Model testing. Usage Model
Testing can be used in both software and hardware integration testing. The basis behind this
type of integration testing is to run user-like workloads in integrated user-like environments.
In doing the testing in this manner, the environment is proofed, while the individual compo-
nents are proofed indirectly through their use.

Usage Model testing takes an optimistic approach to testing, because it expects to

have few problems with the individual components. The strategy relies heavily on the compo-
nent developers to do the isolated unit testing for their product. The goal of the strategy is to
avoid redoing the testing done by the developers, and instead flesh-out problems caused by
the interaction of the components in the environment.

For integration testing, Usage Model testing can be more efficient and provides better
test coverage than traditional focused functional integration testing. To be more efficient and
accurate, care must be used in defining the user-like workloads for creating realistic scenarios
in exercising the environment. This gives confidence that the integrated environment will
work as expected for the target customers.

Top-down and Bottom-up

Bottom Up Testing is an approach to integrated testing where the lowest level com-
ponents are tested first, then used to facilitate the testing of higher level components. The
process is repeated until the component at the top of the hierarchy is tested.

All the bottom or low-level modules, procedures or functions are integrated and then
tested. After the integration testing of lower level integrated modules, the next level of mod-
ules will be formed and can be used for integration testing. This approach is helpful only
when all or most of the modules of the same development level are ready. This method also
helps to determine the levels of software developed and makes it easier to report testing
progress in the form of a percentage.

Top Down Testing is an approach to integrated testing where the top integrated mod-
ules are tested and the branch of the module is tested step by step until the end of the related
module.

Sandwich Testing is an approach to combine top down testing with bottom up test-
ing.

The main advantage of the Bottom-Up approach is that bugs are more easily found. With
Top-Down, it is easier to find a missing branch link.

Validation

In that case, you can use the CustomValidator control. The CustomValidator control in
[Link] allows you to create your own custom logic to validate user data. The
CustomValidator Control can be used on the client side and server side. JavaScript is used for
client validation; you can use any. Some of the popular [Link] validators
are RequiredFieldValidator, CompareValidator, RangeValidator, RegularExpressionValidator,
ValidationSummary, and CustomValidator. Server-side validation helps prevent users from
bypassing validation by disabling or changing the client script. Security Note: By default,
[Link] Web pages automatically validate that malicious users are not attempting to send
script or HTML elements to your application.

Introduction

This article explains validation in the Web API. Here I show the step-by-step procedure to
create the application using validation.

Validation

How validation works is like testing to determine that what the user entered in the field is
valid. After validating the entered field, it checks that it is in the correct format, specified
length, and you can compare the input value in various fields or against values. We can use
the validation for various types of information. That will be explained by the sample applica-
tion.

Types of Validation

Here we define the various types of validation that we can be use in our application. These
are as follows:

1. Required entry: It ensures the required field. The user cannot skip the entry.
2. Compare Value: It is ensures that the comparison of the user's entry with the constant
value or against the value of another constant or a specific data type. We use the com-
parison operator like equal, greater than, less than.
3. Range checking: It checks the range of the input values with the minimum and max-
imum range that is required for the input value. We can use the range checker with the
pairs of numbers, dates and alphabetic characters.
4. Pattern matching: It is used for checking the pattern of an input value that specifies the
sequence of characters.
5. Remote: It is used for checking whether the value exists on the server side.
System Maintenance

Software implementation C# is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. Computing relies on
sharing of resources to achieve coherence and economies of scale, similar to a utility over a
network.

This section describes the five software implementation process as:

1. The implementation processes contains software preparation and transition activities, such
as the conception and creation of the implementation plan, the preparation for handling
problems identified during development, and the follow-up medical records management,

2. The problem and modification analysis process, which is executed once the applications
has become the responsibility of the implementation group.

3. The process considering the implementation of the modification itself.

4. The process acceptance of the modification, by confirming the modified work with the
individual who submitted the request in order to make sure the modification provided a
solution.

5. Finally, the last implementation process, also an event which does not occur on daily basis,
is the retirement of a piece of software.

Snapshots

Admin Page:
Admin Registration Page:
Admin RTO Test Page:
User Home Page:
RTO Test:
Forgot password:
Feedback Page:
Contact Us Page:
Download Page:
Validation Control Page:
Conclusion

It can be concluded that our project "ERTO Management System" which is an Automation of
Road Transport Department through Cellular Network was successfully developed and tested
by our team. Our system introduces a facility for the R.T.O Officers to perform verification of
the License and Vehicle documents electronically. It will also help the R.T.O officials to
maintain records systematically and reduces a lot of paper work and manual efforts. We also
identified some general requirements of such a system and tried to meet those requirements
as much as possible in the design and implementation of our system.

Future Enhancement

In future, as per the user’s requirement our whole Program was designed. It provides a better
way of document verification for R.T.O officials. Our system is an integration of several
systems that in present act as a separate system. The future system Maintains detail
information of Driving License, Vehicle Registration, Emission and Insurance information of
related vehicle. It will also reduce a lot of clerical works and provides better accountability. A
separate sms gateway can also provide fine notification messages at the flex module. We can
also add a provision to track a stolen vehicle in the future systems either through verification
or through GPS tracking.

Bibliography

[1] Yan Lin, Senior Member, IEEE, Gary A. Jordan, Mark O. Sanford, Jinxiang Zhu, Member, IEEE,
and William H. Babcock, “Economic Analysis of Establishing Regional Transmission Organization
and Standard Market Design in the Southeast”, IEEE TRANSACTIONS ON POWER SYSTEMS,
VOL. 21, NO. 4, NOVEMBER 2006

[2]Juszkiewicz," The use of Adobe Flex in combination with Java EE technology on the example of
ticket booking system", in CAD Systems in Microelectronics (CADSM), 2011, pp. 317 - 320

[3]Wan-Mi Chen, Yu-Cheng Chen, "Web design and implementation for remote control", in
Intelligent Control and Automation (WCICA), 2012, pp. 920 - 924

[4]Xiaosheng Yu, Yichang, China Cai Yi, "Design and Implementation of the Website Based on PHP
& MYSQL", in E-Product E-Service and EEntertainment (ICEEE), 2010, pp. 1 – 4

[5]Bazghandi, "Web Database Connectivity Methods (using Mysql) in Windows Platform", in

Information and Communication Technologies, 2009, pp. 3577 - 3581

[6]Norul Huda Yusof, Rosilah Hassan, "Flash Notes and Easy Electronic Software (EES): New
Technique to Improve Digital Logic Design Learning", in International Conference on Electrical
Engineering and Informatics, 2011.

[7]Narayan S. Rau, “Issues in the Path Toward an RTO and Standard Markets”, IEEE
TRANSACTIONS ON POWER SYSTEMS, VOL. 18, NO. 2, MAY 2003.

Web Reference

[Link]
[Link]

[Link]

E-RTO Management System Overview
No ratings yet
E-RTO Management System Overview
5 pages
RTO Fine Collection
No ratings yet
RTO Fine Collection
4 pages
Regional Transportation Management Case Study
No ratings yet
Regional Transportation Management Case Study
5 pages
RTO Management System Overview
No ratings yet
RTO Management System Overview
1 page
RTO Management System Overview
No ratings yet
RTO Management System Overview
10 pages
RTO Vehicle and Driver Verification System
No ratings yet
RTO Vehicle and Driver Verification System
4 pages
Android Traffic Management System
No ratings yet
Android Traffic Management System
5 pages
Cloud-Based Vehicle Verification System
No ratings yet
Cloud-Based Vehicle Verification System
1 page
Computerized Commercial Vehicle Registration
No ratings yet
Computerized Commercial Vehicle Registration
21 pages
BRTA: Overview and Information System
No ratings yet
BRTA: Overview and Information System
22 pages
Regional Transport Office Overview
No ratings yet
Regional Transport Office Overview
11 pages
76 Ankam IEEE
No ratings yet
76 Ankam IEEE
4 pages
Automated Toll Collection via ANPR
No ratings yet
Automated Toll Collection via ANPR
74 pages
Automated UTeM Vehicle Plate Detection
No ratings yet
Automated UTeM Vehicle Plate Detection
15 pages
Malaysian License Plate Recognition System
No ratings yet
Malaysian License Plate Recognition System
14 pages
Beatrice Project Completed
No ratings yet
Beatrice Project Completed
41 pages
Smart Traffic Barrier System Design
No ratings yet
Smart Traffic Barrier System Design
8 pages
Real-Time Vehicle Speed Detection System
No ratings yet
Real-Time Vehicle Speed Detection System
57 pages
Report Number Plate Recognition
No ratings yet
Report Number Plate Recognition
51 pages
Efficient License Plate Recognition System
No ratings yet
Efficient License Plate Recognition System
51 pages
Automated Toll Gate & Vehicle Tracking System
100% (1)
Automated Toll Gate & Vehicle Tracking System
29 pages
RFID-Based Automated Toll Tracking System
No ratings yet
RFID-Based Automated Toll Tracking System
3 pages
Automated RTO Document Verification System
No ratings yet
Automated RTO Document Verification System
3 pages
Authentication Driving License System
No ratings yet
Authentication Driving License System
19 pages
SPM Reoprt
No ratings yet
SPM Reoprt
35 pages
Automated Toll Collection System
100% (1)
Automated Toll Collection System
44 pages
RFID-Based Automated Toll Collection System
No ratings yet
RFID-Based Automated Toll Collection System
14 pages
Automated Toll Gate System Overview
No ratings yet
Automated Toll Gate System Overview
1 page
Application Morphological For Vehicle License Plate Recognition
No ratings yet
Application Morphological For Vehicle License Plate Recognition
8 pages
Intelligent RFID Roadside Parking System
No ratings yet
Intelligent RFID Roadside Parking System
4 pages
Online Vehicle Registration System Design
No ratings yet
Online Vehicle Registration System Design
11 pages
Vehicle Identification System Overview
25% (4)
Vehicle Identification System Overview
46 pages
Toll Gate Automation System Overview
No ratings yet
Toll Gate Automation System Overview
3 pages
ATOM Season 9 - PS6 - BFDL - Bajaj Finserv Direct Limited
No ratings yet
ATOM Season 9 - PS6 - BFDL - Bajaj Finserv Direct Limited
1 page
Vehicle Overspeed Detection Using OCR
No ratings yet
Vehicle Overspeed Detection Using OCR
7 pages
Design and Implementation of An Online Vehicle and Plate Number Registration and Identification System in Nigeria
No ratings yet
Design and Implementation of An Online Vehicle and Plate Number Registration and Identification System in Nigeria
152 pages
Smart Traffic Control System Using MATLAB
No ratings yet
Smart Traffic Control System Using MATLAB
8 pages
RF Vehicle Identification System
No ratings yet
RF Vehicle Identification System
4 pages
Automated Traffic Surveillance System
No ratings yet
Automated Traffic Surveillance System
10 pages
Irjet V7i7216
No ratings yet
Irjet V7i7216
11 pages
Chalan e
No ratings yet
Chalan e
19 pages
RFID-Based Vehicle Theft Detection System
No ratings yet
RFID-Based Vehicle Theft Detection System
4 pages
Online Vehicle License System Overview
No ratings yet
Online Vehicle License System Overview
5 pages
Automated Traffic Violation Detection System
No ratings yet
Automated Traffic Violation Detection System
7 pages
Advanced Queue Algorithm for Toll Tax Management
No ratings yet
Advanced Queue Algorithm for Toll Tax Management
4 pages
Truck Black Box System with LabVIEW
No ratings yet
Truck Black Box System with LabVIEW
7 pages
Electronic Toll Collection System Proposal
No ratings yet
Electronic Toll Collection System Proposal
5 pages
Influence of Telematics of Ubi Insurance On The Ma
No ratings yet
Influence of Telematics of Ubi Insurance On The Ma
14 pages
Automatic Toll Collection System Design
No ratings yet
Automatic Toll Collection System Design
13 pages
Automating Traffic Ticket Management
No ratings yet
Automating Traffic Ticket Management
5 pages
On-Road Vehicle Breakdown Assistance
No ratings yet
On-Road Vehicle Breakdown Assistance
5 pages
Comparison of Time Standardization Methods On The Basis of Real Experiment
100% (1)
Comparison of Time Standardization Methods On The Basis of Real Experiment
9 pages
IoT-Enabled Virtual RTO System
No ratings yet
IoT-Enabled Virtual RTO System
2 pages
Tollsy 2
No ratings yet
Tollsy 2
10 pages
Computerized Traffic Offence System
No ratings yet
Computerized Traffic Offence System
39 pages
ALPR Techniques: A Comprehensive Review
No ratings yet
ALPR Techniques: A Comprehensive Review
11 pages
Vehicle Speed Limiter System Design
No ratings yet
Vehicle Speed Limiter System Design
13 pages
Unique License Plate Recognition System
No ratings yet
Unique License Plate Recognition System
59 pages
Managing Fleet Fines Efficiently
No ratings yet
Managing Fleet Fines Efficiently
3 pages
Enabling Secure and Efficient Ranked Keyword Search Over Outsourced Cloud Data
No ratings yet
Enabling Secure and Efficient Ranked Keyword Search Over Outsourced Cloud Data
69 pages
Evidence Protection System Using Blockchain Technology
No ratings yet
Evidence Protection System Using Blockchain Technology
66 pages
Electricity Bill Management System
No ratings yet
Electricity Bill Management System
65 pages
Advanced Reliable Real Estate Portal
No ratings yet
Advanced Reliable Real Estate Portal
63 pages
Future Enhancements for Project Development
No ratings yet
Future Enhancements for Project Development
1 page
Gauss-Jordan Elimination Explained
100% (2)
Gauss-Jordan Elimination Explained
5 pages
DCC Four-Digit Address Conversion Guide
No ratings yet
DCC Four-Digit Address Conversion Guide
4 pages
Comprehensive Computer Shortcut Keys
No ratings yet
Comprehensive Computer Shortcut Keys
5 pages
SMATV and IPTV Systems Overview
100% (2)
SMATV and IPTV Systems Overview
23 pages
Conference Proceeding
No ratings yet
Conference Proceeding
7 pages
Shell Sort Algorithm Explained
No ratings yet
Shell Sort Algorithm Explained
4 pages
Understanding ERP: Benefits and Implementation
No ratings yet
Understanding ERP: Benefits and Implementation
22 pages
Precedence Diagramming Method in Projects
No ratings yet
Precedence Diagramming Method in Projects
27 pages
Execution Template - Change Management Process
No ratings yet
Execution Template - Change Management Process
10 pages
Array Operations in C Programming
No ratings yet
Array Operations in C Programming
8 pages
ETL Developer with Informatica Expertise
No ratings yet
ETL Developer with Informatica Expertise
4 pages
Enterprise Toolkit & Support User Guide
No ratings yet
Enterprise Toolkit & Support User Guide
28 pages
Message Passing and IPC in Operating Systems
No ratings yet
Message Passing and IPC in Operating Systems
13 pages
Toco Probe Complaint Investigation Report
No ratings yet
Toco Probe Complaint Investigation Report
3 pages
Prolog Programming Exercises Guide
No ratings yet
Prolog Programming Exercises Guide
9 pages
IT Career Objective and Skills Summary
No ratings yet
IT Career Objective and Skills Summary
1 page
CPU Scheduling Algorithms Explained
No ratings yet
CPU Scheduling Algorithms Explained
17 pages
USF BIM Project Execution Plan
100% (6)
USF BIM Project Execution Plan
32 pages
Din 8743 PDF
100% (3)
Din 8743 PDF
35 pages
ABAP Interview Questions and Answers For Experienced
No ratings yet
ABAP Interview Questions and Answers For Experienced
21 pages
150+ Services You Can Offer As A VA
100% (2)
150+ Services You Can Offer As A VA
8 pages
Business Architecture Software Evaluation Matrix
100% (1)
Business Architecture Software Evaluation Matrix
2 pages
225 - 800 Cycles UMS4 Programming Guide
No ratings yet
225 - 800 Cycles UMS4 Programming Guide
105 pages
Citigroup Case Study
No ratings yet
Citigroup Case Study
6 pages
ADG004
No ratings yet
ADG004
18 pages
Defining Accelerograms in SeismoSignal
No ratings yet
Defining Accelerograms in SeismoSignal
2 pages
Desktop Assistant Project Report
No ratings yet
Desktop Assistant Project Report
18 pages
Windows Server 2008 DC & DNS Setup Guide
No ratings yet
Windows Server 2008 DC & DNS Setup Guide
25 pages
Advances in Open Set Recognition
No ratings yet
Advances in Open Set Recognition
16 pages
Convert Drive Test Logs to KML for Google Earth
No ratings yet
Convert Drive Test Logs to KML for Google Earth
7 pages

E Rto

Uploaded by

E Rto

Uploaded by

E-RTO Management System

date at the time of enquiry.

 Existing system is very complex, waste of time & many more

 Many employees are needed to handle current system.

 Immediate responses to the queries are difficult.

 Lots of times are consumed for each report generation.

 So, require to build new Website according to RTO office

Infrastructure and Facilities.

 By using this system we can get Information about RTO.

Microsoft SQL 2008

Microsoft SQL Features:

 Microsoft and Sybase released version 1.0 in 1989.

SQL Server Editions Following editions are available

Key Components and Services of SQL Server

Importance of SQL Server Instances

The following are the advantages of SQL Server instances:

1. For installation of different versions on one machine

2. For cost reduction

3. For maintenance of development, production and test environments separately

4. For reducing temporary database problems

5. For separating security privileges

6. For maintaining a standby server

 SQL Server is defined as a relational database management system (RDBMS) developed by

Anders Hejlsberg is known as the founder of C# language.

C# is object oriented programming language. OOPs makes development and maintenance

6) Scalable and Updateable

C# is component oriented programming language. It is the predominant software develop-

8) Structured Programming Language

C# provides a lot of inbuilt functions that makes the development fast.

10) Fast Speed

The compilation and execution time of C# language is fast.

C# Example: Hello World

In C# programming language, a simple "hello world" program can be written by multiple

o Using public modifier

class: is a keyword which is used to define class.

[Link]("Hello World!"): Here, System is the namespace. Console is

C# Example: Using System

Let's understand the precedence by the example given below:

int data= 10+ 5*5

In C# keywords cannot be used as identifiers. However, if we want to use the keywords as

A list of Reserved Keywords available in C# programming language is given below:

User application Module

Data Flow Diagram

<%@ Page Language="C#" MasterPageFile="~/[Link]" AutoEventWireup="true" CodeFile="Registra-

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

public partial class Default2 : [Link]

string sql = "";

protected void Page_Load(object sender, EventArgs e)

sql = "insert into

protected void Button2_Click(object sender, EventArgs e)

<%@ Page Language="C#" MasterPageFile="~/[Link]" AutoEventWireup="true"

<asp:Content ID="Content1" ContentPlaceHolderID="head" runat="Server">

public partial class _Default : [Link]

string sql = "";

protected void Page_Load(object sender, EventArgs e)

cmd = new SqlCommand(sql, conn);

<%@ Page Language="C#" MasterPageFile="~/[Link]" AutoEventWireup="true" CodeFile="RTO

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

<asp:Image ID="Image1" runat="server" Height="100px"

string sql = "";

protected void Page_Load(object sender, EventArgs e)

conn = new SqlConnection(strCn);

dap = new SqlDataAdapter(sql, strCn);

//if ([Link][2].Text == "1")

sql = "select * from rto1 where q_id = " + [Link][q_n].Cells[0].Text;

//Show Que. No.......

private void set_color()

protected void opteng_CheckedChanged(object sender, EventArgs e)

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Result_Form.[Link]" Inherits="Default3"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

<asp:Label ID="lblScore" runat="server" Font-Bold="False"

public partial class Default3 : [Link]

System Testing And Validation

The various levels of testing are

1. White Box Testing

White Box Testing