CHAPTER -1

INTRODUCTION

E Challans Information System is an online information source developed for Road Transport
Authority to facilitate the users in applying for various licenses and registrations. This tool
has been designed to facilitate the flow of information within the organization.E-
CHALLANS provides the facility of applying licenses online, issuance of permanent license,
tax challans, and receiving payments against challans.

     In the Previous System It is not efficient in performing office work in RTO services, It
includes much manual process and time consuming, It is not user friendly, Maintains local
data base. It is not Generating Accurate Reports.

   The Existing system of E-CHALLANS services has been is usage for two years. The
existing system is not giving accurate results while doing transactions. It doesn’t provide
security, anyone enter into the system and can do their own transactions. It is not flexible in
generating reports and many manual processes are made computerized.

What Is A Challan?

A challan is an official text written on a piece of paper issued to a person in particular. A

challan is usually issued for violating traffic rules and regulation in India and neighboring
countries. If a traffic challan is issued in your name, you are liable to pay the fine as
mentioned in The Motor Vehicles Act, 1988. A traffic police officer holds the right to issue a
challan in the name of any person who does not follow one or more traffic rules.

What Is E-challan?

An E-challan is nothing but an electronically generated challan with the help of Electronic
Challan System. E-challan has recently replaced the physical pieces of paper. From a person
breaking a traffic rule in India to him/her paying the corresponding fine, several stages of this
process have been digitized thanks to the introduction of the e-challan check.
 How Does The E-challan System Work?

The traffic police have introduced the CCTV-enabled e-Challan system in an attempt to
eventually curb the rising number of road accidents. A CCTV camera continuously records
footage of the ongoing traffic. If a motorist breaks any traffic rule, the act will be recorded in
the footage. The police will try to extract the number from the vehicle’s screen-shot captured
from the CCTV footage and the offense will be registered in the records.

The traffic police will be then coordinate with the Regional Transport Office (RTO) to find
the details of the vehicle and its owner. Details like the name and address of the vehicle
owner, make and model of the vehicle, etc. As soon as they receive the details, an SMS will
be sent on the registered phone number of the violator. This SMS will contain the time, date
and location of the offense.

Ways To Pay E-challan

There are two ways in which you can pay an e-challan issued in your name. The most
convenient way is to pay it online. The authorities have created a dedicated website for
paying the e-challan directly. You can easily find the e-challan payment online website for
your Indian state. The e-challan issued in your name will have a unique challan number.
Enter this number in the box provided on the website and proceed to make the payment.

    To overcome problems in the existing System a new RTO services “Road Transport
Authority Information System” is proposed after study of system. The objectives of proposed
system are: Ensure data integrity and security, less manpower, Generate accurate reports,

Accurate handling in multiple details.

E-CHALLANS has the following modules

1. Application for learner license.
2. Issuance of permanent license.
3. Issuance of road tax challans for transport vehicles.
4. Receiving payments against challans.
 Process Model
The System keeps track of the transactions in the RTO office. It maintains Renewal of
learner’s License, Renewal of permanent license, Issue of learner’s license, Online LLR
Form, Registration Form, Issue of permanent license, payment against challans and finally it
produce printouts to payment of customers.

Purpose of the project

This project Deals with the transactions of RTO services office:-

 Renewal of learner’s license.

 Renewal of permanent license.
 Issue of learner’s license.
 Issue of permanent license.
 Registration Form
 Payment against challan.
 Online LLR Form
Problem in Existing System
The Existing system of RTO services has been is usage for two years. The existing system is
not giving accurate results while doing transactions. It doesn’t provide security, anyone enter
into the system and can do their own transactions. It is not flexible in generating reports. and
many manual processes are made computerized.

The present system has following drawbacks:

o    It is not efficient in performing office work in RTO services.

o    It includes much manual process and time consuming.
o    It is not user friendly.
o    Maintains local data base.
o    It is not Generating Accurate Reports.
Solution of these Problems
To overcome problems in the existing System a new RTO services “Road Transport
Authority Information System” is proposed after study of system. The objectives of

proposed system are:

 Facilities ease of operation.
 Ensure data integrity and security.

 Less manpower.

H/W AND S/W SPECIFICATION

SOFTWARE CONFIGURATION
OPERATING PLATFORM  :           WINDOWS 2000/NT/XP
RDBMS                                              :           SQLSERVER 2000
SOFTWARE                          :           VS.NET 2003
FRONT END TOOL              :           sql server

HARDWARE CONFIGURATION
RAM                                       :           128MB
HARD DISK                          :           MINIMUM 20 GB
 LANGUAGE SPECIFICATION
FRONT END:
.NET:
.NET Framework (Pronounced Dot Net) Is A Software Framework
Developed By Microsoft That Runs Primarily On Microsoft Windows. It
Includes A Large Class Library Known As Framework Class Library (FCL)
And Provides Language Interoperability (Each Language Can Use Code
Written In Other Languages) Across Several Programming Languages.
Programs Written For .NET Framework Execute in a Software Environment
(As Contrasted To Hardware Environment), Known As Common Language
Runtime (CLR), An Application Virtual Machine That Provides Services Such
As Security, Memory Management, And Exception Handling. FCL and CLR
Together constitute .NET Framework. Common Language Runtime (CLR)
serves as the execution engine of .NET Framework. All .NET programs execute
under the supervision of CLR, guaranteeing certain properties and behaviors in
the areas of memory management, security, and exception handling.

C#:
C# (pronounced cee sharp) is a multi-paradigm programming language
encompassing strong typing, imperative, declarative, functional, generic, object-
oriented (class-based), and component-oriented programming disciplines. It was
developed by Microsoft within its .NET initiative and later approved as a
standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270:2006). C# is one of
the programming languages designed for the Common Language Infrastructure.

C# is intended to be a simple, modern, general-purpose, object-oriented

programming language. Its development team is led by Anders Hejlsberg. The
most recent version is C# 4.0, which was released on April 12, 2010.

FEATURES OF THE COMMON LANGUAGE RUNTIME

 The common language runtime manages memory, thread execution, code execution, code
safety verification, compilation, and other system services. These features are intrinsic to the managed
code that runs on the common language runtime.
With regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin (such as the Internet, enterprise network, or
local computer). This means that a managed component might or might not be able to perform file-
access operations, registry-access operations, or other sensitive functions, even if it is being used in
the same active application.
The runtime enforces code access security. For example, users can trust that an executable
embedded in a Web page can play an animation on screen or sing a song, but cannot access their
personal data, file system, or network. The security features of the runtime thus enable legitimate
Internet-deployed software to be exceptionally featuring rich.
The runtime also enforces code robustness by implementing a strict type- and code-
verification infrastructure called the common type system (CTS). The CTS ensures that all managed
code is self-describing. The various Microsoft and third-party language compilers

Generate managed code that conforms to the CTS. This means that managed code can
consume other managed types and instances, while strictly enforcing type fidelity and type safety.
In addition, the managed environment of the runtime eliminates many common software
issues. For example, the runtime automatically handles object layout and manages references to
objects, releasing them when they are no longer being used. This automatic memory management
resolves the two most common application errors, memory leaks and invalid memory references.
The runtime also accelerates developer productivity. For example, programmers can write
applications in their development language of choice, yet take full advantage of the runtime, the class
library, and components written in other languages by other developers. Any compiler vendor who
chooses to target the runtime can do so. Language compilers that target the .NET Framework make
the features of the .NET Framework available to existing code written in that language, greatly easing
the migration process for existing applications.
While the runtime is designed for the software of the future, it also supports software of today
and yesterday. Interoperability between managed and unmanaged code enables developers to continue
to use necessary COM components and DLLs.
The runtime is designed to enhance performance. Although the common language runtime
provides many standard runtime services, managed code is never interpreted. A feature called just-in-
time (JIT) compiling enables all managed code to run in the native machine language of the system on
which it is executing. Meanwhile, the memory manager removes the possibilities of fragmented
memory and increases memory locality-of-reference to further increase performance.
 Finally, the runtime can be hosted by high-performance, server-side applications, such as
Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure enables you to
use managed code to write your business logic, while still enjoying the superior performance of the
industry's best enterprise servers that support runtime hosting.

.NET FRAMEWORK CLASS LIBRARY

The .NET Framework class library is a collection of reusable types that tightly integrate with
the common language runtime. The class library is object oriented, providing types from which your
own managed code can derive functionality. This not only makes the .NET Framework types easy to
use, but also reduces the time associated with learning new features of the .NET Framework. In
addition, third-party components can integrate seamlessly with classes in the .NET Framework.
For example, the .NET Framework collection classes implement a set of interfaces that you
can use to develop your own collection classes. Your collection classes will blend seamlessly with the
classes in the .NET Framework.
As you would expect from an object-oriented class library, the .NET Framework types enable
you to accomplish a range of common programming tasks, including tasks such as string
management, data collection, database connectivity, and file access. In addition to these common
tasks, the class library includes types that support a variety of specialized development scenarios. For
example, you can use the .NET Framework to develop the following types of applications and
services:
 Console applications.
 Scripted or hosted applications.
 Windows GUI applications (Windows Forms).
 ASP.NET applications.
 XML Web services.
 Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable types that
vastly simplify Windows GUI development. If you write an ASP.NET Web Form application, you
can use the Web Forms classes.
CLIENT APPLICATION DEVELOPMENT

Client applications are the closest to a traditional style of application in Windows-based

programming. These are the types of applications that display windows or forms on the desktop,
enabling a user to perform a task. Client applications include applications such as word processors
and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools, and
so on. Client applications usually employ windows, menus, buttons, and other GUI elements, and they
likely access local resources such as the file system and peripherals such as printers.
Another kind of client application is the traditional ActiveX control (now replaced by the
managed Windows Forms control) deployed over the Internet as a Web page. This application is
much like other client applications: it is executed natively, has access to local resources, and includes
graphical elements.
In the past, developers created such applications using C/C++ in conjunction with the
Microsoft Foundation Classes (MFC) or with a rapid application development (RAD) environment
such as Microsoft® Visual Basic®. The .NET Framework incorporates aspects of these existing
products into a single, consistent development environment that drastically simplifies the
development of client applications.
The Windows Forms classes contained in the .NET Framework are designed to be used for
GUI development. You can easily create command windows, buttons, menus, toolbars, and other
screen elements with the flexibility necessary to accommodate shifting business needs.
For example, the .NET Framework provides simple properties to adjust visual attributes
associated with forms. In some cases the underlying operating system does not support changing these
attributes directly, and in these cases the .NET Framework automatically recreates the forms. This is
one of many ways in which the .NET Framework integrates the developer interface, making coding
simpler and more consistent.
Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user's
computer. This means that binary or natively executing code can access some of the resources on the
user's system (such as GUI elements and limited file access) without being able to access or
compromise other resources. Because of code access security, many applications that once needed to
be installed on a user's system can now be safely deployed through the Web. Your applications can
implement the features of a local application while being deployed like a Web page.

ASP.NET

Server Application Development

 Server-side applications in the managed world are implemented through runtime hosts.
Unmanaged applications host the common language runtime, which allows your custom managed
code to control the behavior of the server. This model provides you with all the features of the
common language runtime and class library while gaining the performance and scalability of the host
server.
The following illustration shows a basic network schema with managed code running in
different server environments. Servers such as IIS and SQL Server can perform standard operations
while your application logic executes through the managed code.

SERVER-SIDE MANAGED CODE

ASP.NET is the hosting environment that enables developers to use the .NET Framework to
target Web-based applications. However, ASP.NET is more than just a runtime host; it is a complete
architecture for developing Web sites and Internet-distributed objects using managed code. Both Web
Forms and XML Web services use IIS and ASP.NET as the publishing mechanism for applications,
and both have a collection of supporting classes in the .NET Framework.
XML Web services, an important evolution in Web-based technology, are distributed, server-
side application components similar to common Web sites. However, unlike Web-based applications,
XML Web services components have no UI and are not targeted for browsers such as Internet
Explorer and Netscape Navigator. Instead, XML Web services consist of reusable software
components designed to be consumed by other applications, such as traditional client applications,
Web-based applications, or even other XML Web services. As a result, XML Web services
technology is rapidly moving application development and deployment into the highly distributed
environment of the Internet.
If you have used earlier versions of ASP technology, you will immediately notice the
improvements that ASP.NET and Web Forms offers. For example, you can develop Web Forms pages
in any language that supports the .NET Framework. In addition, your code no longer needs to share
the same file with your HTTP text (although it can continue to do so if you prefer). Web Forms pages
execute in native machine language because, like any other managed application, they take full
advantage of the runtime. In contrast, unmanaged ASP pages are always scripted and interpreted.
ASP.NET pages are faster, more functional, and easier to develop than unmanaged ASP pages
because they interact with the runtime like any managed application.
The .NET Framework also provides a collection of classes and tools to aid in development
and consumption of XML Web services applications. XML Web services are built on standards such
as SOAP (a remote procedure-call protocol), XML (an extensible data format), and WSDL ( the Web
Services Description Language). The .NET Framework is built on these standards to promote
interoperability with non-Microsoft solutions.
 For example, the Web Services Description Language tool included with the .NET
Framework SDK can query an XML Web service published on the Web, parse its WSDL description,
and produce C# or Visual Basic source code that your application can use to become a client of the
XML Web service. The source code can create classes derived from classes in the class library that
handle all the underlying communication using SOAP and XML parsing. Although you can use the
class library to consume XML Web services directly, the Web Services Description Language tool
and the other tools contained in the SDK facilitate your development efforts with the .NET
Framework.
If you develop and publish your own XML Web service, the .NET Framework provides a set
of classes that conform to all the underlying communication standards, such as SOAP, WSDL, and
XML. Using those classes enables you to focus on the logic of your service, without concerning
yourself with the communications infrastructure required by distributed software development.
Finally, like Web Forms pages in the managed environment, your XML Web service will run with the
speed of native machine language using the scalable communication of IIS.

ACTIVE SERVER PAGES.NET

ASP.NET is a programming framework built on the common language runtime that can be
used on a server to build powerful Web applications. ASP.NET offers several important advantages
over previous Web development models:
 Enhanced Performance. ASP.NET is compiled common language runtime code running on
the server. Unlike its interpreted predecessors, ASP.NET can take advantage of early binding,
just-in-time compilation, native optimization, and caching services right out of the box. This
amounts to dramatically better performance before you ever write a line of code.
 World-Class Tool Support. The ASP.NET framework is complemented by a rich toolbox
and designer in the Visual Studio integrated development environment. WYSIWYG editing, drag-
and-drop server controls, and automatic deployment are just a few of the features this powerful
tool provides.
 Power and Flexibility. Because ASP.NET is based on the common language runtime, the
power and flexibility of that entire platform is available to Web application developers. The .NET
Framework class library, Messaging, and Data Access solutions are all seamlessly accessible from
the Web. ASP.NET is also language-independent, so you can choose the language that best
applies to your application or partition your application across many languages. Further, common
language runtime interoperability guarantees that your existing investment in COM-based
development is preserved when migrating to ASP.NET.
 Simplicity. ASP.NET makes it easy to perform common tasks, from simple form submission
and client authentication to deployment and site configuration. For example, the ASP.NET page
 framework allows you to build user interfaces that cleanly separate application logic from
presentation code and to handle events in a simple, Visual Basic - like forms processing model.
Additionally, the common language runtime simplifies development, with managed code services
such as automatic reference counting and garbage collection.
 Manageability. ASP.NET employs a text-based, hierarchical configuration system, which
simplifies applying settings to your server environment and Web applications. Because
configuration information is stored as plain text, new settings may be applied without the aid of
local administration tools. This "zero local administration" philosophy extends to deploying
ASP.NET Framework applications as well. An ASP.NET Framework application is deployed to a
server simply by copying the necessary files to the server. No server restart is required, even to
deploy or replace running compiled code.
 Scalability and Availability. ASP.NET has been designed with scalability in mind, with
features specifically tailored to improve performance in clustered and multiprocessor
environments. Further, processes are closely monitored and managed by the ASP.NET runtime,
so that if one misbehaves (leaks, deadlocks), a new process can be created in its place, which
helps keep your application constantly available to handle requests.
 Customizability and Extensibility. ASP.NET delivers a well-factored architecture that
allows developers to "plug-in" their code at the appropriate level. In fact, it is possible to extend
or replace any subcomponent of the ASP.NET runtime with your own custom-written component.
Implementing custom authentication or state services has never been easier.
 Security. With built in Windows authentication and per-application configuration, you can be
assured that your applications are secure.

LANGUAGE SUPPORT
The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual
Basic, and JScript.

WHAT IS ASP.NET WEB FORMS?

The ASP.NET Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.
Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with existing
pages), the ASP.NET Web Forms framework has been specifically designed to address a number of
key deficiencies in the previous model. In particular, it provides:
 The ability to create and use reusable UI controls that can encapsulate common functionality and
thus reduce the amount of code that a page developer has to write.
 The ability for developers to cleanly structure their page logic in an orderly fashion (not
"spaghetti code").
 The ability for development tools to provide strong WYSIWYG design support for pages
(existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an .aspx file name extension. They can be
deployed throughout an IIS virtual root directory tree. When a browser client requests .aspx resources,
the ASP.NET runtime parses and compiles the target file into a .NET Framework class. This class can
then be used to dynamically process incoming requests. (Note that the .aspx file is compiled only the
first time it is accessed; the compiled type instance is then reused across multiple requests).
An ASP.NET page can be created simply by taking an existing HTML file and changing its
file name extension to .aspx (no modification of code is required). For example, the following sample
demonstrates a simple HTML page that collects a user's name and category preference and then
performs a form postback to the originating page when a button is clicked:
ASP.NET provides syntax compatibility with existing ASP pages. This includes support for <
% %> code render blocks that can be intermixed with HTML content within an .aspx file. These code
blocks execute in a top-down manner at page render time.

CODE-BEHIND WEB FORMS

ASP.NET supports two methods of authoring dynamic pages. The first is the method shown
in the preceding samples, where the page code is physically declared within the originating .aspx file.
An alternative approach--known as the code-behind method--enables the page code to be more
cleanly separated from the HTML content into an entirely separate file.

INTRODUCTION TO ASP.NET SERVER CONTROLS

In addition to (or instead of) using <% %> code blocks to program dynamic content,
ASP.NET page developers can use ASP.NET server controls to program Web pages. Server controls
are declared within an .aspx file using custom tags or intrinsic HTML tags that contain a
runat="server" attributes value. Intrinsic HTML tags are handled by one of the controls in the
System.Web.UI.HtmlControls namespace. Any tag that doesn't explicitly map to one of the controls
is assigned the type of System.Web.UI.HtmlControls.HtmlGenericControl.
Server controls automatically maintain any client-entered values between round trips to the
server. This control state is not stored on the server (it is instead stored within an <input
type="hidden"> form field that is round-tripped between requests). Note also that no client-side
script is required.
 In addition to supporting standard HTML input controls, ASP.NET enables developers to
utilize richer custom controls on their pages. For example, the following sample demonstrates how the
<asp:adrotator> control can be used to dynamically display rotating ads on a page.
1. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI.
2. ASP.NET Web Forms pages can target any browser client (there are no script library or cookie
requirements).
3. ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages.
4. ASP.NET server controls provide an easy way to encapsulate common functionality.
5. ASP.NET ships with 45 built-in server controls. Developers can also use controls built by third
parties.
6. ASP.NET server controls can automatically project both uplevel and downlevel HTML.
7. ASP.NET templates provide an easy way to customize the look and feel of list server controls.
8. ASP.NET validation controls provide an easy way to do declarative client or server data
validation.

C#.NET

ADO.NET OVERVIEW

ADO.NET is an evolution of the ADO data access model that directly addresses user
requirements for developing scalable applications. It was designed specifically for the web with
scalability, statelessness, and XML in mind.
ADO.NET uses some ADO objects, such as the Connection and Command objects, and also
introduces new objects. Key new ADO.NET objects include the DataSet, DataReader, and
DataAdapter.

The important distinction between this evolved stage of ADO.NET and previous data
architectures is that there exists an object -- the DataSet -- that is separate and distinct from any data
stores. Because of that, the DataSet functions as a standalone entity. You can think of the DataSet as
an always disconnected recordset that knows nothing about the source or destination of the data it
contains. Inside a DataSet, much like in a database, there are tables, columns, relationships,
constraints, views, and so forth.

A DataAdapter is the object that connects to the database to fill the DataSet. Then, it
connects back to the database to update the data there, based on operations performed while the
DataSet held the data. In the past, data processing has been primarily connection-based. Now, in an
effort to make multi-tiered apps more efficient, data processing is turning to a message-based
approach that revolves around chunks of information. At the center of this approach is the
DataAdapter, which provides a bridge to retrieve and save data between a DataSet and its source
data store. It accomplishes this by means of requests to the appropriate SQL commands made against
the data store.
The XML-based DataSet object provides a consistent programming model that works with
all models of data storage: flat, relational, and hierarchical. It does this by having no 'knowledge' of
the source of its data, and by representing the data that it holds as collections and data types. No
matter what the source of the data within the DataSet is, it is manipulated through the same set of
standard APIs exposed through the DataSet and its subordinate objects.
While the DataSet has no knowledge of the source of its data, the managed provider has detailed and
specific information. The role of the managed provider is to connect, fill, and persist the DataSet to
and from data stores. The OLE DB and SQL Server .NET Data Providers (System.Data.OleDb and
System.Data.SqlClient) that are part of the .Net Framework provide four basic objects: the
Command, Connection, DataReader and DataAdapter. In the remaining sections of this document,
we'll walk through each part of the DataSet and the OLE DB/SQL Server .NET Data Providers
explaining what they are, and how to program against them.
The following sections will introduce you to some objects that have evolved, and some that are new.
These objects are:

 Connections. For connection to and managing transactions against a database.

 Commands. For issuing SQL commands against a database.
 DataReaders. For reading a forward-only stream of data records from a SQL Server data
source.
 DataSets. For storing, Remoting and programming against flat data, XML data and relational
data.
 DataAdapters. For pushing data into a DataSet, and reconciling data against a database.
When dealing with connections to a database, there are two different options: SQL Server
.NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider (System.Data.OleDb).
In these samples we will use the SQL Server .NET Data Provider. These are written to talk directly to
Microsoft SQL Server. The OLE DB .NET Data Provider is used to talk to any OLE DB provider (as
it uses OLE DB underneath).

Connections:

Connections are used to 'talk to' databases, and are represented by provider-specific classes
such as SqlConnection. Commands travel over connections and resultsets are returned in the form of
streams which can be read by a DataReader object, or pushed into a DataSet object.
Commands:
Commands contain the information that is submitted to a database, and are represented by
provider-specific classes such as SqlCommand. A command can be a stored procedure call, an
UPDATE statement, or a statement that returns results. You can also use input and output parameters,
and return values as part of your command syntax. The example below shows how to issue an
INSERT statement against the Northwind database.

DataReaders:
The DataReader object is somewhat synonymous with a read-only/forward-only cursor over data.
The DataReader API supports flat as well as hierarchical data. A DataReader object is returned after
executing a command against a database. The format of the returned DataReader object is different
from a recordset. For example, you might use the DataReader to show the results of a search list in a
web page.

DATASETS AND DATAADAPTERS:

DataSets
The DataSet object is similar to the ADO Recordset object, but more powerful, and with one other
important distinction: the DataSet is always disconnected. The DataSet object represents a cache of
data, with database-like structures such as tables, columns, relationships, and constraints. However,
though a DataSet can and does behave much like a database, it is important to remember that
DataSet objects do not interact directly with databases, or other source data. This allows the
developer to work with a programming model that is always consistent, regardless of where the
source data resides. Data coming from a database, an XML file, from code, or user input can all be
placed into DataSet objects. Then, as changes are made to the DataSet they can be tracked and
verified before updating the source data. The GetChanges method of the DataSet object actually
creates a second DatSet that contains only the changes to the data. This DataSet is then used by a
DataAdapter (or other objects) to update the original data source.
The DataSet has many XML characteristics, including the ability to produce and consume XML data
and XML schemas. XML schemas can be used to describe schemas interchanged via WebServices. In
fact, a DataSet with a schema can actually be compiled for type safety and statement completion.

DATAADAPTERS (OLEDB/SQL)

The DataAdapter object works as a bridge between the DataSet and the source data. Using
the provider-specific SqlDataAdapter (along with its associated SqlCommand and SqlConnection)
can increase overall performance when working with a Microsoft SQL Server databases. For other
OLE DB-supported databases, you would use the OleDbDataAdapter object and its associated
OleDbCommand and OleDbConnection objects.
The DataAdapter object uses commands to update the data source after changes have been made
to the DataSet. Using the Fill method of the DataAdapter calls the SELECT command; using the
Update method calls the INSERT, UPDATE or DELETE command for each changed row. You can
explicitly set these commands in order to control the statements used at runtime to resolve changes,
including the use of stored procedures. For ad-hoc scenarios, a CommandBuilder object can generate
these at run-time based upon a select statement. However, this run-time generation requires an extra
round-trip to the server in order to gather required metadata, so explicitly providing the INSERT,
UPDATE, and DELETE commands at design time will result in better run-time performance.
1. ADO.NET is the next evolution of ADO for the .Net Framework.
2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two new objects,
the DataSet and DataAdapter, are provided for these scenarios.
3. ADO.NET can be used to get data from a stream, or to store data in a cache for updates.
4. There is a lot more information about ADO.NET in the documentation.
5. Remember, you can execute a command directly against the database in order to do inserts,
updates, and deletes. You don't need to first put data into a DataSet in order to insert, update, or
delete it.
6. Also, you can use a DataSet to bind to the data, move through the data, and navigate data
relationships

Back End:
SQL SERVER

A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include dBase, paradox,
IMS, SQL Server and SQL Server. These systems allow users to create, update and extract
information from their database.

A database is a structured collection of data. Data refers to the characteristics of people,

things and events. SQL Server stores each data item in its own fields. In SQL Server, the fields
relating to a particular person, thing or event are bundled together to form a single complete unit of
data, called a record (it can also be referred to as raw or an occurrence). Each record is made up of a
number of fields. No two fields in a record can have the same field name.

During an SQL Server Database design project, the analysis of your business needs identifies
all the fields or attributes of interest. If your business needs change over time, you define any
additional fields or change the definition of existing fields.

SQL SERVER TABLES

SQL Server stores records relating to each other in a table. Different tables are created for the
various groups of information. Related tables are grouped together to form a database.

PRIMARY KEY

Every table in SQL Server has a field or a combination of fields that uniquely identifies each
record in the table. The Unique identifier is called the Primary Key, or simply the Key. The primary
key provides the means to distinguish one record from all other in a table. It allows the user and the
database system to identify, locate and refer to one particular record in the database.

RELATIONAL DATABASE

Sometimes all the information of interest to a business operation can be stored in one table.
SQL Server makes it very easy to link the data in multiple tables. Matching an employee to the
department in which they work is one example. This is what makes SQL Server a relational database
management system, or RDBMS. It stores data in two or more tables and enables you to define
relationships between the table and enables you to define relationships between the tables.

FOREIGN KEY

When a field is one table matches the primary key of another field is referred to as a foreign
key. A foreign key is a field or a group of fields in one table whose values match those of the primary
key of another table.
 TESTING

Software Testing is the process of executing a program or system with the intent
of finding errors. Software testing is any activity aimed at evaluating an
attribute or capability of a program or system and determining that it meets its
required results.

Types of Testing Done

The development process involves various types of testing. Each test type
addresses a specific testing requirement. The most common types of testing
involved in the development process are:
• Unit Test.
• System Test
• Functional Test
• Integration Test

Unit Testing
The first test in the development process is the unit test. The source code
is normally divided into modules, which in turn are divided into smaller units
called units. These units have specific behavior. The test done on these units of
code is called unit test. Unit test depends upon the language on which the
project is developed. Unit tests ensure that each unique path of the project
performs accurately to the documented specifications and contains clearly
defined inputs and expected results. Functional and reliability testing in an
Engineering environment. Producing tests for the behavior of components
(nodes and vertices of a product to ensure their correct behavior prior to system
integration.
System Testing
Several modules constitute a project. If the project is long-term project,
several developers write the modules. Once all the modules are integrated,
several errors may arise. The testing done at this stage is called system test.
System testing ensures that the entire integrated software system meets
requirements. It tests a configuration to ensure known and predictable results.
System testing is based on process descriptions and flows, emphasizing pre-
driven process links and integration points. Testing a specific hardware/software
installation. This is typically performed on a COTS (commercial off the shelf)
system or any other system comprised of disparate parts where custom
configurations and/or unique installations are the norm.

Functional Testing

Functional test can be defined as testing two or more modules together

with the intent of finding defects, demonstrating that defects are not present,
verifying that the module performs its intended functions as stated in the
specification and establishing confidence that a program does what it is
supposed to do.

Integration Testing

Integration testing is an additional step that is used when different sub-

systems are being developed simultaneously by independent developers. It
verifies that the parameters passed between sub-systems are being handled
correctly. Testing in which modules are combined and tested as a group.
Modules are typically code modules, individual applications, source and
destination applications on a network, etc. Integration Testing follows unit
testing and precedes system testing. Testing after the product is code complete.
Betas are often widely distributed or even distributed to the public at large in
hopes that they will buy the final product when it is released.