ONLINE INSURANCE SALES SYSTEM FOR TWO

WHEELERS
Dissertation Submitted to the

BHARATHIDASAN UNIVERSITY,
Thiruchirapalli.
In partial fulfillment for the award of the degree of
BACHELOR OF COMPUTER APPLICATION

Submitted by
S.CHINNADHURAI
CB15S 241760
Under the Guidance of
Mrs.C.SARANYA M.phil.

DEPARTMENT OF COMPUTER SCIENCE

MASS COLLEGE OF ARTS & SCIENCE

Chennai salai,Kumbakonam-612501

APRIL-2018

DEPARTMENT OF COMPUTER SCIENCE

 MASS COLLEGE OF ARTS & SCIENCE
Chennai salai,Kumbakonam-612501

APRIL-2018

BONAFIDE CERTIFICATE

This is to certify that the project entitled “ONLINE INSURANCE SALES

SYSTEM FOR TWO WHEELERS” is a Bonafide record of the project work
done by S.CHINNADHURAI, CB15S241760 submitted to Bharathidasan
University, Thiruchirapalli in partial fulfillment of the requirement for the
award of degree of BACHELOR OF COMPUTER APPLICATION during
the academic year 2015-2018

Head of the Department Internal Guide

Examiners

1……………….

2……………….

ACKNOWLEDGEMENT
I express my sincere thanks to our chairman Mr.S.Vijayakumar, for providing the
wonderful atmosphere to complete my course successfully
 I express my respectful and sincere thanks to Dr.K.SARAVANAN, Principal,
MASS COLLEGE OF ARTS & SCIENCE, Kumbakonam, who provided the wonderful
atmosphere, which enabled me to do not only this project work but also all academic
activities.

I proudly thank Mr.S.PARTHIBAN, HEAD, and Department of computer

Science for providing a great opportunity to pursue this project study.

I am extremely grateful to my guide Prof. C. SARANYA for his constant

encouragement valuable suggestions and kind advice throughout the course of my study.

I also express my sincere thanks to all staff members in the department of Master of
computer Application and computer science for their well support throughout my project
work.

Finally I am also grateful to my parents and friends who inspired me all through the
days of my project work. Last but not least; I thank everybody who was a source of help to
complete this project work effectively.

S.CHINNADHURAI
 CHAPTER
NO CONTENT PAGE NO

1. ABSTRACT

1.1 INTRODUCTION

1.2 SYSTEM REQUIREMENT

2. SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

2.2 PROPOSED SYSTEM

2.3 ABOUT SOFTWARE

3. SYSTEM STUDY

3.1 PROJECT DESCRIPTION

4. SYSTEM DESIGN

4.1 DATAFLOW DIAGRAM

4.2 TABLE

5. SYSTEM IMPLEMENTATION

5.1 CODING

5.2 SCREEN SHOTS

6. SYSTEM TESTING

7. CONCLUSION

8. BIBLIOGRAPHY

ONLINE INSURANCE SALES SYSTEM FOR TWO WHEELERS

ABSTRACT
 The “Online Insurance Sales System for Two Wheelers” project has been
developing with the intention to provide the feasible environment to process the insurance for
two wheelers in the web based applications.

The primary objective of this project is to help the vehicle owners they are to sell their
used vehicle through online and automatic existing system that enables the any
other person to buy their desired vehicles models through online. It also maintains the sales
information and generates the sales reports.

This software is run in any operating system. Because this software used ASP.NET as
a front end and SQL SERVER as a back end. ASP.NET is also a server side scripting
language and also SQL SERVER is also one of the open source database. So the cost of
implementing this software is very less when compared with other existing system.

The existing systems are to sales new vehicles but this project is to sale the used
vehicles. The existing systems are having lack of information sharing, lack of Client-Server
technology and inconsistent maintenance of database. So there is no centralized control,
proper maintenance and user interactivity. So the proposed system is developed to overcome
from all these disadvantages.

There are seven modules are used in this system for various operations and three
database tables are used to store various information about the customer, vehicles and sales
report.
1. Introduction
The primary objective of this project is to help the vehicle owners they are to sell their
used vehicle through online and automatic existing system that enables the any
other person to buy their desired vehicles models through online. It also maintains the
sales information and generates the sales reports This software is run in any operating
system. Because this software used ASP.NET as a front end and SQL SERVER as a back
end. ASP.NET is also a server side scripting language and also SQL SERVER is also one
of the open source database. So the cost of implementing this software is very less when
compared with other existing systemAll the vehicles models of a particular brand are
displayed depending on the customer selection. The customer who is registered only can
buy the desired vehicles and it also provides facilities to pay their bill through online. The
bill amount will be taken from the credit card of the customer and this also helps the
dealer to maintain the invoice reports and allows adding, The Booking vehicle modules is
customer to book the vehicle in purchase any existing vehicle from vehicles gallery.
These booking are stored in administrative database and managed. After the booking the
vehicle gallery is modified, the booking vehicle details are deleted from the vehicle
gallery.
 1. 2 SYSTEM CONFIGURATION

Hardware Specification:

Processor : Intel Pentium IV

Speed : 2.4 GHz

RAM : 512

Hard Disk : 80GB

CD ROM Drive : 5 MB

Monitor :Monitor resolution 1024 with minimum 256 colors

Mouse : Logitech Mouse

Keyboard :104 Keys(HCL)

Software Specification:

Operating System : Windows XP

Front End : Microsoft.NET

Back End : SQL-SERVER 2005

Web Server : Internet Information Server

Web Browser : Internet Explorer

Documentation : Microsoft Word 2007

 2. SYSTEM ANALYSIS
System study is the understanding of the existing system to develop a convenient
system for working. System study includes the recognition of the needs. Only after
identifying the needs, we are able to build efficient system for usage.

Existing System:

Advantages and disadvantages of Existing System

 Lack of Client-Server Technology

 High Reliability

 The Low Cost implementation

 Inconsistent Maintenance of Database

 Lack of information sharing

Proposed System:

The proposed system is designed to utilize Client-Server Technology. The

proposed system is designed with the multi-user application, administrator can
have the permission to update database and others can only view the
information, Proposed System modules are

 Login Form

 Registration

 Displaying Vehicles

 Customer Searching vehicles

 Customer buying details

 Adding records in vehicle database

 Deleting records in vehicle database

 Updating records in vehicle database

 Management the Payment options

 Sales Details
 2.1ABOUT SOFTWARE

NET FRAMEWORK

Microsoft® .NET Framework version 1.1 the .NET Framework is an integral

Windows component that supports building and running the next generation of applications
and XML Web services. The key components of the .NET Framework are the common
language runtime and the .NET Framework class library, which includes ADO.NET,
VB.NET, and Windows Forms. The .NET Framework provides a managed execution
environment simplified development and deployment, and integration with a wide variety of
programming languages. For a brief introduction to the architecture of the .NET Framework

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 fulfill 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 minimizes software deployment
and versioning conflicts.
 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. You can think of the runtime is an agent that manages code at
execution time, providing core services such as memory management, thread management,
and remoting while also enforcing strict type safety 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 use interface (GUI) applications based on the latest innovations
provided by VB.NET, such as Web Forms and XML Web Services.

The following illustration shows the relationship of the common language runtime
and the class library to your applications and to the overall system. The illustration also
shows how managed code operates within a larger architecture.

NET FRAMEWORK IN CONTEXT

.NET Framework in context

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 feature 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.
 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.

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.

Server-side managed code

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 offer. 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.

COMMON LANGUAGE RUNTIME

Compilers and tools expose the runtime's functionality and enable you to write code
that benefits from this managed execution environment. Code that you develop with a
language compiler that targets the runtime is called managed code; it benefits from features
such as cross-language integration, cross-language exception handling, enhanced security,
versioning and deployment support, a simplified model for component interaction, and
debugging and profiling services.

To enable the runtime to provide services to managed code, language compilers must emit
metadata that describes the types, members, and references in your code. Metadata is stored
with the code; every loadable common language runtime portable executable (PE) file
contains metadata. The runtime uses metadata to locate and load classes, lay out instances in
memory, resolve method invocations, generate native code, enforce security, and set run-time
context boundaries.

The runtime automatically handles object layout and manages references to objects, releasing
them when they are no longer being used. Objects whose lifetimes are managed in this way
are called managed data. Garbage collection eliminates memory leaks as well as some other
common programming errors. If your code is managed, you can use managed data,
unmanaged data, or both managed and unmanaged data in your .NET Framework application.
Because language compilers supply their own types, such as primitive types, you might not
always know (or need to know) whether your data is being managed.

The common language runtime makes it easy to design components and applications whose
objects interact across languages. Objects written in different languages can communicate
with each other, and their behaviors can be tightly integrated. For example, you can define a
class and then use a different language to derive a class from your original class or call a
method on the original class. You can also pass an instance of a class to a method of a class
written in a different language. This cross-language integration is possible because language
compilers and tools that target the runtime use a common type system defined by the runtime,
and they follow the runtime's rules for defining new types, as well as for creating, using,
persisting, and binding to types.

As part of their metadata, all managed components carry information about the
components and resources they were built against. The runtime uses this information to
ensure that your component or application has the specified versions of everything it needs,
which makes your code less likely to break because of some unmet dependency. Registration
information and state data are no longer stored in the registry where they can be difficult to
establish and maintain. Rather, information about the types you define (and their
dependencies) is stored with the code as metadata, making the tasks of component replication
and removal much less complicated.

Language compilers and tools expose the runtime's functionality in ways that are intended
to be useful and intuitive to developers. This means that some features of the runtime might
be more noticeable in one environment than in another. How you experience the runtime
depends on which language compilers or tools you use. For example, if you are a Visual
Basic developer, you might notice that with the common language runtime, the Visual Basic
language has more object-oriented features than before. Following are some benefits of the
runtime.
  Performance improvements.
 The ability to easily use components developed in other languages.
 Extensible types provided by a class library.
 New language features such as inheritance, interfaces, and overloading for object-
oriented programming; support for explicit free threading that allows creation of
multithreaded, scalable applications; support for structured exception handling and
custom attributes.

If you use Microsoft® Visual C++® .NET, you can write managed code using the
Managed Extensions for C++, which provide the benefits of a managed execution
environment as well as access to powerful capabilities and expressive data types that you are
familiar with. Additional runtime features include:

 Cross- language integration, especially cross- language inheritance.

 Garbage collection, which manages object lifetime so that reference counting is
unnecessary.
 Self-describing objects, which make using Interface Definition Language (IDL)
unnecessary.

ADO.NET ARCHITECTURE

ADO.NET Architecture
REMOTING OR MARSHALING DATA BETWEEN TIERS AND CLIENTS

The design of the Dataset enables you to easily transport data to clients over the Web
using XML Web services, as well as allowing you to marshal data between .NET components
using .NET Remoting services. You can also remote a strongly typed Dataset in this fashion.
For an overview of XML Web services..

An overview of remoting services can be found in the .NET Remoting Overview.

Note that Data Table objects can also be used with remoting services, but cannot be
transported via an XML Web service.

.NET FRAMEWORK DATA PROVIDERS

A .NET Framework data provider is used for connecting to a database, executing

commands, and retrieving results. Those results are either processed directly, or placed in an
ADO.NET Dataset in order to be exposed to the user in an ad-hoc manner, combined with
data from multiple sources, or remoted between tiers. The .NET Framework data provider is
designed to be lightweight, creating a minimal layer between the data source and your code,
increasing performance without sacrificing functionality.

The following table outlines the four core objects that make up a .NET Framework
data provider.

Object Description

Connection Establishes a connection to a specific data

source.

Command Executes a command against a data source.

Exposes Parameters and can execute within
the scope of a Transaction from a
Connection.

Data Reader Reads a forward-only, read-only stream of

data from a data source.

Data Adapter Populates a Dataset and resolves updates with

the data source.
 The .NET Framework includes the .NET Framework Data Provider for SQL Server
(for Microsoft SQL Server version 7.0 or later), the .NET Framework Data Provider for OLE
DB, and the .NET Framework Data Provider for ODBC.

Note   The .NET Framework Data Provider for ODBC is not included in the .NET
Framework version 1.0. If you require the .NET Framework Data Provider for ODBC and are
using the .NET Framework version 1.0, you can download the .NET Framework Data
Provider for ODBC at http://msdn.microsoft.com/downloads. The namespace for the
downloaded .NET Framework Data Provider for ODBC is Microsoft.Data.Odbc.

THE .NET FRAMEWORK DATA PROVIDER FOR SQL SERVER

The .NET Framework Data Provider for SQL Server uses its own protocol to
communicate with SQL Server. It is lightweight and performs well because it is optimized to
access a SQL Server directly without adding an OLE DB or Open Database Connectivity
(ODBC) layer. The following illustration contrasts the .NET Framework Data Provider for
SQL Server with the .NET Framework Data Provider for OLE DB. The .NET Framework
Data Provider for OLE DB communicates to an OLE DB data source through both the OLE
DB Service component, which provides connection pooling and transaction services, and the
OLE DB Provider for the data source.

Comparison of the .NET Framework Data Provider for SQL Server and the .NET
Framework Data Provider for OLE DB

Comparison of .NET Framework Data Provider for SQL Server and OLEDB

To use the .NET Framework Data Provider for SQL Server, you must have access to
Microsoft SQL Server 7.0 or later. .NET Framework Data Provider for SQL Server classes
are located in the System.Data.SqlClient namespace. For earlier versions of Microsoft SQL
Server, use the .NET Framework Data Provider for OLE DB with the SQL Server OLE DB
Provider (SQLOLEDB).
VISUAL C# LANGUAGE

Microsoft C# (pronounced C sharp) is a new programming language designed for

building a wide range of enterprise applications that run on the .NET Framework. An
evolution of Microsoft C and Microsoft C++, C# is simple, modern, type safe, and object
oriented. C# code is compiled as managed code, which means it benefits from the services of
the common language runtime. These services include language interoperability, garbage
collection, enhanced security, and improved versioning support.

C# is introduced as Visual C# in the Visual Studio .NET suite. Support for Visual C#

includes project templates, designers, property pages, code wizards, an object model, and
other features of the development environment. The library for Visual C# programming is the
.NET Framework.

C# (pronounced “See Sharp”) is a simple, modern, object-oriented, and type safe

programming language. C# has its roots in the C family of languages and will be
immediately familiar to C, C++, and Java programmers. C# is standardized by ECMA
International as the ECMA-334 standard and by ISO/IEC as the ISO/IEC 23270 standard.
Microsoft’s C# compiler for the .NET Framework is a conforming implementation of both of
these standards. C# aims to combine the high productivity of Visual Basic and the raw power
of C++.

Visual C#.NET is Microsoft’s C# development tool. It includes an interactive

development environment, visual designers for building Windows and Web applications, a
compiler, and a debugger. Visual C#.NET is part of suite of products, called Visual
Studio.NET, that also includes Visual Basic.NET, Visual C++.NET, and the Jscript scripting
language. All of these languages provide access to the Microsoft .NET Framework, which
includes a common execution engine and a rich class library. The .NET Framework defines a
“Common language Specification” (CLS), a sort of lingua franca that ensures seamless
interoperability between CLS compliant languages and class libraries. For C# developers,
this means that even though C# is a new language, it has complete access to the same rich
class libraries that are used by seasoned tools such as Visual Basic .NET and Visual C+
+.NET. C# itself does not include a class library.

C# is an object-oriented language, but C# further includes support for component-

oriented programming. Contemporary software design increasingly relies on software
components in the form of self-contained and self-describing packages of functionality. Key
to such components is that they present a programming model with properties, methods and
events; they have attributes that provide declarative information about the component; and
they incorporate their own documentation. C# provides language constructs to directly
support these concepts, making C# a very natural language in which to create and use
software components.

Several C# features aid in the construction of robust and durable applications:

Garbage collection automatically reclaims memory occupied by unused objects; exception
handling provides a structured and extensible approach to error detection and recovery; and
the type-safe design of the language makes it impossible to have uninitialized variables, to
index arrays beyond their bounds, or to perform unchecked type casts.

C# has a unified type system. All C# types, including primitive types such as int and
double, inherit from a single root object type, Thus, all types share a set of common
operations, and values of any type can be stored, transported, and operated upon in a
consistent manner. Furthermore, C# supports both user-defined reference types and value
types, allowing dynamic allocation of objects as well as in-line storage of lightweight
structures.

To ensure that C# programs and libraries can evolve over time in a compatible
manner, much emphasis has been placed on versioning in C#’s design. Many programming
languages pay little attention to this issue, and, as a result, programs written in those
languages break more often than necessary when newer versions of dependent libraries are
introduced. Aspects of C# ’s design that were directly influenced by versioning
considerations include the separate virtual and override modifiers, the rules for method
overload resolution, and support for explicit interface member declarations.

C# 2.0 introduces several language extensions, including Generics, Anonymous

Methods, Iterators, Partial Types, and Nullable Types.

 Generics permit classes, structs, interfaces, delegates, and methods to be

parameterized by the types of data they store and manipulate. Generics are
useful because they provide stronger compile-time type checking, require
fewer explicit conversions between data types, and reduce the need for boxing
operations and run-time type checks.
 Anonymous methods allow code blocks to be written “in-line” where delegate
values are expected. Anonymous methods are similar to lambda functions in
 the Lisp programming language. C# 2.0 supports the creation of “closures”
where anonymous methods access surrounding local variables and parameters.
 Iterators are methods that incrementally compute and yield a sequence of
values. Iterators make it easy for a type to specify how for each statement will
iterate over its elements.
 Partial types allow classes, structs, and interfaces to be broken into multiple
pieces stored in different source files for easier development and maintenance.
Additionally, partial types allow separation of machine-generated and user-
written parts of types so that it is easier to augment code generated by a tool.
 Nullable types represent values that possibly are unknown. A nullable type
supports all values of its underlying type plus an additional null state. Any
value type can be the underlying type of a nullable type.

ASP.NET

The .NET framework includes tools that ease the creation of web services.
ASP.NET is the latest offering from Microsoft toward the creation of a new paradigm for
server-side scripting. The systemwill see the basics of ASP.NET, which provides a
complete framework for the development of web applications. Here the systemget
introduced into ASP.NET, the platform requirements for ASP.NET applications, and the
ASP.NET architecture. In addition, the systemget introduced to web forms of ASP.NET
applications, a new addition to ASP.NET.

ASP .NET differs in some ways from earlier versions Os ASP. ASP.NET has new
features such as better language support, a new set of controls, XML-based components, and
more secure user authentication. ASP.NET also provides increased performance by executing
ASP code.

Usually a software product undergoes many evolutionary phases. In each release

version of the software product, the software vendor fixes the bugs form previous versions
and adds new features. ASP 1.0 was released in 1996. Since then, two more versions of ASP
(2.0 AND 3.0) have been released. In various versions of ASP, new features have been
added. However, the basic methodology used for creating applications has not changed.
 ASP.NET provides a unique approach toward web application development, so one
might say that ASP.NET has stared a new revolution in the world of web application
development. ASP.NET is based on the Microsoft.NET framework. The .NET framework.
The .NET framework is based on the common language runtime (CLR). There fore, it
imparts all of the CLR benefits to ASP.NET applications. These CLR benefits include
automatic memory management, support for multiple languages, secure user authentication,
and ease in configuration, and ease in deployment.

BENEFITS OF ASP.NET

Support for various programming language ASP.NET provides better programming-

language support than ASP. It uses the new ADO.NET earlier versions of ASP support only
scripting language such as VBScript and Jscript. Using this scripting language, the system
can write applications used to perform server-side processing, but this has two major
drawbacks. First, scripting language is interpreted and not complied. Therefore, the errors can
only be checked at runtime. This affects the performance of web applications. Second,
scripting language is not strongly typed. The scripting languages do not have a built –in set of
predefined data types. This requires developers to cast the existing objects of the language to
their expected data type. Thus, these objects can be validated only at runtime. This validation
leads to a low performance of web applications. ASP.NET continues to support scripting
languages, but it supports complete Visual Basic for server-side programming ASP.NET also
provides support for c# (pronounced c sharp) and C++.

CROSS – LANGUAGE DEVELOPMENT

ASP.NET provides flexibility to extend created in one language to another language. For
example, if the system has an object in C++, ASP.NET enables us to extend this object in
Visual Basic.
ASP.NET PAGE SYNTAX

DIRECTIVES
<% @ page language =”VB” […] %>

Code Declaration Blocks

<script run at=”server” […]>

[ lines of code]

</script>

CODE RENDER BLOCKS

<%

[inline code or expressions]

%>

HTML Control Syntax

<HTML element runat=”server” [attribute(s)]>

</HTML element>

CUSTOM CONTROL SYNTAX

CUSTOM SERVER CONTROLS

<ASP: Textbox id=”My Tbi” run at=”server”>

SERVER CONTROL PROPERTY

<ASP: Textbox maxlength=”80” run at=”server”>
SUB PROPERTY

<ASP: Label font-size=”14” run at=”server”>

SERVER CONTROL EVEN BINDING

<ASP: Button On Click=”My Click” run at=”server”>

DATA BINDING EXPRESSION

< asp: label

Text=’<%# data binding expression %>’

Run at =”server”/>

SERVER-SIDE OBJECTS TAGS

<object id=”id” run at=”server”

Identifier=”idName”/>

SERVER-SIDE INCLUDE DIRECTIVES

<!-#include pathtype=filename -->

SERVER-SIDE COMMENTS

%-- comment block -- %>

An application in ASP.NET consists of files, pages, modules, and executable code that reside
in one virtual directory and its subdirectories. Application state is stored in global variables
for a given ASP.NET application. For that Reason developers have to follow some
implements rules .Variables for storing application state occupy system resources.

A global variable has to be locked and unlocked to prevent problems with concurrent

access.

WEB FORMS SERVER CONTROLS

The term server controls always means Web Forms server controls,
because they are specially designed to work with Web Forms.
SERVER CONTROL FAMILIES

Web Forms provide different server control families

 HTML server controls

 ASP.NET server controls
 Validation controls
 User controls
 Mobile controls

DATA BINDING

The systemcan bind Web Forms control properties to any data in a data store. This so-
called data binding gives us nearly complete control over how data moves to the page and
back again to the data store.

PAGE CLASS

When a page is loaded, the ASP.NET runtime generates and instantiates a

page class. This object forms a collection of our separate components (like visual
elements and business logic). So all (visual and code) elements are accessible
through this object.

HTML SERVER CONTROLS

The system can convert simple HTML elements to HTML server controls, let
the ASP.NET engine create an instance on the server, and now they are
programmable on the server. The conversion is done by simply adding attributes
to the HTML tag. The attributes runat=server informs the framework to create a
server-side instance of the control. If the system additionally assigns an ID, the
system can reference the control in our code.
 For example, the system can use the HTMLAnchor control to program
against the HTML <a> tag to dynamically generate the H Ref values, or use
HtmlTable (HTML <table>) to dynamically create tables and their content.
ASP.NET SERVER CONTROLS

ASP.NET server controls are abstract controls. There is no one-to-one

mapping to HTML server controls. But ASP.NET comes with a rich set of controls.

Another feature is the typed object model. This gives us the potential for
type-safe programming. Server controls can automatically detect what browser
the system is using and generate the proper version of HTML output.

BUTTON
This is way to enable the user to finish editing a form. A Button enforces the
submitting of the page, and the systemcan additionally raise events like the Click event.

TEXTBOX
A Textbox is an input box where the user can enter information like numbers, text, or
dates formatted as single line, multilane, or password. This control raises a Text Changed
event when the focus “leaves” the control.

VALIDATION CONTROLS
Another group of server controls are validation controls. These can be used to check
the user’s entries. Validation can be processed on the client and on the server.

Validation on the client side can be performed using a client script. In that case, the
user will be confronted with immediate feedback-without a roundtrip to the server. Server-
side validation in addition provides, for example, security against users bypassing client-side
validation.

ASP.NET PROVIDES THE FOLLOWING TYPES OF VALIDATION

Required entry- the field must be filled in by the user. Comparison to a value- the
entered value is checked against another value of another field, a database, or a constant
value by using comparison operators. Range checking – the user’s entry is checked to see
whether it resides between given boundaries. Pattern matching- a regular expression is
defined that the entered value must match. User’s defined- implement our own validation
logic. When the validation fails, an error message is generated and sent back to the client
browser. This can be done in several ways. For example, all error messages related to a
specific transaction could be collected and presented to the user in summary.

SQL SERVER INTRODUCTION

SQL stands for Structured Query Language. SQL is used to communicate with a
database. According to ANSI (American National Standards Institute), it is the standard
language for relational database management systems.

SQL statements are used to perform tasks such as update data on a database, or
retrieve data from a database. Some common relational database management systems that
the SQL are: Oracle, Sybase, Microsoft SQL Server, Access, Ingress, etc. Although most
database systems use SQL, most of them also have their own additional proprietary
extensions that are usually only used on their system.

The standard SQL commands such as “Select”, “Insert”, “Update”, ”Delete”,

”Create”, and “Drop” can be used to accomplish almost everything that one needs to do with
a database. This tutorial will provide you with the instruction on the basics of each of these
commands as well as allow you to put them to practice using the SQL Interpreter.

TABLE BASICS

A relational database system contains one of more objects called tables. The data or
information for the database is stored in these tables. Tables are uniquely identified by their
names and are comprised of columns and rows. Columns contain the column name, data
type, and any other attributes for the column. Rows contain the records or data for the
columns.

SELECTING DATA

The select statement is used to query the database and relatives selected data that
match the criteria that you specify. Here is the format of a simple select statement.

Select “column1” [,”column2”, etc] from “table name”

[Where “condition”]; [ ] =optional

The column names that follow the select keyword determine which columns will be
returned in the results. The system can select as many column names that you’d like, or you
can use a “*” to select all columns. The table name that follows the keyword from specifies
the table that will be queried to retrieve the desired results.

The where clause (optional) specifies which data values or rows will be
returned or displayed, based on the criteria described after the keyword where.

Conditional selections used in the where clause

= Equal

> Greater than

< Less than

>= Greater than or equal

<= Less than or equal

< > Not equal to

LIKE

The LIKE pattern matching operator can also be used in the conditional selection of
the where clause. Like is a very powerful operator that allows you to select only rows that are
“Like” what you specify. The percent sign “%” can be used as a wild card to match any
possible character that might appear before or after the characters specified.

For example

Select first, last, city

From empinfo

Where first LIKE ‘Er%’;

This SQL statement will match any first names that start with ‘Er’. Strings must be in
single quotes. Or the systemcan specify
 Select first, last

From empinfo where last LIKE ‘%s’;

This statement will match any last names that end in‘s’.

Select * from user

Where first = ‘Erie’;

This will only select rows where the first name equals ‘Erie’ exactly.

CREATING TABLES

The create tables statement is used to create a new table. Here is the format of a
simple create table statement.
Create table “table name”

(“column1” “data type”,

“column2” “data type”,

“column3” “data type”);

FORMAT FOR CREATING TABLE BY USING OPTIONAL CONSTRAINTS

Create table “table name”

(“column1” “data type”

[Constraints],

“column2” “data type”

[Constraints],

“column3” “data type”

[Constraints],

[ ] = optional)
 To create a new table, enter the keywords create table followed by the table name,
followed by an open parenthesis , followed by the first column name, followed by the data
type for that column, followed by any optional constraints, any followed by a closing
parenthesis before the beginning table and a closing parenthesis after the end of the last
column definition. Make sure you separate each column definition with a comma. All SQL
statements should end with a “;”.

The table and column names must start with a letter and can be followed by letters,
numbers, or underscore – not to exceed a total of 30 characters in length. Do not use any
SQL reserved keywords as names for tables or column names (such as “select”, “create”,
“insert”, etc).Data types specify what the types of data can be for that particular column. If a
column called “Last Name” is to be used to hold names, then that particular column should
have a “VarChar” (variable-length character) data type.

COMMON DATA TYPES

Char(size) Fixed-length character string. Size is specified in parenthesis.

Max 255 bytes.

VarChar (size) Variable-length character string. Max size is specified in

parenthesis.

Number (size) Number value with a max number of columns digits specified in
parenthesis.

Date Date value

Number(size, d) Number value with a maximum number of digits of “size” total,

with a maximum number of “d” digits to the right of the decimal

Number(size, d) Number value with a maximum number of digits of “size” total,

with a maximum number of “d” digits to the right of the decimal.

What are constraints? When tables are created, it is common for one or more
columns to have constraints associated with them. A constraint is basically a rule associated
with a column that the data entered into that column must follow. For example, a ‘unique”
constraints specifies that no two records can have the same value in a particular column. They
must all be unique.

The other two most particular constraints are “not null” which specifies that a column
can’t be left blank, and “primary key”. A “primary key” constraint defines a unique
identification of each record (or row) in a table. Constraints can be entered in this SQL
interpreter, however, they are not supported in this Intro to SQL tutorial & interpreter. They
will be covered and supported in the future release of the Advanced SQL tutorial- that is, if
“response” is good.

INSERTING INTO A TABLE

The insert statement is used to insert or add a row of data into the table. To insert
records into a table, enter the key words insert into followed by the table name, followed by
an open parenthesis, followed by a list of column names separated by commas, followed by a
closing parenthesis, followed by the keyword values, followed by the list of values enclosed
in parenthesis. The values that you enter will be held in the rows and they will match up with
the column names that you specify. Strings should be enclosed in single quotes, and numbers
should not.

Insert into “table name”

(First column...last column)

Values (first value...last value);

UPDATING RECORDS
The update statement is used to update or change records that match specified criteria.
This is accomplished by carefully constructing a where clause.

Update “table name”

Set “column name”= “new value”

[ ,”next column” = “newvalue2”...]

Where “column name” OPERATOR “value”

[and/or “column” OPERATOR “value”];

DELETING RECORDS
The delete statement is used to delete records or rows from the table.

Delete from “table name”

Where “column name”

OPERATOR “value”

[and/or “column”

OPERATOR “value”]

To delete an entire record/row from a table, enter “delete form” followed by the table
name, followed by the where clause which contains the conditions to delete. If you leave off
the where clause, all records will be deleted.

DROP A TABLE
The drop table command is used to delete a table and all rows in the table. To delete
an entire table including all of its rows, issue the drop table command followed by the table
name. Drop table is different from deleting all of the records in the table. Deleting all of the
records in the table leaves the table including column and constraint information. Dropping
the table removes the table definition as well as all of its rows.

Drop table “table name”

TABLE JOINS

All of the queries up until this point have been useful with the exception of one major
limitation- that is, you’ve been selecting from only one table are a time with your SELECT
statement. It is time to introduce you to one of the most beneficial features of SQL &
relational database system – the

Joins allow you to link data from two or more tables together into a single query result
– from one single SELECT statement. A “join” can be recognized in a SQL SELECT
statement if it has more than one table after the FROM keyword.
 3.SYSTEM STUDY

Project Description:
The Online Insurance System for Two Wheelers is an web application that allows
companies to develop better and secured software products and client matrix system. These
application includes

 About as

 Login

 Vehicles gallery

 Vehicles search

 Insurance Booking vehicles

 Payment options

 Reports

About as:

The project title is “ Used Vehicles Sales Management System”. This project is a web
based application that has been developed for vehicles owners who willing to sell their
vehicle through online. All the vehicles models of a particular brand are displayed depending
on the customer selection. The customer who is registered only can buy the desired vehicles
and it also provides facilities to pay their bill through online. The bill amount will be taken
from the credit card of the customer and this also helps the dealer to maintain the invoice
reports and allows adding, deleting and modifying the various vehicle models’ details in the
database.

Login:

This module is developed with the motto of high security and hashed data saving
options for the clients, administration and vehicle owners. The proper authentification
mechanisms have been followed to maintain the integrity of the user’s information that is
stored in the central database system.

Vehicles gallery:

This modules is developed for customer, the main usage is customer can view all the
models of existing vehicles. All the vehicles models of a particular brand are displayed
depending on the customer selection. The customer who is registered only can buy the
desired vehicles. These model have the information of each and every vehicles and that are
displayed for example vehicle name, price, model, color, previous owner, image and etc.
Vehicle Search:

The vehicle Search module has one form, that form require some information from
customer. Customer to fill the form in details of desired vehicle for example vehicle name,
vehicle ID, previous owner, mobile number and etc. Suppose if the information are exist in
vehicle gallery database then to booking that vehicle.

Booking vehicles:

The Booking vehicle modules is customer to book the vehicle in purchase any
existing vehicle from vehicles gallery. These booking are stored in administrative database
and managed. After the booking the vehicle gallery is modified, the booking vehicle details
are deleted from the vehicle gallery.

Payment Option:

The payment option is very important module of this project because the customer
who is registered only can buy the desired vehicles and it also provides facilities to pay their
bill through online. The bill amount will be taken from the credit card of the customer and
this also helps the dealer to maintain the invoice reports and allows adding, deleting and
modifying the various vehicle models’ details in the database.

Reports:

This system provides the option to take the reports according to the client’s requests.
We can provides reports in the following options such as Ms-Excel, PPT and Ms-Word
document formats.
 4. DATA FLOW DIAGRAM

ADMIN LOGIN DATABASE

LOGIN

CLIENT LOGIN Insurance vehicle

registry
 ARCHITECTURE DESIGN

USER

Login

IS Valid?

Vehicles gallery Administrator

Show Items Purchase Details

Add Items Delete Items Update Items Sales Details

4.2 TABLE DESIGN

Db design:-
 5. SYSTEM IMPLEMENTATION

5.1 CODING
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
usingSystem.Web.UI.WebControls;
usingSystem.Data.SqlClient;
usingSystem.Data;

publicpartialclassreg : System.Web.UI.Page
{
SqlConnection con;
SqlCommandcmd;
string s;
protectedvoidPage_Load(object sender, EventArgs e)
{

protectedvoid Button1_Click(object sender, EventArgs e)

{
string s;
if(RadioButton1.Checked==true)
{
s= "male";
}
else
{
s= "female";
}

con = newSqlConnection("Data Source=.\\SQLEXPRESS;Initial Catalog=health;Integrated

Security=True");
con.Open();
s = "insert into reg values('"
+TextBox1.Text+"','"+TextBox2.Text+"','"+TextBox3.Text+"','"+s+"','"+TextBox4.Text+"',
'"+TextBox5.Text+"','"+TextBox6.Text+"')";
cmd = newSqlCommand(s, con);
cmd.ExecuteNonQuery();
con.Close();
}
}

using System;
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
usingSystem.Web.UI.WebControls;

publicpartialclassadmin : System.Web.UI.Page
{
protectedvoidPage_Load(object sender, EventArgs e)
{

protectedvoid Button1_Click(object sender, EventArgs e)

{
if(TextBox2.Text=="Admin"&& TextBox3.Text=="123")
{
Response.Redirect("adddiseaset.aspx");
}
}
}

using System;
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
usingSystem.Web.UI.WebControls;
usingSystem.Data.SqlClient;
usingSystem.Data;
publicpartialclassreport : System.Web.UI.Page
{
SqlConnection con;
SqlCommandcmd;
string s;
protectedvoidPage_Load(object sender, EventArgs e)
{

protectedvoid Button1_Click(object sender, EventArgs e)

{
con = newSqlConnection("Data Source=.\\SQLEXPRESS;Initial
Catalog=health;Integrated Security=True");
con.Open();
s = "select *from reg";
cmd = newSqlCommand(s, con);
SqlDataAdapter da = newSqlDataAdapter(cmd);
DataTabledt = newDataTable();
da.Fill(dt);
GridView1.DataSource = dt;
GridView1.DataBind();
con.Close();
5.2 SREEN SHOTS
 6. TESTING
Testing is vital to the success of the system. System testing makes a logical
assumption that if all parts of the system are correct, the global has been achieved. System
testing is vital but time consuming activity. During the programming testing to the
specifications lay down by the designer.

As per seven laws of computing “Any non-trivial program contains at least one bug.
There are no trivial programs. “The proper choice of test data is an important as the test itself
so live data has been collected for testing.

 Software testing is a critical element of software quality assurance and represents the
ultimate review of specification laid down by the designer.

 Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding the objectives of testing can be
given as

Testing objectives

 Testing is a process of executing a program with the intent of finding errors.

 A good test has high probability for finding an undiscovered error.

 A successful test is one that a covers as yet undiscovered problem.

Unit Testing:

The modules of the system are tested as individual in uniting testing; each unit has
definite input and output parameters. Each and every unit is tested by applying different
parameters. The unit test always white-box oriented and the step can conduct in parallel for
multiple modules. Unit testing modules are said to be error-free. Unit testing is essential for
verifications of the code produced during the coding phase and hence the goal is to test the
internal login of the modules. This testing is carried out during the programming stage.

System Testing:

Software testing is an important element of software quality assurance and represents

the ultimate review of specification design and coding. The increasing visibility of software
as a system element and the cost of associating with a software as a system element and the
cost of associating with software failure and motivation force for well planned through
testing. In the system testing, “Software Information System” is tested as a whole
intercommunication, among the individual units and functions of the complete system are all
tested.
System testing is actually a series of different tests whose primary purpose is to fully exercise
the computer-based system. Although each test has a different purpose, all work should
verify that all system elements have been properly integrated and perform attracted function.

Validation Testing:

Validation testing is the step where requirements established as apart of the software
requirement analysis, are validated against the software already been constructed. This test
provides the final assurance that the software meets all the functional and behavioral and
performance requirements and the errors, which are uncovered during the testing.

Acceptance Testing:

This test was performed with the users of the system and made sure that it performed
as they expected. It was verified that all functionality required by the user have been satisfied.
So for, the system has been found defect free and is working well.

User Interface Testing:

An interactive interface is a system that is dominated by interaction between the system and
external sources such as humans, devices or other programs. The external agents are
independently from the computational part of communications protocol between and the
external agents, the syntax of possible interactions, the presentation of the output, and the
flow of control with in the system, the ease of understanding and user interface, performance
and error handling. The Dynamic model dominates interactive interfaces. Objects in the
model represent interaction elements, such as input and output tokens and presentation
formats. The functional model describes which application functions are executed in response
to input event sequences, but the internal structure of the function is usually unimportant to
the behavior of the interface.
 7. CONCLUSION

Summary of Project

This project entitled “Online Insurance System for Two Wheelers” has been completed
successfully with the designs that are made to bring solutions to the undertaken problem. The
solution is brought using ASP.NET. As the product is tested, its performance is studied. The
product uses SQL Server as back end.

New enhancement

This system has been developed for the used vehicle dealers who want to sell their vehicle
through online. It also provides facilities that make as possible the customer to pay their bill
through online.

This system has been made in Client-Server Technology. So the system is centralized control.
The user sends request to the Server and then the Server immediately response to the client
machine. So the system has very fast and effective information sharing through this
technology and also the system has effective maintenance of database.
8. REFERENCE
1. Centers for Medicare & Medicaid Services: Diagnosis and Procedure Codes and Their
Abbreviated Titles. 2004. Version 22, effective October 1. Retrieved August 28,
2006, http://www.cdc.gov/nchs/ datawh.htm#International%20Classification.
2. Chang, R. E., C. L. Lai. 2005. Use of diagnosis-based risk adjustment models to
predict individual health care expenditure under the national health insurance system
in Taiwan. J. Formosan Med. Assoc. 104 883–890. Cheng, D., R. Kannan, S.
Vempala, G. Wang. 2008.
3. A divide-andmerge methodology for clustering. Proc. ACM Sympos. Principles of
Database Systems. Forthcoming. Classification Rule with Unbiased Interaction
Selection and Estimation. Binaries retrieved July 20, 2007,
http://www.stat.wisc.edu/loh/ cruise.html. Cumming, R., D. Knutson, B. Cameron, B.
Derrick. 2002. A comparative analysis of claims-based methods of health risk
assessment for commercial populations. Retrieved August 28, 2006, http://www.soa.
org/ccm/cms-service/stream/asset?asset_id = 9215098&g11n.
4. Dans, P. 1993. Looking for answers in all the wrong places. Ann. Internal Med. 119
855–857. Dove, H., I. Duncan, A. Robb. 2003. A prediction model for targeting low-
cost, high-risk members of managed care organizations. Amer. J. Managed Care 9
381–389.

Dunn, D. L., A. Rosenblatt, D. A. Taira, E. Latimer, J. Bertko, T. Stoiber, P. Braun, S. Busch.

2002. A comparative analysis of methods of health risk assessment. Society of Actuaries
Monograph M-HB96-1. Retrieved August 28, 2006,