You are on page 1of 52

Insurance Policy Maintenance System

SYNOPSIS
Life insurance is a contract for payment of a sum of money to the person assured
on the happening of the event insured against. Usually the contract provides for the
payment of an amount on the date of maturity or at specific dates at periodic intervals.
Life insurance is universally acknowledged to be an institution, which eliminates 'risk'
substitution.
The act was amended in 1950, making far-reaching changes such as requirement
of equity capital for companies, carrying on life insurance business, ceilings on
shareholdings such companies, stricter control on investment of life insurance companies,
submission of periodical returns relating to investments and such other information to the
Controller as he may call for, appointments of administrators for mismanaged companies,
ceilings on expenses of management and agency commission, incorporation of the
Insurance Association of India and formation of councils and committees thereof.

Insurance Policy Maintenance System

PROJECT DESCRIPTION
The project Insurance Policy Maintenance System has been developed using
Asp .net as front end tool and SQL server as back end as its back end process.
In 1938, with a view to protecting the interest of insuring public, earlier
legislation was consolidated and amended by Insurance Act, 1938 with comprehensive
provisions for detailed and effective control over the activities of insurers. In order to
administer the aforesaid legislation, an insurance wing was established and attached first
with the Ministry of Commerce and then Ministry of Finance. This ministry was
administratively responsible for policy matters pertaining to insurance.
The acturial and operational matters relating to the insurance industry were
looked after by an attached office in Shimla, headed first by Actuary to the Government
of India, then by Superintendent of Insurance and finally by the Controller of Insurance.
The act was amended in 1950, making far-reaching changes such as requirement of
equity capital for companies, carrying on life insurance business, ceilings on
shareholdings

such companies, stricter control on investment of life insurance

companies, submission of periodical returns relating to investments and such other


information to the Controller as he may call for, appointments of administrators for
mismanaged companies, ceilings on expenses of management and agency commission,
incorporation of the Insurance Association of India and formation of councils and
committees thereof.

By 1956, 154 Indian insurers, 16 non-Indian insurers and 75 provident societies


were carrying on life insurance business in India. Life insurance business was confirmed
mainly to cities and better off segments of the society.

Insurance Policy Maintenance System


Modules:
Admin
Add Insurance
View Customers
View Payment
Customer
View Insurance
Monthly Payment

Module Description
Admin
Add Insurance
In this module the admin has all the rights to add the insurance types, total
insurance amount, and monthly amount and stored into the database.
View Customers
In this module the admin view all the customers that have register to claim
the insurance and all details are retrieved from the database.
View Payment
All the payment details of the customers are viewed in this module and the
monthly payment are also listed.

Insurance Policy Maintenance System


Customer
View Insurance
After registering the details the customer is provide the login and then the
customers can view all the insurances available.
Monthly Payment
In this module the customers can pay their amount once every month
according to the amount that is provided.

Insurance Policy Maintenance System

DATA FLOW DIAGRAM

Add Insurance
Details

Add Insurance

Stored

Admin
View Customers

Database

View Customers

Details

View Books
Details

Customer

Insurance
Register

Types

Select Insurance
Monthly
Payment

View
Insurance

Insurance Policy Maintenance System

DATABASE DESIGN
Customer Registration:

Column Name
Customer id

DataType
integer

Desciption
Comtomer id

Customer name

Varchar

Customer name

Contact number

Numeric

Contact number

E-mail

Varchar

E-mail

Address

Varchar

Address

varchar

Insurance type

Insurance type
Insurance Amount
Total period

Float
Numeric

Amount per month

Float

Register date

Varchar

Insurance Amount
Total period
Amount per month
Register date

Insurance Policy Maintenance System


Monthly Payment:

Column Name

Customer id

DataType

integer

Desciption

Comtomer id

Customer name

Varchar

Customer name

Insurance type

varchar

Insurance type

Insurance Amount

Monthly amount

Date

Float

Insurance Amount

Float

Monthly amount

Varchar

Date

Insurance
7

Insurance Policy Maintenance System

Column Name

DataType

Customer id

integer

Desciption

Comtomer id

Customer name

Varchar

Customer name

Insurance type

varchar

Insurance type

Insurance Amount

Monthly amount

Duration

Float

Insurance Amount

Float

Monthly amount

Varchar

Duration

SOFTWARE TOOLS USED

Insurance Policy Maintenance System

Operating System

Windows XP Professional

Environment

Visual Studio .Net 2005

.Net Framework

Version 2.0

Language

C#.Net

Web Technology

Active Server Pages.Net

Web Server

Internet information Server 5.0

Back End

Sql Server 2000

Insurance Policy Maintenance System

HARDWARE USED

Processor

Pentium IV

RAM

512MB

Monitor size

17SVGA

Extra Device

CD-ROM 52x

Operating System

Windows XP

Keyboard

104 standards Keyboard

10

Insurance Policy Maintenance System

SOFTWARE TOOLS DESCRIPTION


Windows XP is an operating system that was produced by Microsoft for use on
personal computers, including home and business desktops, laptops, and media centers. It
was first released in August 2001, and is the most popular version of Windows, based on
installed user base. The name "XP" is short for "eXPerience."
Windows XP was the successor to both Windows 2000 and, and was the first
consumer-oriented operating system produced by Microsoft to be built on the and.
Windows XP was released for retail sale on October 25, 2001, and over 400 million
copies were in use in January 2006, according to an estimate in that month by an analyst.
It was succeeded by, which was released to volume license customers on November 8,
2006 and worldwide to the general public on January 30, 2007. Direct and retail sales of
Windows XP ceased on June 30, 2008. Microsoft continued to sell Windows XP through
their System Builders (smaller OEMs who sell assembled computers) program until
January 31, 2009. XP may continue to be available as these sources run through their
inventory or by purchasing Windows 7 Ultimate, Windows 7 Pro, Windows Vista
Ultimate or Windows Vista Business, and then to Windows XP.
The most common editions of the operating system were Windows XP Home Edition,
which was targeted at home users, and Windows XP Professional, which offered
additional features such as support for and , and was targeted at , business and enterprise
clients has additional multimedia features enhancing the ability to record and watch TV
shows, view DVD movies, and listen to music. Was designed to run stylus applications
built using the platform.
Windows XP was eventually released for two additional architectures, for ()
processors and for. There is also, a component version of the Windows XP Professional,
and editions for specific markets such as Windows XP Starter Edition. By mid 2009, a
manufacturer revealed the first Windows XP powered cellular telephone.

11

Insurance Policy Maintenance System


Users can further customize these settings. Some effects, such as (transparency and
fading), are handled entirely by many newer video cards. However, if the video card is
not capable of hardware alpha blending, performance can be substantially hurt, and
Microsoft recommends the feature should be turned off manually. Windows XP added the
ability for Windows to use "Visual Styles" to change the user interface. However, visual
styles must be cryptographically signed by Microsoft to run. Is the name of the new
visual style that ships with Windows XP, and is enabled by default for machines with
more than 64 of? Luna refers only to one particular visual style, not to all of the new user
interface features of Windows XP as a whole. Some users "patch" the uxtheme.dll file
that restricts the ability to use visual styles, created by the general public or the user, on
Windows XP.
New and updated features
Main article:
Windows XP introduced several new features to the Windows line, including:

graphics subsystem

and improvements

A number of new features in

Faster start-up, logon and logoff and sequences.

The ability to discard a newer in favor of the previous one (known as driver
rollback), should a driver upgrade not produce desirable results.

A new, arguably more user-friendly interface, including the framework for


developing for the desktop environment

which allows a user to save the current state and open applications of their
desktop and allow another user to log on without losing that information

12

Insurance Policy Maintenance System

The font rendering mechanism, which is designed to improve text readability on


(LCD) and similar monitors

Editions
The two major editions are Windows XP Home Edition, designed for home users,
and Windows XP Professional, designed for business and power-users. XP Professional
contains advanced features that the average home user would not use. However, these
features are not necessarily missing from XP Home. They are simply disabled, but are
there and can become functional. These releases were made available at retail outlets that
sell computer software, and were preinstalled on computers sold by major computer
manufacturers. As of mid-2008, both editions continue to be sold. A third edition, called
Windows XP Media Center Edition was introduced in 2002 and was updated every year
until 2006 to incorporate new digital media, broadcast television and capabilities. Unlike
the Home and Professional edition, it was never made available for retail purchase, and
was typically either sold through channels, or was preinstalled on computers that were
typically marketed as "media center PCs".
Editions for specific markets
Is a lower-cost edition of Windows XP available in Thailand, Indonesia,
Philippines, Russia, India, Colombia, Brazil, Argentina, Peru, Bolivia, Chile, Mexico,
Ecuador, Uruguay and Venezuela? It is similar to Windows XP Home, but is limited to
low-end hardware, can only run 3 programs at a time, and has some other features either
removed or disabled by default. Each country's edition is also customized for that
country, including desktop backgrounds of popular locations, help features for those who
may not speak English, and other default settings designed for easier use than typical
Windows XP installations. The Malaysian version, for example, contains a desktop
background of the skyline.

13

Insurance Policy Maintenance System


That same year, Microsoft also released two additional editions of Windows XP
Home Edition directed towards subscription-based and pay-as-you-go pricing models.
These editions, released as part of Microsofts initiative, are used in conjunction with a
hardware component to enforce time limitations on the usage of Windows. Its target
market is emerging economies such as Brazil and Vietnam.
Languages
Windows XP was available in many languages. In addition, packs and translating
the user interface were also available for certain languages.
ATMs and Vendors
(ATM) vendors, and have all adopted Microsoft Windows XP as their migration
path from. Wincor Nixdorf, who has been pushing for standardization for many years,
began shipping ATMs with Windows when they first arrived on the scene.
Diebold initially shipped XP Home Edition exclusively, but, following extensive
pressure from customer banks to support a common operating system, switched to
support XP Professional to match their primary competitor, NCR Corporation and Wincor
Nixdorf.
Vending machines run a modified version of XP designed for the full screen of the
Vending Touch screen and the DVD vending itself.
Service packs
Microsoft occasionally releases for its Windows operating systems to fix
problems and add features. Each service pack is a superset of all previous service packs
and patches so that only the latest service pack needs to be installed, and also includes
new revisions. However if you still have the earliest version of Windows XP on Retail
CD (without any service packs included), you will need to install SP1a or SP2, before
SP3 can be installed. Older service packs need not be manually removed before

14

Insurance Policy Maintenance System


application of the most recent one. Windows Update "normally" takes care of
automatically removing unnecessary files.
The service pack details below only apply to the 32-bit editions. Windows XP
Professional x64 Edition was based on Service Pack 1 and claimed to be "SP1" in system
properties from the initial release. It is updated by the same service packs and hot fixes as
the x64 edition of Windows Server 2003

FRONT END TOOLS


ABOUT ASP.NET
INTRODUCTION OF VISUAL STUDIO:
In 2002, Visual Studio took the biggest leap in innovation since it was released,
with the introduction of Visual Basic .NET (as it was renamed). After more than a
decade, Visual Basic was overdue for a major overhaul. But .NET goes beyond an
overhaul. It changes almost every aspect of software development. From integrating
Internet functionality to creating object-oriented frameworks, Visual Basic .NET
challenged traditional VB developers to learn dramatic new concepts and techniques.

2005 brings us an enhanced Visual Basic language (renamed this time Visual
Basic 2005). New features have been added that cement this languages position as a true
object-oriented language. With Visual Basic 2005, it is still going to be a challenge for the
traditional VB6 developers to learn, but it is an easy road and books like this are here to
help you on your path.

First, its necessary to learn the differences between Visual Basic 2005 and the
older versions. In some cases, the same functionality is implemented in a different way.
This was not done arbitrarilythere are good reasons for the changes. But you must be
prepared to unlearn old habits and form new ones.

15

Insurance Policy Maintenance System


Next, you must be open to the new concepts. Full object orientation, new component
techniques, new visual tools for both local and Internet interfacesall of these and more
must become part of your skill

THE IMPORTANCE OF VISUAL BASIC


Early in the adoption cycle of .NET, Microsofts new language, C#, got the lions
share of attention. But as .NET adoption has increased, Visual Basics continuing
importance has also been apparent. Microsoft has publicly stated that they consider
Visual Basic the language of choice for applications where developer productivity is one
of the highest priorities.
Future development of Visual Basic is emphasizing capabilities that enable access
to the whole expanse of the .NET Framework in the most productive way, while C#
development is emphasizing the experience of writing code. That fits the traditional role
of Visual Basic as the language developers use in the real world to create business
applications as quickly as possible.

This difference is more than academic. One of the most important advantages of
the .NET Framework is that it allows applications to be written with dramatically less
code. In the world of business applications, the goal is to concentrate on writing business
logic and to eliminate routine coding tasks as much as possible. The value in this new
world is not in churning out lots of codeit is in writing robust, useful applications with
as little code as possible.

An Overview of the .NET Framework

16

Insurance Policy Maintenance System


First and foremost, .NET is a framework that covers all the layers of software
development above the operating system level. It provides the richest level of integration
among presentation technologies, component Technologies and data technologies ever
seen on a Microsoft, or perhaps any, platform. Second, the entire architecture has been
created to make it as easy to develop Internet applications as it is to develop for the
desktop.

The .NET Framework actually wraps the operating system, insulating software
developed with .NET from most operating system specifics such as file handling and
memory allocation. This prepares for a possible future in which the software developed
for .NET is portable to a wide variety of hardware and operating system foundations.
VS.NET supports Windows 2003, Windows XP, and all versions of Windows
2000. Programs created for .NET can also run under Windows NT, Windows 98, and
Windows Me, though VS.NET does not run on these systems. Note that in some cases
certain service packs are required to run .NET.

The framework starts all the way down at the memory management and
component loading level and goes all the way up to multiple ways of rendering user and
program interfaces. In between, there are layers that provide just about any system-level
capability that a developer would need.

Microsoft .NET
At the base is the common language runtime, often abbreviated to CLR. This is
the heart of the .NET Framework it is the engine that drives key functionality. It includes,
for example, a common system of data types. These common types, plus a standard
interface convention, make cross-language inheritance possible. In addition to allocation

17

Insurance Policy Maintenance System


and management of memory, the CLR also does reference tracking for objects and
handles garbage collection.

The middle layer includes the next generation of standard system Services such as
classes that manage data and Extensible Markup Language (XML). These services are
brought under control of the Framework, making them universally available and making
their usage consistent across languages.

The top layer includes user and program interfaces. Windows Forms is a new and
more advanced way to do standard Win32 screens (often referred to as smart clients).
Web Forms provides a new Web-based user interface. Perhaps the most revolutionary is
Web Services, which provide a mechanism for programs to communicate over the
Internet, using SOAP. Web Services provide an analog of COM and DCOM for object
brokering and interfacing, but based on Internet technologies so that allowance is made
even for integration to non-Microsoft platforms.

FEATURES OF ASP.NET
ASP.NET is the next version of Active Server Pages (ASP); it is a unified Web
development platform that provides the services necessary for developers to build
enterprise-class Web applications. While ASP.NET is largely syntax compatible, it also
provides a new programming model and infrastructure for more secure, scalable, and
stable applications.
ASP.NET is a compiled, NET-based environment, we can author applications in
any .NET compatible language, including Visual Basic .NET, C#, and JScript .NET.
Additionally, the entire .NET Framework is available to any ASP.NET application.
Developers can easily access the benefits of these technologies, which include the

18

Insurance Policy Maintenance System


managed common language runtime environment (CLR), type safety, inheritance, and so
on.
ASP.NET has been designed to work seamlessly with WYSIWYG HTML editors
and other programming tools, including Microsoft Visual Studio .NET. Not only does this
make Web development easier, but it also provides all the benefits that these tools have to
offer, including a GUI that developers can use to drop server controls onto a Web page
and fully integrated debugging support.

Developers can choose from the following two features when creating an
ASP.NET application. Web Forms and Web services, or combine these in any way they
see fit. Each is supported by the same infrastructure that allows you to use authentication
schemes; cache frequently used data, or customizes your application's configuration, to
name only a few possibilities.
Web Forms allows us to build powerful forms-based Web pages. When building
these pages, we can use ASP.NET server controls to create common UI elements, and
program them for common tasks. These controls allow us to rapidly build a Web Form
out of reusable built-in or custom components, simplifying the code of a page.
ASP.NET takes advantage of performance enhancements found in the .NET
Framework and common language runtime. Additionally, it has been designed to offer
significant performance improvements over ASP and other Web development platforms.
All ASP.NET code is compiled, rather than interpreted, which allows early binding,
strong typing, and just-in-time (JIT) compilation to native code, to name only a few of its
benefits. ASP.NET is also easily factorable, meaning that developers can remove modules
(a session module, for instance) that are not relevant to the application they are
developing.
ASP.NET provides extensive caching services (both built-in services and caching
APIs). ASP.NET also ships with performance counters that developers and system
19

Insurance Policy Maintenance System


administrators can monitor to test new applications and gather metrics on existing
applications.
Writing custom debug statements to your Web page can help immensely in
troubleshooting your application's code. However, it can cause embarrassment if it is not
removed. The problem is that removing the debug statements from your pages when your
application is ready to be ported to a production server can require significant effort.

ASP.NET offers the Trace Context class, which allows us to write custom debug
statements to our pages as we develop them. They appear only when you have enabled
tracing for a page or entire application. Enabling tracing also appends details about a
request to the page, or, if you so specify, to a custom trace viewer that is stored in the root
directory of your application.
The .NET Framework and ASP.NET provide default authorization and
authentication schemes for Web applications. We can easily remove, add to, or replace
these schemes, depending upon the needs of our application.
ASP.NET configuration settings are stored in XML-based files, which are human
readable and writable. Each of our applications can have a distinct configuration file and
we can extend the configuration scheme to suit our requirements.

THE .NET FRAMEWORK


The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet.
OBJECTIVES OF .NET FRAMEWORK:
1. To provide a consistent object-oriented programming environment whether
object codes is stored and executed locally on Internet-distributed, or executed remotely.

20

Insurance Policy Maintenance System


2. To provide a code-execution environment to minimizes software deployment
and guarantees safe execution of code.
3. Eliminates the performance problems.
There are different types of application, such as Windows-based applications and
Web-based applications. To make communication on distributed environment to ensure
that code be accessed by the .NET Framework can integrate with any other code.

THE COMMON LANGUAGE RUNTIME (CLR):


The common language runtime is the foundation of the .NET Framework. It manages
code at execution time, providing important services such as memory management,
thread management, and removing and also ensures more security and robustness. 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 .NET FRAME WORK CLASS LIBRARY
It is a comprehensive, object-oriented collection of reusable types used to develop
applications ranging from traditional command-line or graphical user interface (GUI)
applications to applications based on the latest innovations provided by ASP.NET, such as
Web Forms and XML Web services.
The .NET Framework can be hosted by unmanaged components that load the
common language runtime into their processes and initiate the execution of managed
code, thereby creating a software environment that can exploit both managed .
Internet Explorer is an example of an unmanaged application that hosts the
runtime (in the form of a MIME type extension). Using Internet Explorer to host the
runtime to enables embeds managed components or Windows Forms controls in HTML
documents.

21

Insurance Policy Maintenance System


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 are all
run on CLR.
Security.
Robustness.
Productivity.
Performance.

SECURITY:
The runtime enforces code access security. The security features of the runtime
thus enable legitimate Internet-deployed software to be exceptionally featuring rich. With
regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin to perform file-access
operations, registry-access operations, or other sensitive functions.

ROBUSTNESS:
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 managed environment of the runtime
eliminates many common software issues.
PRODUCTIVITY:
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.

22

Insurance Policy Maintenance System

PERFORMANCE:
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. Finally, the runtime can be
hosted by high-performance, server-side applications, such as Microsoft SQL Server
and Internet Information Services (IIS).

ADO.NET
As you develop applications using ADO.NET, you will have different
requirements for working with data. You might never need to directly edit an XML file
containing data - but it is very useful to understand the data architecture in ADO.NET.
ADO.NET offers several advantages over previous versions of ADO:
Interoperability
Maintainability
Programmability
Performance Scalability

INTEROPERABILITY:
ADO.NET applications can take advantage of the flexibility and broad acceptance
of XML. Because XML is the format for transmitting datasets across the network, any
component that can read the XML format can process data. The receiving component
need not be an ADO.NET component.

23

Insurance Policy Maintenance System


The transmitting component can simply transmit the dataset to its destination
without regard to how the receiving component is implemented. The destination
component might be a Visual Studio application or any other application implemented
with any tool whatsoever.
The only requirement is that the receiving component be able to read XML. SO,
XML was designed with exactly this kind of interoperability in mind.

MAINTAINABILITY:
In the life of a deployed system, modest changes are possible, but substantial,
Architectural changes are rarely attempted because they are so difficult. As the
performance load on a deployed application server grows, system resources can become
scarce and response time or throughput can suffer. Faced with this problem, software
architects can choose to divide the server's business-logic processing and user-interface
processing onto separate tiers on separate machines.
In effect, the application server tier is replaced with two tiers, alleviating the
shortage of system resources. If the original application is implemented in ADO.NET
using datasets, this transformation is made easier.
ADO.NET data components in Visual Studio encapsulate data access
functionality in various ways that help you program more quickly and with fewer
mistakes.
VISUAL STUDIO .NET
Visual Studio .NET is a complete set of development tools for building ASP Web
applications, XML Web services, desktop applications, and mobile applications In
addition to building high-performing desktop applications, you can use Visual Studio's
powerful component-based development tools and other technologies to simplify teambased design, development, and deployment of Enterprise solutions.

24

Insurance Policy Maintenance System


Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same
integrated development environment (IDE), which allows them to share tools and
facilitates in the creation of mixed-language solutions. In addition, these languages
leverage the functionality of the .NET Framework and simplify the development of ASP
Web applications and XML Web services.
Visual Studio supports the .NET Framework, which provides a common language
runtime and unified programming classes; ASP.NET uses these components to create
ASP Web applications and XML Web services. Also it includes MSDN Library, which
contains all the documentation for these development tools.
XML WEB SERVICES
XML Web services are applications that can receive the requested data using
XML over HTTP. XML Web services are not tied to a particular component technology
or object-calling convention but it can be accessed by any language, component model,
or operating system. In Visual Studio .NET, you can quickly create and include XML
Web services using Visual Basic, Visual C#, JScript, Managed Extensions for C++, or
ATL Server.
XML SUPPORT
Extensible Markup Language (XML) provides a method for describing structured
data. XML is a subset of SGML that is optimized for delivery over the Web. The World
Wide Web Consortium (W3C) defines XML standards so that structured data will be
uniform and independent of applications. Visual Studio .NET fully supports XML,
providing the XML Designer to make it easier to edit XML and create XML schemas.
COMMON LANGUAE SPEGIFICATION (CLS)
Visual Basic.NET is also compliant with CLS (Common Language Specification)
and supports structured exception handling. CLS is set of rules and constructs that are
supported by the CLR (Common Language Runtime). CLR is the runtime environment
provided by the .NET Framework; it manages the execution of the code and also makes
the development process easier by providing services.

25

Insurance Policy Maintenance System


Visual Basic.NET is a CLS-compliant language. Any objects, classes, or
components that created in Visual Basic.NET can be used in any other CLS-compliant
language. In addition, we can use objects, classes, and components created in other CLScompliant languages in Visual Basic.NET.

IMPLEMENTATION INHERITANCE
Visual Basic.NET supports implementation inheritance. This means that, while
creating applications in Visual Basic.NET, we can drive from another class, which is
know as the base class that derived class inherits all the methods and properties of the
base class. In the derived class, we can either use the existing code of the base class or
override the existing code. Therefore, with help of the implementation inheritance, code
can be reused.

CONSTRUCTORS AND DESTRUCTORS


Constructors are used to initialize objects, whereas destructors are used to destroy
them. In other words, destructors are used to release the resources allocated to the object.
In Visual Basic.NET the sub finalize procedure is available. The sub finalize procedure is
used to complete the tasks that must be performed when an object is destroyed. The sub
finalize procedure is called automatically when an object is destroyed. In addition, the
sub finalize procedure can be called only from the class it belongs to or from derived
classes.

GARBAGE COLLECTION
26

Insurance Policy Maintenance System


Garbage Collection is another new feature in Visual Basic.NET. The .NET
Framework monitors allocated resources, such as objects and variables. In addition,
the .NET Framework automatically releases memory for reuse by destroying objects that
are no longer in use. In Visual Basic.NET, the garbage collector checks for the objects
that are not currently in use by applications. When the garbage collector comes across an
object that is marked for garbage collection, it releases the memory occupied by the
object.

BACK END TOOLS

SQL STRUCTURED QUERY LANGUAGE

FEATURES OF SQL SERVER 2000


The OLAP Services feature available in SQL Server version 7.0 is now called
SQL Server 2000 Analysis Services. The term OLAP Services has been replaced with the
term Analysis Services. Analysis Services also includes a new data mining component.
The Repository component available in SQL Server version 7.0 is now called Microsoft
SQL Server 2000 Meta Data Services. References to the component now use the term
Meta Data Services. The term repository is used only in reference to the repository engine
within Meta Data Services
SQL-SERVER database consist of six type of objects,
They are,
1. TABLE
2. QUERY
3. FORM
27

Insurance Policy Maintenance System


4. REPORT
5. MACRO
Tables
In relational database systems (DBS) data are represented using tables (relations).
A query issued against the DBS also results in a table. A table has the following structure:
Column 1 Column 2 . . . Column n
..
A table is uniquely identified by its name and consists of rows that contain the
stored information, each row containing exactly one tuple (or record). A table can have
one or more columns.
A column is made up of a column name and a data type, and it describes an
attribute of the tuples. The structure of a table, also called relation schema, thus is defined
by its attributes.
The type of information to be stored in a table is defined by the data types of the
attributes at table creation time.
SQL uses the terms table, row, and column for relation, tuple, and attribute,
respectively. In this tutorial we will use the terms interchangeably.
A table can have up to 254 columns which may have different or same data types
and sets of values (domains), respectively. Possible domains are alphanumeric data
(strings), numbers and date formats. SQL offers the following basic data types:
char (n): Fixed-length character data (string), n characters long. The maximum size for
n is 255 bytes (2000 in Oracle8). Note that a string of type char is always padded on right
with blanks to full length of n. (+ can be memory consuming).
Example: char (40)

28

Insurance Policy Maintenance System


varchar2 (n): Variable-length character string. The maximum size for n is 2000 (4000 in
Oracle8). Only the bytes used for a string require storage. Example: varchar(80)
Number (o, d): Numeric data type for integers and reals. o = overall number of digits,
d = number of digits to the right of the decimal point.
Maximum values: o =38, d= 84 to +127. Examples: number (8), number (5,2)
Note that, e.g., number (5,2) cannot contain anything larger than 999.99 without resulting
in an error. Data types derived from number are int [eger], dec [imal], smallint and real.
Date: Date data type for storing date and time.
The default format for a date is: DD-MMM-YY. Examples: 13-OCT-94, 07-JAN-98
Long: Character data up to a length of 2GB. Only one long column is allowed per table.
Further properties of tables are:
The order in which tuples appear in a table is not relevant (unless a query requires an
explicit sorting).
A table has no duplicate tuples (depending on the query, however, duplicate tuples can
appear in the query result).
A database schema is a set of relation schemas. The extension of a database schema at
database run-time is called a database instance or database, for short.

VIEWS OF TABLE:
We can work with a table in two types,
1. Design View
2. Datasheet View

Design View

29

Insurance Policy Maintenance System


To build or modify the structure of a table we work in the table design view. We
can specify what kind of data will be hold.

Datasheet View
To add, edit or analyses the data itself we work in tables datasheet view mode.
QUERY:
A query is a question that has to be asked the data. Access gathers data that
answers the question from one or more table. The data that make up the answer is either
dynast (if you edit it) or a snapshot (it cannot be edited).Each time we run query, we get
latest information in the dynast. Access either displays the dynast or snapshot for us to
view or perform an action on it, such as deleting or updating.
FORMS:
A form is used to view and edit information in the database record by record .A
form displays only the information we want to see in the way we want to see it. Forms
use the familiar controls such as textboxes and checkboxes. This makes viewing and
entering data easy.
Views of Form:
We can work with forms in several primarily there are two views,
They are,
1. Design View
2. Form View
Design View
To build or modify the structure of a form, we work in forms design view. We can
add control to the form that are bound to fields in a table or query, includes textboxes,
option buttons, graphs and pictures.
Form View
The form view which display the whole design of the form.
30

Insurance Policy Maintenance System

SYSTEM TESTING
Software testing is an investigation conducted to provide stakeholders with
information about the quality of the product or service under test. Software testing also
provides an objective, independent view of the software to allow the business to
appreciate and understand the risks of software implementation. Test techniques include,
but are not limited to, the process of executing a program or application with the intent of
finding software bugs.
Software testing can also be stated as the process of validating and verifying that a
software program/application/product:

meets the business and technical requirements that guided its design and
development;

works as expected; and

Can be implemented with the same characteristics.

Unit Testing
In computer programming, unit testing is a method by which individual units of
source code are tested to determine if they are fit for use. A unit is the smallest testable
part of an application. In procedural programming a unit may be an individual function or
procedure. Unit tests are created by programmers or occasionally by white box testers.
31

Insurance Policy Maintenance System


Ideally, each test case is independent from the others: substitutes like method
stubs, mock objects, fakes and test harnesses can be used to assist testing a module in
isolation. Unit tests are typically written and run by software developers to ensure that
code meets its design and behaves as intended. Its implementation can vary from being
very manual (pencil and paper) to being formalized as part of build automation.
The goal of unit testing is to isolate each part of the program and show that the
individual parts are correct. A unit test provides a strict, written contract that the piece of
code must satisfy. As a result, it affords several benefits. Unit tests find problems early in
the development cycle.
System Testing
System testing of software or hardware is testing conducted on a complete,
integrated system to evaluate the system's compliance with its specified requirements.
System testing falls within the scope of black box testing, and as such, should require no
knowledge of the inner design of the code or logic.
As a rule, system testing takes, as its input, all of the "integrated" software
components that have successfully passed integration testing and also the software
system itself integrated with any applicable hardware system(s).

Acceptance Testing
Acceptance testing generally involves running a suite of tests on the completed
system. Each individual test, known as a case, exercises a particular operating condition
of the user's environment or feature of the system, and will result in a pass or fail, or
Boolean, outcome. There is generally no degree of success or failure. The test
environment is usually designed to be identical, or as close as possible, to the anticipated
user's environment, including extremes of such. These test cases must each be
accompanied by test case input data or a formal description of the operational activities
(or both) to be performed intended to thoroughly exercise the specific case and a formal
description of the expected results.
32

Insurance Policy Maintenance System

User Acceptance Testing (UAT) is a process to obtain confirmation that a system


meets mutually agreed-upon requirements. A Subject Matter Expert (SME), preferably
the owner or client of the object under test, provides such confirmation after trial or
review. In software development, UAT is one of the final stages of a project and often
occurs before a client or customer accepts the new system.
Users of the system perform these tests, which developers derive from the client's
contract or the user requirements specification.
Test-designers draw up formal tests and devise a range of severity levels. Ideally
the designer of the user acceptance tests should not be the creator of the formal
integration and system test cases for the same system; however in some situations this
may not be avoided.
The results of these tests give confidence to the clients as to how the system will
perform in production. There may also be legal or contractual requirements for
acceptance of the system.
Software quality assurance (SQA)
Though controversial, software testing is a part of the software quality assurance
(SQA) process. In SQA, software process specialists and auditors are concerned for the
software development process rather than just the artifacts such as documentation, code
and systems. They examine and change the software engineering process itself to reduce
the amount of faults that end up in the delivered software: the so-called defect rate.
What constitutes an "acceptable defect rate" depends on the nature of the
software; a flight simulator video game would have much higher defect tolerance than
software for an actual airplane.
Although there are close links with SQA, testing departments often exist
independently, and there may be no SQA function in some companies.

33

Insurance Policy Maintenance System


Software testing is a task intended to detect defects in software by contrasting a
computer programs expected

SOURCE CODING
Add Insurance

using
using
using
using
using
using
using
using
using
using
using
using

System;
System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;

public partial class AddInsurance : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
string Query = "insert into Insurance values('" + TextBox1.Text
+ "','" + TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text
+ "','" + TextBox5.Text + "','" + TextBox6.Text + "')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved Successfully");
}
else

34

Insurance Policy Maintenance System


{
}

Response.Write("Not Saved");

Admin Login

using
using
using
using
using
using
using
using
using
using
using
using

System;
System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;

public partial class ADminLogin : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
if (TextBox1.Text == "Admin" && TextBox2.Text == "Admin")
{
Response.Redirect("ADminPage.aspx");
}
else
{
Response.Write("Invalid Login");
}
}
}

Customer Login

using System;

35

Insurance Policy Maintenance System


using
using
using
using
using
using
using
using
using
using
using
using

System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;
System.Data.SqlClient;

public partial class CustomerLogin : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
SqlDataReader dr;
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
string Query = "select Cus_Id,Cus_Name from Cus_Reg where
Cus_Id='" + TextBox1.Text + "' and Cus_Name like '" + TextBox2.Text +
"'";
dr = _objDb.Select(Query);
if (dr.Read())
{
TextBox1.Text = dr[0].ToString();
TextBox2.Text = dr[1].ToString();
Response.Redirect("CustomerPage.apsx");
}
else
{
Response.Write("Invalid Login");
}
}
}

Customer Registration

using
using
using
using
using
using
using
using

System;
System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;

36

Insurance Policy Maintenance System


using
using
using
using

System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;

public partial class CustomerReg : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
string Query = "insert into Cus_Reg values('" + TextBox1.Text +
"','" + TextBox2.Text + "','" + TextBox3.Text + "','" + TextBox4.Text +
"','" + TextBox5.Text + "','" + TextBox6.Text + "','" + TextBox7.Text +
"','" + TextBox8.Text + "','" + TextBox9.Text + "','" + TextBox10.Text +
"')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved Successfully");
}
else
{
Response.Write("Not Saved");
}
}
}

Monthly Payment

using
using
using
using
using
using
using
using
using
using
using
using
using

System;
System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;
System.Data.SqlClient;

public partial class MonthlyPayment : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();

37

Insurance Policy Maintenance System


SqlDataReader dr;
protected void Page_Load(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender,
{
string Query = "insert into Monthly_Pay
TextBox1.Text + "','" + TextBox2.Text + "','" +
TextBox4.Text + "','" + TextBox5.Text + "','" +
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Amount Payed");
}
else
{
Response.Write("Not Payed");
}
}
}

EventArgs e)
values('" +
TextBox3.Text + "','" +
TextBox6.Text + "')";

View Customers

using
using
using
using
using
using
using
using
using
using
using
using
using

System;
System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;
System.Data.SqlClient;

public partial class ViewCustomers : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
string Query = "select * from Cus_Reg";

38

Insurance Policy Maintenance System

ds = _objDb.Display(Query);
GridView1.DataSource = ds;
GridView1.DataBind();

View Insurance

using
using
using
using
using
using
using
using
using
using
using
using
using

System;
System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;
System.Data.SqlClient;

public partial class ViewInsurance : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
string Query = "select * from Insurance";
ds = _objDb.Display(Query);
GridView1.DataSource = ds;
GridView1.DataBind();
}
}

View Payment Details

using
using
using
using
using
using
using
using

System;
System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;

39

Insurance Policy Maintenance System


using
using
using
using
using

System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;
System.Data.SqlClient;

public partial class ViewPaymentDetails : System.Web.UI.Page


{
ClsDbLayer _objDb = new ClsDbLayer();
DataSet ds;
protected void Page_Load(object sender, EventArgs e)
{
string Query = "select * from Monthly_Pay";
ds = _objDb.Display(Query);
GridView1.DataSource = ds;
GridView1.DataBind();
}
}

OUTPUT

Home Page

40

Insurance Policy Maintenance System

Admin Login

41

Insurance Policy Maintenance System

Admin Page

42

Insurance Policy Maintenance System

Add Insurance

43

Insurance Policy Maintenance System

View Customers

44

Insurance Policy Maintenance System

View Payment

45

Insurance Policy Maintenance System

Customer Login
46

Insurance Policy Maintenance System

Customer Page

47

Insurance Policy Maintenance System

View Insurance

48

Insurance Policy Maintenance System

Monthly Payment

49

Insurance Policy Maintenance System

CONCLUSION

This project entitled Insurance Policy Maintenance System was successfully


completed and all three phases namely as system analysis, system design and system

50

Insurance Policy Maintenance System


implementation are thoroughly tested with live data. This project is validated using unit
testing.
The project was design to fulfill all the requirements of the user. This system was
successfully tested using all testing process tools improve with reliability and
consistency.

The project is fully menu driven one. So, any one with little knowledge of
computer can handle the software and the requirements for the user are fully completed.
The project is simple and suitably designed for end users.

BIBLIOGRAPHY

51

Insurance Policy Maintenance System


Active Server Page Unleashed, Stephen Walther, Second Edition, Sums
Publishing 2003

Active Server Page 2.0, Richard Launcher, Second Reprint, Queue 2003

Roger S.Pressman, 1997, Software Engineering A Parishioners Approach,

Fourth Edition, McGraw-Hill International

MS SQL Server 2000, Kaleen Delaney JOE Cellos SQL for smartens, JOE

Cello The Gurus Guide to Transact SQL, Ken Henderson

Websites:

http://www.dotnettutorials.com
http://www.csharpcorner.com
http://www.w3schools.com

52