1 INTRODUCTION

1.1- Objective
The application will help the administration of the organization to keep track of all policies, their maturity. This application will simplify the premium calculation and reimbursement of claims. Report generated in this application will help in customer retention before maturity of the policy. This application will make the retrieving of data much simpler and faster.

1.2- Introduction To The Project

Insurance policy provider will provide a complete platform to the company to create and maintain different types insurance products. This system has got the enhance feature which will help to maintain the client and agent records. This system will also generates reports on daily and monthly basis to help in customer retention. Moreover its enhanced feature will also enable to moderate customer account on a call for query for further reference.

2
2.1

SYSTEM REQUIREMENT Hardware requirements :

Processor Speed RAM Free HDD Space Internet Connection Network Card Mouse Keyboard Monitor : : : : : : : : : Intel Pentium Processor III 700 MHz 128 MB 10 MB Dial up (56 kbps) Any network interface card or modem 3 button scroll mouse 104 keys keyboard 15 color

2.2

Software Requirements
Development environment Running environment Database Used Operating System Browser : : : : : Microsoft Visual Studio 2010 Microsoft NET Framework 4.0 Microsoft SQL Server 2008 Microsoft WINDOWS XP, 2007 Microsoft Internet Explorer 6 or Netscape Navigator or Mozilla FireFox

2.3

Feasibility Requirements
An important outcome of the project startup meeting is the determination that the system requested is feasible. There are three aspects in the feasibility study portion of the preliminary investigation

2.3.1 Technical Feasibility

In this part the aspects that are considered are, Can the work for the project be done with the current equipment, existing software technology, and available personnel? If new technology is required, what is the likelihood that it can be developed? Since In the start-up meeting, it was found that the main need was for better response and throughput from the system. The committee for technical feasibility study decided that the problems of existing system were because of following reasons: The existing system was designed many years back and since then lot of patches had been done, as and when needed. Which had made it inefficient and the documentation of the code was also not up to date. The technology being used in the present system was quite old in comparison to the recent advancement in all areas of computers. There was lot of bottlenecks in the existing software, which delayed the processing. Keeping in view with above problems, as desired in case of

further expansion, the study group gave the report to go in for more open type of hardware. Apart from that the redesigning of the existing system. According to some latest DBMS, which could meet the needs of the end users, was also recommended.

2.3.2 Economic Feasibility

The study group also went into the economic aspects of its proposals. The groups were of the view that there were sufficient benefits in going in for a new version of the existing system and of course, for acquiring new hardware to cater especially, the new system. Also, it was decided that the whole rewriting of the existing system would be economically feasible only if the development took place, by the students of PCTI. Of course in the matter of helping them with the new machine a specialist could be called in.

2.3.3 Operational Feasibility

All along the above studies and discussion, the users of HUL Merchandising Analysis were actively involved and were keen to get a new system, which would eliminate all the old problems. Overall the users went all out to support for the proposed new system. The total project costs, priority, completion time and personnels required were estimated. Initial plans were drawn up as to how the project would proceed to its final implementation, while running the existing system so that companys information needs were not affected.

2.3.4 Request Approval

With all the preliminary investigation carried out thoroughly, the decisions and proposals were put forth to the top management. The management which values the useful changes, was also of the view that library should keep up the pace with latest technological trends in IT industry. So, they approved whole heartily the kind of major work being proposed, to be undertaken by management. Another group was set up to go into the details for acquiring the suitable hardware and software for the new system.

2.4

Performance Requirements
The following performance characteristics were taken care of in developing the systems

2.4.1 User Friendliness

3

The system is easy to learn and understand. A native user can also use the system effectively, without any difficulty.

2.4.2 User Satisfaction

The system is such that it stands up to the users expectations and requirements.

2.4.3 Response Time

The response time of all the operations is very low. This has been made possible by careful programming.

2.4.4 Error Handling

Response to User Errors and undesired situations have been taken care of to ensure that the system operates without halting in case of such situation and proper error messages are given to user.

2.4.5 Safety
The system is able to avoid catastrophic behavior.

2.4.6 Robustness
The system recovers from undesired events without human intervention.

2.4.7 Security
The system provides protection of information through the mechanism of password incorporated in it. Therefore, only authorized people can access the databases.

2.4.8 Accuracy
The system is accurate. Thus, its utility is very high.

2.4.9 Portability / Pervasiveness

The system can be accessed from anywhere just having internet connectivity. It can be accessed through any device having xml parser.

2.4.10 Throughput
The system gives the maximum throughput.

2.4.11 Cost Element

In this system, servicing a given demand in a program does not require a lot of money. The system is reliable, versatile and efficient.

Introduction to the .NET Framework

Although the goal of this book is to introduce deployable solutions with the .NET Enterprise Servers, it is necessary to begin by examining the architecture of the .NET Framework. The .NET Enterprise Servers that will be introduced in later chapters will be discussed as tools that can be exploited by .NET developers. As a new, integrated software development environment, the .NET Framework allows the developer to combine the front-end development environment easily with the .NET Enterprise Servers to facilitate the development of scalable, Internet-ready applications. The framework is the foundation for the .NET programming environment and should be researched thoroughly by all developers who need to create new Windows applications. .NET Framework base classes, and the user and program interfaces. The section on user and program interfaces specifically defines the purpose of both Windows Forms and Web Forms. After the overview of the .NET Framework, the chapter highlights some of the changes to the Visual Basic and Visual C++ programming languages.

3.1

.NET Framework Overview

Microsofts new software development platform, .NET Framework, is the first Microsoft development environment designed from the ground up for Internet development. Although .NET is not meant to be used exclusively for Internet development, its innovations were driven by the limitations of current Internet development tools and technology. The basis of this new development platform consists of three primary components or layers: the common language runtime, the .NET Framework base classes, and the user and program interfaces. The .NET Framework has three layers: common language runtime, the .NET Framework base classes, and the user and program interfaces (ASP.NET and Windows Forms). The foundation of the .NET Framework is the common language runtime. Its principal purpose is to load, execute, and manage code that has been compiled to Microsofts new intermediate byte-code format called Intermediate Language (IL). Several languages, notably Microsofts Visual Basic .NET and C# .NET (pronounced C sharp), have compilers supporting this format, and many more are currently in development. It is important to note that the IL code is not interpreted. The common language runtime uses just-in-time compilers to compile the IL code to native binary code before execution. Other significant features of the common language runtime include the following:

The foundation of the .NET Framework is the common language runtime. Its principal purpose is to load, execute, and manage code that has been compiled to Microsofts new intermediate byte-code format called Intermediate Language (IL). Several languages, notably Microsofts Visual Basic .NET and C# .NET (pronounced C sharp), have compilers supporting this format, and many more are currently in development. It is important to note that the IL code is not interpreted. The common language runtime uses just-in-time compilers to compile the IL code to native binary code before execution. Other significant features of the common language runtime include the following:

Version control Memory management Cross-language integration Common data type system

The next component or layer of the .NET Framework is the .NET Framework base classes. The purpose of this layer is to provide the services and object models for data access and manipulation, data streams (input/output [I/O]), security, thread management, and more. In many respects the Windows API (Application Programming Interface) has been abstracted into these base classes. These libraries are an object-oriented collection of classes that can be reused and enhanced to enable rapid application development. The classes support the creation of applications that range from ASP.NET Web pages and Web Services to traditional Windows and command line applications. The .NET Framework also provides several runtime hosts, which are unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, creating a software environment that can exploit both managed and unmanaged features. The .NET Framework software developers kit (SDK) not only provides several runtime hosts but also supports the development of third-party runtime hosts. For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly 6

with the runtime to enable .aspx pages and Web services, both of which are discussed later in this section. The final layer of the .NET Framework consists of the user and program Interfaces. The two components of this layer are ASP.NET Application Services and Windows Application Services. The cornerstone of the ASP.NET Application Services is, of course, ASP.NET, which in turn supports the new Web services and Web Forms technologies that are discussed later. The Windows Application Services component supports traditional Windows programming applications through Windows Forms.

3.2

INTRODUCTION TO THE .NET FRAMEWORK 5

The following sections describe the main components of the .NET Framework in more detail.

Features of the Common Language Runtime

The common language runtime provides an execution environment that manages the set of code targeted to the .NET Framework. Code management can include memory management, thread management, security management, code verification, and compilation of the code. All managed components must first be assigned a level of trust. The level or degree of trust can vary on the basis of the following origins:

Local computer Internet connection Enterprise local area network (LAN) connection

After the component is assigned an appropriate level of trust, the managed component either can or cannot perform functions from within the application. In fact, based on the trust levels, a managed component may act differently within the same active application. The degree of trust can be used to limit registry access, file access, or network functionality. The common language runtime enforces security in a way that enables a client to run executables without endangering or risking inappropriate access to sensitive local resources or devices. For example, a user could double-click an executable in an email, and although it may play a video or audio stream, access to personal data on the computer is not at risk. This enables an Internet application to be as feature-rich as normal desktop applications. The common language runtime also uses a common type system (CTS) to enforce code robustness and language interoperability. Various Microsoft and other third-party compilers can generate managed code that complies with the CTS. The purpose of the CTS is to enforce a strict data type and code verification standard. Through the CTS, managed code can include managed classes, types, and other objects while enforcing type safety and conformity to the infrastructure.

Another primary goal of the common language runtime is increased programmer efficiency. With all the .NET Framework languages complying with the common language runtime, the programmer can choose a language of preference. Each language can take full advantage of the common language runtime, the class library, and the components. This will make future programming available in whichever language is best suited to the developer and application requirements while maintaining a high level of language interoperability and independence. The built-in automatic memory management also enhances application and infrastructure stability. some of the most common application errors involving memory leaks and invalid memory references. It manages all references to objects and releases them when they are no longer in use. In a nutshell, the automatic memory management helps the application clean up after itself. The common language runtime also should increase application performance. This may be accomplished in two ways: just-in-time (JIT) compliers and server-side applications. The JIT compilers are used to compile all managed code to native machine binary code at execution. Server-side applications can house application logic and business rules on .NET Enterprise Servers such as Internet Information Server (IIS) and SQL Server. This allows the consolidation of application logic and business rules in a more maintainable environment and permits execution closer to dependent resources. For many applications this will result in not only reduced maintenance requirements but increased responsiveness.

3.3 .NET FRAMEWORK CLASS LIBRARY

The .NET Framework class library is a collection of reusable classes, or types, that tightly integrate with the common language runtime. .NET applications benefit from using and extending or inheriting the functionality from the classes and types available in the class library. The class library is very hierarchical and well organized, as shown in Figure 1.2. It starts with the most generic classes and continues to build down to classes with very specific and precise functionality. Although this library is extensive, its organization makes it easy to learn and use. In an age of ever-growing technology it is refreshing to see a new technology and a new architecture that promise a reduced learning curve. This model also makes it easy for third-party components to be integrated easily with the existing class library.

As expected in an object-oriented class library, the .NET Framework classes enable developers to accomplish rapidly a wide range of common programming tasks, including things such as string management, file access, and database connectivity. Also, several classes facilitate highly specialized and custom development environments. These classes make the application development environment very flexible. The following types of applications are readily supported through the .NET Framework:

ASP.NET applications Console applications Scripted applications Windows applications (Windows Forms) Web services

For example, the Windows Forms classes are used to create Windows graphical user interface (GUI) applications, which often are referred to as standalone applications. This is facilitated through a series of reusable graphical interface classes. Alternatively, in developing a Web-based application, the HTML and Web Forms classes facilitate its rapid development. Either way the underlying framework provides the flexibility for feature-rich applications regardless of the choice of application environment.

3.4

CLIENT APPLICATION DEVELOPMENT

Client applications represent the most common application environment in use today. These are the applications that one would invoke by opening some type of form and initiating an action. Examples of client applications range from word processing applications to a customized accounting package. One typically begins the application by opening a form from a desktop icon or the Windows Start menu. Client applications typically use the standard Windows features, such as dialogue boxes, menu items, and buttons. In most cases the files and executables for the application are stored and run locally and are interacted with by using local peripherals. The traditional Windows programming environment has been replaced in .NET by the Windows Forms control. The managed Windows Forms control allows the application to be deployed over the Internet, and the user can view the application as a Web page. In the past developers created such applications by using C or 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 the earlier products into a single, consistent development environment. The goal of the single environment is to simplify the development of client applications. This simplicity can be further enhanced by incorporating the security and deployment features of the common language runtime. Because feature-rich applications can be deployed from the Web, many applications that once were installed on a users system can now be 9

Web-based. The application can define code-access security limits, which restrict what the application can do on an individuals machine. This gives the developer security features even though the application is running in the machine language. In fact, a single application can incorporate objects from multiple Web servers. Each object and Web server may have security rights different from those of another server. All security rights are evaluated even though the objects are used within a single application. Windows Forms applications still have some advantages over Web-based applications. Windows Forms applications have a level of trust that is already assumed. This allows binary and natively executing code to interact with some of the resources on the local machine. This is used to perform the necessary GUI elements of the application.

3.5

SERVER APPLICATION DEVELOPMENT

Web services are server-side application components that can be distributed easily in a similar fashion to Web sites. Web services components are not targeted for a specific browser and have no user interface. They are simply reusable software components designed to be used by other applications. Web-based applications, traditional applications, and even other Web services can use the Web services. The Web services are moving application development toward the Internet. All application development can now take advantage of the highly distributed world that previously was available only with Web-based applications. ASP.NET is the environment that enables developers to use the .NET Framework to target Web services applications. Both Web Forms and Web services use IIS as the publishing mechanism for applications, and both have a collection of supporting classes in the .NET Framework. If you are familiar with earlier versions of ASP technology, you will enjoy the new features of Web Forms. The most noticeable new feature is the ability to develop ones Web Forms in any language that supports the .NET Framework. You can use Visual Basic .NET to create your Web Forms if that is the language you prefer. You are not required to learn multiple languages to create different types of applications. Web Forms also can execute in the native machine language and take advantage of the common language runtime in the same manner as all other managed applications. This allows the Web Forms to be compiled and executed at a much faster rate. Users will notice that the ASP.NET pages are faster, more functional, and easier to create. The .NET Framework also provides a collection of classes and tools to aid in the development and consumption of Web services applications. Web services are built on standards such as SOAP (a remote procedure-call protocol), XML (an extensible data format), and WSDL (Web Service Description Language). The .NET Framework conforms to these standards to promote interoperability with non-Microsoft solutions. Although many of the chapters in this book define the role of these protocols and show how they allow the .NET Framework to interact with .NET Enterprise Servers, readers can reference Chapter 15, Web Services with .NET, for more information on the role of each of these standards. The .NET Framework provides a set of classes that conform to the underlying standards of SOAP, WSDL, and XML. Consequently, as the user develops and publishes Web services, he or she just focuses on the underlying logic and function of the service, not on 10

infrastructure communication issues. Web Forms and Web services are compiled and executed in native machine language and take advantage of the scalable architecture of IIS. While these technologies are dependent on IIS, their tight integration makes initial configuration and ongoing maintenance easy.

3.6

WINDOWS FORMS

As the technologies shift more toward the Web environment, it may appear that the .NET Framework is discouraging traditional Windows application development. This is far from accurate. The Windows Forms environment simplifies the development of applications and can be used to create feature rich user interface Windows applications. Windows Forms is a new forms package that can be used to develop and deploy Windows applications through the .NET Framework. Windows Forms is included as part of the new Microsoft Visual Studio package. It uses the .NET platform and leverages the new technologies, including a common application framework, managed execution environment, integrated security, and object-oriented design principles. In addition, Windows Forms offers full support for Web services and can connect easily to data stores by using a .NET data model called ADO.NET. The shared environment of Visual Studio allows a developer to create Windows Forms applications by using any of the languages that support the .NET platform. These languages include Visual Basic .NET, C++, and C#. Windows Forms in the .NET Framework supports the development of Windows user interface applications. While the design is similar to that of Web Forms, the classes and implementation are significantly different. The development environment, however, is such that an application developer will feel equally comfortable writing an application using Windows Forms or Web Forms. Both environments have similar classes and some events in common, and the classes that are different are at least consistent in function and purpose. Although this book is not necessarily about creating Windows Forms or Web Forms, it is necessary to understand the foundation to be able to build on it with the .NET Enterprise Servers. The primary goals of Windows Forms are ease of use and reusability. All Windows Forms are based on a common language runtime feature called delegates. Delegates are basically pointers. Each event can be given a delegate handler so that the user is not required to define the handler through another means (override, event map, and interface for all events on the class). The process of creating a Windows Forms project is also easy. Creating a Windows Forms project with Visual Studio .NET creates only one project file that is compiled: Form1.cs. There are no header files, no interface definition files, no bootstrap application files, no resource files, and no library files. The goal is to keep the process minimal and easy to coordinate. All the information needed for the project is contained in the code for the form. Because Windows Forms are built on the common language runtime, developers can choose any one of the many languages that are now targeting the common language runtime to build Windows applications. Developers can now write Windows Forms applications (or Web Forms applications or data applications) in a variety of languages that range from C# to COBOL, Eiffel, and Perl, among others. This decreases the learning curve by allowing developers to stick with their language of choice. 11

Windows Forms takes full advantage of GDI+, Microsofts next-generation 2-D graphics system. The graphics programming model in Windows Forms is fully object-oriented, and the assorted pens, brushes, images, and other graphics objects follow the same ease-of-use guidelines as the rest of the .NET Framework. Developers can now include great new drawing features such as alpha blending, color gradients, textures, anti-aliasing, and vector image formats. When this feature is coupled with the Windows 2000 operating systems layered and transparent windows features, developers can create richer, more graphical Win32 applications with much less effort.

3.7

WEB FORMS

Web Forms are the forms that are engine-supplied with ASP.NET. Their purpose is to provide Web browser-based user interfaces. This technology has been enhanced to provide the next generation of development by adding features such as drag-and-drop development. Web Forms consist of two parts: a template and a component. The template contains the layout information for the user interface elements. The component contains all the logic that is linked to the user interface. Web Forms take advantage of controls to make all the coordination required appear easy. Controls run on the server and make themselves known to the client. This allows the application interface to have many of the characteristics of a normal Win32 application. Controls are reusable user interface elements that are used to construct the form.

3.8

NEW PROGRAMMING LANGUAGES

Visual Studio .NET is Microsofts .NET Framework development environment. Unlike earlier releases, this integrated development environment (IDE) is designed to support all programming languages that compile to Microsofts Intermediate Language (MSIL), the managed code that actually is executed by the common language runtime. To meet this requirement, the Visual Studio .NET releases of Visual Basic and C++ underwent significant changes. In addition, Microsoft introduced C#, a new .NET programming language. To fully exploit the new capabilities of the .NET Framework, the changes to Visual Basic were particularly significant. While the .NET release is not compatible with prior versions of Visual Basic, Microsoft has incorporated a migration tool to ease the conversion of existing applications. However, because the architecture of .NET is so different from the previous application development architecture, many applications may not port easily from the older platform to .NET. Consequently, many Visual Basic Version 6 applications will either be around for some time or undergo complete rewrites for the new .NET Framework. The following sections introduce and reference the most popular new features of Visual Basic .NET, C#, and ASP.NET and discuss a couple of considerations for C++. 12

3.8.1 Visual Basic .NET

This release of Visual Basic represents the most significant architectural change since the initial release of Visual Basic. Because it now shares its development environment with other .NET languages, Visual Basic. NET can draw on the functionality of the .NET Framework base classes. Arguably the most significant advantage this gives Visual Basic developers is its tight integration with Web-based development. Visual Basic has long been the dominant programming language for Windows-based applications, but it always lacked an elegant approach to developing Internet applications. This release changes that situation. In addition to integration with the .NET Framework, Visual Basic .NET incorporates several new features, listed below, which expand the scalability and robustness of Visual Basic application development. Object-oriented development has been expanded to be fully supported in Visual Basic .NET. This includes full inheritance, parameterized constructors, and control over property and method overriding. Variables can be declared and initialized on the same line. Previously, variables were first declared (associated with a data type) and later initialized to a value. Additionally, the variant data type is no longer supported. However, the user still is not required to declare variables before initializing them. For example, the following ASP.NET Page directive can be used to turn off option explicit, thus suspending the need to declare variables before using them. Generally, this is a poor programming practice and is not encouraged. <%@Page Language = vb Explicit=false %> Type Safety is used to generate errors when a data type conversion could fail at runtime. Error handling has been expanded to support the C-based language Try...Catch...Finally exception-handling statements. Visual Basic previously required, and still accepts, On Error statements in each procedure, which often results in duplicated code. The Try...Catch...Finally statements represent a more structured error-handling process that permits the nesting, and consequently the reuse, of exception-handling routines. Additionally, the finally statement is a control structure for writing cleanup code that executes in both normal and exception conditions. Initializers can be used anywhere, including inside a control structure. Visual Basic .NET supports initializing the variable on the same line on which it is created. The semantics for a procedure-level declaration is similar if written in a single line as opposed to a declaration statement followed by an assignment statement. In other words, the following two examples are equivalent. Dim Y As Integer = 10 Dim Y As Integer Y = 10 13

Parentheses must be used in calling functions and subprocedures. All methods, functions, and subprocedures must now use parentheses to close the parameter list. Parameters are now passed to functions and subprocedures by value by default. Earlier versions of Visual Basic defaulted to passing parameters by reference. The ByRef keyword can still be used to pass a parameter by reference. New conversion methods are available for converting data types. Although older methods such as CStr are available, newer methods such as ToString are recommended.

These features combine with the .NET Framework to provide an easier environment to work with, a better performing application, and flexibility in incorporating Web-based applications. The resulting version of Visual Basic is more stable, scalable, and easier to use. However, as previously noted, the downside to these much-anticipated new features is a lack of direct backward compatibility. Moderately complex applications cannot be ported easily from earlier versions to Visual Basic .NET. Although conversion tools exist, the number of required changes is significant. In many cases the migration tools simply flag an area that needs to be addressed, giving no indication of what the problem is or what needs to be done about it.

3.8.2 Visual C++

Among the programming languages Microsoft has altered to conform to the .NET Framework, Visual C++ has the fewest changes and requires the shortest learning curve. In addition, applications written in C++ can be ported easily to the new environment. The most significant change to C++ revolves around the concept of managed code, or the ability to compile code to MSIL for execution by the common language runtime. Within Visual Studio .NET, the developer can identify blocks of code as managed. The default option for Visual C++ development is still unmanaged code, which is compiled directly to machine language code, lacks the type safety required for language interoperability, and forgoes the memory management features of the .NET Framework. In other words, Visual C++ developers can pretty much conduct business as usual. The language expands with a few additional items, which are detailed in the following list: Exception-handling tables Metadata describing the modules into which the code is compiled Location of object references (no need for Co Create Instance; just use New to declare an object) Visual C++ then uses managed code and lets the common language runtime handle the following items: Exception handling Security 14

Lifetime management Debugging Profiling Memory management

3.8.3 C#
C# is Microsofts programming language for its new .NET development environment. Microsofts goal with C# is to provide a simple, modern, object oriented .NET programming language that is Internet-centric. Although .NET code can be written in many languages, C# is the only language designed specifically for the .NET platform and for that reason may become the language of choice for this environment. C# may be deceptively simple. Although it has only about 80 keywords and a dozen intrinsic data types, it is highly expressive. It includes support for all types of modern component-based, object-oriented development. C#, like C++ and Java, owes its origins to the C programming language. For that reason, C++ and Java developers will notice a striking similarity to those languages and enjoy an easy-to-learn and familiar programming environment. Specifically, C# is an elegant language object-oriented language that: Readily supports the definition of and working with classes and their properties and methods. Implements encapsulation, inheritance, and polymorphism, the three pillars of object-oriented programming. Features self-contained class declarations (definitions). Header files or IDF (interface definition files) are not required to define or publicize a classs signature. Supports the implementation of interfaces, or contracts, to implement functionality. While a class can only inherit, or extend, from a single class, it can implement multiple interfaces. Supports structs, which are lightweight custom types that require fewer resources than does a more complex, robust type defined as a class. Provides for operator overloading and modern exception handling. Microsoft again has bet the company on a new technology and developed C# as its premier language for that technology. C# was developed for the .NET platform and was modeled after the success of earlier languages. It has a rapid application development environment courtesy of Visual Basic, performance due to C, object-oriented nature from C++, and elegance from Java.

15

3.8.4 ASP.NET
ASP.NET is a programming framework developed by Microsoft for building powerful Web-based applications. While not a programming language, ASP.NET is the cornerstone of the .NET platforms Internet-centric orientation.

It is the latest version of Microsofts ASP, a powerful, server-based technology for creating dynamic Web pages. Being a core element in the .NET platform, all .NET languages utilize ASP.NET as their entry point for Internet development. Perhaps the biggest difference between earlier versions of ASP and ASP.NET is the way in which code runs on the Web server. With ASP.NET, code is compiled into executable classes that are compiled to native code by the common language runtime layer of the .NET Framework. All the earlier versions of ASP supported only scripting languages, which were interpreted. Since ASP.NET pages are now executable classes, they have access to all the other powerful features of the common language runtime, such as memory management, debugging, security, and strong data typing. ASP.NET has built-in support for three languages: Visual Basic .NET, C#, and JScript.NET. The user can install support for other .NET-compatible languages as well. JScript.NET is Microsofts latest version and implementation of JavaScript. Although this version still maintains its scripting feel, it is fully objectoriented and compiles to MSIL. Because all ASP.NET code must be written in a .NET language, the ASP.NET programming framework is the foundation of Web services and Web Forms, the two components of ASP.NET Application Services. The following list illustrates how developers can exploit ASP.NET in developing Internet-centric applications. XMLWeb services give developers the ability to access server functionality remotely. Using Web services, organizations can share their data and component libraries with other applications. Web services enable client/server and server/server communication through the HTTP protocol by using XML. Consequently, programs written in any language, using a component model and running on any operating system, can access Web services. ASP.NET Web Forms gives the developer the ability to create Web pages on the .NET platform. Web Forms enables developers to program embedded controls on either the client or the server. Using ASP Server Controls, Web applications enable the easy maintenance of state as information is communicated between the browser and the Web server. ASP.NET and the .NET Framework provide default authorization and authentication schemes for Web applications. Developers can easily remove, add to, or replace these schemes, depending on the needs of the application. 16

 Simple ASP pages can be migrated easily to ASP.NET applications. ASP.NET offers
complete syntax and processing compatibility with ASP applications. Developers simply need to change the file extensions from .asp to. aspx to migrate their files to the ASP.NET page framework.

3.9

WHAT .NET MEANS TO DEVELOPERS

Since the .NET Framework is a software development platform, it should be no surprise that .NET will have the biggest impact on developers. Here are some of the more significant benefits and implications awaiting them: With all the languages that soon will be compatible with .NET, developers have an unprecedented choice of interoperable languages to select from. That selection is far more than simply a lifestyle choice. .NET language choices provide the opportunity for a gradual transition from less complex languages to more powerful ones. Additionally, much of what is learned about the .NET base classes in one language carries over to the next language. Not only is the choice of languages unprecedented, so is the ease of the learning curve. Previously, Windows application programming required the developer to interact with components, application programming interfaces, and language-specific runtime libraries. This resulted in application development that was vastly different from one language to another. The new methodology, as described below allows all languages to interface directly with the .NET Framework. The .NET languages are interoperable, meaning that classes developed in one .NET language can be freely reused and extended by a developer using another .NET language. While organizations may strive to standardize on a consistent development platform and language, developers may have more freedom to strike a proper balance between the skill required and the power necessary to accomplish their tasks

17

. .NET continues the evolution of Windows development in the direction of providing more built-in functionality. The .NET base classes in particular encapsulate many of the mundane chores necessary in building application and network infrastructures. Developers may finally be freed from .DLL hell. Prior development environments stored information about components separately from those components. Consequently, installing and upgrading components were often a problem. .NET maintains these metadata inside the component itself, preventing the data from becoming out of sync with the component.

The common language runtime now features a garbage collector, a process responsible for removing objects from memory that no longer have references to them. The developer is freed from the tedious and often fruitless activity of trying to assure that all objects have been destroyed. Finally, .NET developers will have the challenge of working in a true object-oriented programming environment. While object-oriented programming and design can be a complex process, the elegant implementation offered to developers in the .NET environment will make it a thrilling and stimulating challenge.

18

3.10 ADO+
Every 2.3 years Microsoft develops a new and better data access technology. First we had DAO, then RDO and most recently ADO. ADO was pretty good but not particularly ideal in the highly scalable and often disconnected world of web development ADO+ is a new data access technology that is optimized for disconnected operation. It is XML based, and offers a great deal of flexibility over its predecessors. Some of its new features includes : Integrated XML support. Enhanced support for disconnected data sets. Easier data sharing. Strongly typed data. Increased performance. ADO+ allows us to establish a connection to a data source, retrieve that data, map the data into an XML based DataSet, and then distribute that DataSet object as needed. The DataSet object is designed for disconnected operation. Of course, data binding remains available, both in Web Forms and Win Forms. From a programmers perspective, data binding is not much different to the way it has been since VB6. We still set properties on our controls to indicate where to get the data and which data field or fields are to be displayed. As with virtually all the technologies were discussing here, ADO+ is accessed via the .NET system class libraries in this case via the System.Data.ADO namespace

3.11 ASPX File Format

ASPX is a text file format used to create Webform pages; in programming jargon, the ASPX file typically contains static HTML or XHTML markup, as well as markup defining Web Controls and Web User Control where the developer places all the required static and dynamic content for the web page. Additionally, dynamic code which runs on the server can be placed in a page within a block <% dynamic code %> which is similar to other web development technologies such as PHP, JSP and ASP, but this practice is generally discouraged except for Data binding.

19

The recommended method for dealing with dynamic program code is to use the code behind model, which places this code in a separate file or in a specially designated script tag. Code behind files is typically name something to the effect of MyPage.aspx.cs or MyPage.aspx.vb based on the ASPX file name.

3.12 Other Files

Other file extensions associated with different versions of ASP.NET includes : Asax Global.asax, used for application level logic and event handling. Ascx Web UserControl custom controls to be placed onto web pages. Ashx custom HTTP handlers Asmx web service pages. Axd when enabled in web.config requesting trace.axd outputs application level tracing. Browser browser capabilities files stored in XML format; introduced in version 3.0. ASP.NET 2 includes many of these by default, to support common web browsers. These specify which browsers have which capabilities, so that ASP.NET 2 can automatically customize and optimize its output accordingly. Special browser files are available for free download to handle, for instance, the W3C Validator, so that it properly shows standards compliant pages as being standards compliant. Replaces the harder to use rowser Caps section that was in machine.config and could be overridden in web.config in ASP.NET 1.x. Config web.config is the only file in a specific web application to use this extension by default, however ASP.NET provides facilities to create and consume other config files. These are stored in XML format, so as to allow configuration changes to be made with simplicity. Cs/vb In ASP.NET 2 any cs/vb files placed inside the App_Code folder are dynamically compiled and available to the whole application.

3.13 Development Tools

Several available software packages exist for developing ASP.NET applications: Microsoft Expression Web Designer, part of the forthcoming Microsoft Expression Studio application suite. Visual Studio .NET or Visual Studio 2008 or Visual Web Developer 2008 Express Edition. ASP.NET Web Matrix. Macromedia HomeSite 5.5 Microsoft SharePoint Designer 12 Delphi 2006 20

MonoDevelop (Free/Open Source) SharpDevelop (Free/Open Source)

3.14 The Common Language Runtime

Many different languages and platforms provide a runtime, and the .NET Framework is no exception. Its runtime, however, is quite different from most. The Common Language Runtime (CLR) in the .NET Framework manages the execution of the code and provides access to a variety of services that make the development process easier. The CLR has been developed to be far superior to previous runtimes, such as the VB runtime, by providing the following functionality: Cross-language integration Code access security Object lifetime management Debugging and profiling support

Code that is compiled and targeted to the CLR is known as managed code. Managed code has the metadata needed for the CLR to provide the services of multilanguage support, code security, object lifetime management, and memory management. Metadata is basically data about data or a description of the contents of a .NET component. This metadata is stored within the assembly manifest. In the past, it was difficult for components written in competing languages to interact with one another. The .NET Framework uses metadata so that .NET components are self-describing, making them easy to interoperate with other components.

3.15 Compilation to managed code

When creating a .NET application, use one of the .NET languages. After the code is written, you (or Visual Studio .NET) uses the languages compiler to compile the code down to Microsoft Intermediate Language (IL). IL is a CPU-independent set of instructions that can easily be converted to native code. The metadata (the self-describing information about the object created) is also contained within the IL. You can see from the diagram of the compilation process that it really doesnt matter which language you are using with the .NET platform. In the end, each .NET language compiles down to the same type of object. The IL is CPU-independent, which means that the object created by the compiler is not dependent upon the computer that created it. It, therefore, can be moved at this stage from the computer that created it to any other computer that has the .NET Framework on it. And because this IL object is self-describing, it doesnt need to be registered in the Windows registry. You only have to copy it to the hard drive of the computerthats it. It makes XCopy possible with .NET applications. To run the application from here, it actually needs to be compiled even furtherdown to native code. This is handled by the .NET 21

Frameworks JIT compiler. The IL contains everything that is needed to do this, such as the instructions to load, call methods, and a number of other operations.

3.16 Compiling further with JIT compilation

When the ASP.NET application is invoked for the first time, one of the .NET Frameworks JIT compilers takes the IL code and compiles it down to native code. The native code or machine code that is produced is CPU-specific code. This compilation process is quite apparent when working with ASP.NET. You can build a page in ASP.NET and compile it down to IL using Visual Studio .NET. When you invoke the page by typing the endpoint of the Web page in the browser (using the pages URL), it is run through a JIT compiler. The JIT compiler used depends upon the architecture of the server hosting the .aspx page. After the page is compiled down to native code, the code is executed, and the page class that is created outputs the appropriate code to the end users browser. This compilation process takes time, and you can see this time elapse when you first invoke an ASP.NET page. There is a pause of a few seconds before the page is generated. After the JIT compilation is complete, however, the page has been compiled into CPUspecific code, and this process doesnt need to occur again. So when a second end user invokes the same ASP.NET page, that user doesnt have to wait for the JIT compilation to take place again. The page output is quick. You can see this by simply pressing F5 (for Refresh). Notice how quickly the page is retrieved. If you make a change to the code of the ASP.NET page, the page goes through the entire compilation process again. If you make a change to the code and re-invoke the ASP.NET, you notice the same slow start, but only with the first invocation. Also the JIT compiler, as it compiles to machine code, ensures that the code is type safe. It makes certain that objects are separate, thereby ensuring that these objects wont unintentionally corrupt one another. An interesting point to understand with JIT compilation and ASP.NET applications is that the entire ASP.NET application is not JIT-compiled when only one of the .aspx pages of the application is invoked. Instead, the JIT compiler compiles only the code that is needed by the application at the point of invocation. The pieces of your application that are not needed at the point of invocation are not be compiled down to native code until they are called for the first time. The more your ASP.NET application is used, therefore, the faster it runs.

3.17 Namespaces
System
This namespace includes the core needs for programming. It includes base types like string, date time, Boolean and so forth, support for environments such as the console, math functions, and base classes for attributes, exceptions and arrays.

System.CodeDom
This library provides the ability to create code and run it, at runtime. 22

System.Collections
Defines many common containers or collections used in programming such as lists, queues, stacks, hash tables, and dictionaries. It includes support for generics.

System.ComponentModel
Provides the ability to implement the run time and design time behavior of components and controls. It contains the infrastructure for implementing attributes and type converters, binding to data sources, and licensing components.

System.Configuration
Provides the infrastructure for handling configuration data.

System.Data
This namespace represents the ADO.NET architecture, which is set of computer software components that can be used by programmers to access data and data services.

System.Deployment
Allows you to customize the way your application upgrades when using ClickOnce.

System.Diagnostics
Gives you the ability to diagnose your application. It includes event logging, performance counters, tracing and interaction with system processes.

System.DirectoryServices
Provides easy access to Active Directory from managed code.

System.Drawing
Provides access to GDI+graphics functionality, including support for 2D and vector graphics, imaging, printing and text services.

System.EnterpriseServices
Provides .NET objects with access to COM+ services making the .NET Framework objects more practical for enterprise applications.

System.Globalization
Provides help for writing internationalized applications. Culture related information, including the language, the country/region the calendars in use. The format patterns for dates, currency and numbers can be defined.

23

System.IO
Allows you to read from and write to different streams such as files or other data streams. Also provides a connection to the file system.

System.Management
Allows you to query for information such as how much free space is left on the disk, what is the current CPU utilization, which database a certain application is connected to and much more.

System.Media
Provides you the ability to play system sounds and .wav files.

System.Messaging
Allows you to connect to monitor and administer message queues on the network and send, receive or peek messages. .NET remoting is another name for some of the functionality provided. This namespace is being superseded by Windows Communication Foundation.

Ssytem.Net
Provides an interface for many of the protocols used on networks today such as HTTP, FTP and SMTP. Secure communication is supported by protocols such as SSL.

System.Reflection
Provides an object view of types, methods and fields. You have the ability to dynamically create and invoke types.

System.Resources
Allows you to manage many different resources in the application in order to internationalize an application for different cultures and languages.

System.Runtime
Allows you to manage the runtime behavior of an application or the CLR. Some of the included abilities are interoping with COM or other native code, writing distributed applications, and serializing objects into binary or SOAP.

System.Security
Provides the underlying structure of the common languages runtime security system. This namespace allows you to build security into your application based on policy and permissions. It provides services such as cryptography.

System.ServiceProcess
Allows you to create applications that run as a service within windows. 24

System.Text
Supports various encodings, regular expressions and a more efficient mechanism for manipulating strings.

System.Threading
Helps facilitate multithreaded programming. It allows the synchronizing of thread activities and access to data and provides a pool of system supplied threads.

System.Timers
Allows you to raise an event on a specified interval.

System.Transactions
Provides support for local or distributed transactions.

System.Web
Provides various web related functionality. It enables browser server communication and the creating XML web services. Most or all of these libraries are referred to as the ASP.NET architecture.

System.Windows.Forms
This namespace contains the windows forms architecture which provides access to the older windows API for writing graphical applications for Windows from within managed code.

25

4.
4.1

SYSTEM DESIGN
Design of Input and Output
Input Design: While designing input, the objective is to ensure that the data which will be processed by the system is collected and entered into the system efficiently, according to the specified requirements and with the minimum of errors. In the discussion with the client, the designer will choose the method of input which is cost effective and acceptable to the end user. The process of input design has four stages : Identifying the inputs in the system by listing the data flow diagram which cross the system boundary on the way in. Determining the content of the inputs by inspecting data dictionary. Choosing an appropriate input device to change the users data into a form, this can be read and processed by the computer system. Completing the detailed design work involved in specifying forms, input screens and any other data collection documents. Mostly users prefer it to be a keyboard input when the data is small. When there is bulk or large volume of data to be input users prefer it to be scanner or optical mark reader. Out Design : Having identified from logical model of the new system where the output will be by listing those data flows, which cross the system boundary as they leave the system the next stage in the process is to determine their content. Again structured techniques play a useful role here, because the designer can turn to the data dictionary to find the content of each data flow, which represents an output. Once the content is known, the designer must select the appropriate methods or technology to present information and then create the document, report or display which contains the required by the user might be shown on a data flow diagram. A quality output is one which meets the requirements of the end user and which presents the information in a way which is clear, easy to read and visually attractive.

4.2

System Design Life Cycle

The life-cycle paradigm demands a systematic, sequential approach to software development that begins at the system level and progresses through analysis, design, coding, testing and maintenance. The life-cycle paradigm encompasses the following activities:

System engineering and analysis:

Establishing requirements for every system element and then allocating some subset of these requirements to software.

Software requirement analysis:

To understand the nature of the program to be built, the software engineer (analyst) must understand the information domain for the 26

software, as well as the required function, performance, and interfacing. Requirements for both the system and the software are documented and reviewed with the customer.

Design:

Software design is actually a multiuse process that focuses on four distinct attributes of the program: data structure, software architecture, procedural detail and interface characterization of the software.

Coding: The design must be translated into a machine-readable form. The coding step performs this task. Testing: Once code has been generated, program testing begins. Maintenance: Software will undoubtedly undergo change after it is delivered to the
customer. Software maintenance reapplies each of the preceding life cycle steps to an existing program rather than a new one.

System engineering Analysis Design Coding Testing Maintenance

Fig.: Water Fall Model

27

4.3 E-R Diagram for Insurance Policy

28

4.3 Diagrammatical Representation of the System Design Data Flow Diagram

User

User

Web Server
Authenticate User Request

Search

Online / Shoping
Online / Details

First Level DFD

29

2nd Level DFD

Customer

Vehicle

Life

New User

New Insurance request

Insurance Renewal request

Insurance Claim request

View Request

View Policies

Insurance Management System

Data Storage

Data Base
Data Access

Request Forms

Renewal Form

Insurance Claim request

New Policies

Insurance Officer 30

3rd Level DFD

Customer Validation Vehicle Life

New User

New Insurance request

Insurance Renewal request

Insurance Claim request

View Request

View Policies

New Authorised User

New Customer

Other Requests

New Policies

Vehical / Life

Cancelled

Accepted

Policies

Request Forms

Renewal Form

Insurance Claim request

New Policies

Insurance Officer 31

4.5

Database Design
A database system consists of two main components: 1. The physical and logical organization of a database is controlled by a database management system. The DBMS constructs, maintains and controls access to the database. It is not normally possible to access the data except via the DBMS. 2. The database application code enables the data in the database to be retrieved, modified and updated. This code executes a particular process or function. The data in database is available for use by several user or application programmers simultaneously. Each user may have a different view picture of the data, depending on the requirements of the applications.

LOGIN TABLE:

L_RENEWAL TABLE

32

CLAIM TABLE :

RENEWAL TABLE :

33

NEW USER TABLE :

NEW FORM TABLE :

34

4 Screen Snapshots

Homepage :

35

Registration page :

36

Life Insurance form page :

37

Vehicle Insurance form page :

38

Insurance benefit page :

39

Details:

Coding
Login.aspx.cs: using using using using using using using using using using using System; System.Data; System.Data.SqlClient; System.Configuration; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Xml.Linq;

public partial class _Default : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { TextBox1.Focus(); } protected void Button1_Click1(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationSettings.AppSettings["Con"]); SqlCommand cmd = new SqlCommand("select count (*) from new_user where UserId=@u and password=@p", con); cmd.Parameters.AddWithValue("@u", TextBox1.Text); cmd.Parameters.AddWithValue("@p", TextBox2.Text); con.Open(); int i = (int)cmd.ExecuteScalar(); if (i > 0) { Session["user"] = TextBox1.Text; Response.Redirect("main_form.aspx"); } else { Label6.Text = "<font size=6 color=blue>Sorry ! You are not authorised user</font>"; } con.Close(); } protected void Button2_Click1(object sender, EventArgs e) {

40

//Session["New"] = TextBox3.Text; Response.Redirect("vehical/User.aspx"); } protected void TextBox1_TextChanged(object sender, EventArgs e) { } protected void TextBox2_TextChanged(object sender, EventArgs e) { //TextBox2.BackColor = System.Drawing.Color.Yellow; } protected void Timer1_Tick(object sender, EventArgs e) { Label7.Text = DateTime.Now.ToLongTimeString(); } }

Main_Form.aspx.cs: using using using using using using using using using using using System; System.Data; System.Data.SqlClient; System.Configuration; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Xml.Linq;

public partial class _Default : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { TextBox1.Focus(); } protected void Button1_Click1(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationSettings.AppSettings["Con"]); SqlCommand cmd = new SqlCommand("select count (*) from new_user where UserId=@u and password=@p", con); cmd.Parameters.AddWithValue("@u", TextBox1.Text); cmd.Parameters.AddWithValue("@p", TextBox2.Text); con.Open(); int i = (int)cmd.ExecuteScalar(); if (i > 0) { Session["user"] = TextBox1.Text; Response.Redirect("main_form.aspx"); } else

41

{ Label6.Text = "<font size=6 color=blue>Sorry ! You are not authorised user</font>"; } con.Close(); } protected void Button2_Click1(object sender, EventArgs e) { //Session["New"] = TextBox3.Text; Response.Redirect("vehical/User.aspx"); } protected void TextBox1_TextChanged(object sender, EventArgs e) { //TextBox1.BackColor = System.Drawing.Color.Yellow; //if (TextBox1.Text.Length > 0) //{ // TextBox1.BackColor = System.Drawing.Color.Yellow; //} } protected void TextBox2_TextChanged(object sender, EventArgs e) { //TextBox2.BackColor = System.Drawing.Color.Yellow; } protected void Timer1_Tick(object sender, EventArgs e) { Label7.Text = DateTime.Now.ToLongTimeString(); } } } Life/Claim.aspx.cs: using using using using using using using using using using using System; System.Data; System.Data.SqlClient; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Life_Claim : System.Web.UI.Page { static int var, i1; protected void Page_Load(object sender, EventArgs e) { for (int i = 18; i <= 60; i++) { DropDownList1.Items.Add(i.ToString()); ; } if (Session["user"] == null)

42

{ Response.Redirect("/Insaurance/Login.aspx"); } Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; Load(); } protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } public void Load() { SqlConnection con = new SqlConnection(ConfigurationSettings.AppSettings["Con"]); SqlDataAdapter ad = new SqlDataAdapter("select * from L_claim", con); DataSet ds = new DataSet(); ad.Fill(ds, "cl"); DataTable dt = new DataTable(); dt = ds.Tables[0]; i1 = dt.Rows.Count; if (i1 > 0) { DataRow dr = dt.Rows[i1 - 1]; //int m =Convert.ToInt32( dr[0].ToString()) % 10; int d = 1 + Convert.ToInt32(dr[0].ToString()); //int d = 1 + m; TextBox1.Text = d.ToString(); } else { TextBox1.Text = Convert.ToString("1"); } } protected void Button2_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationSettings.AppSettings["Con"]); SqlCommand cmd = new SqlCommand("insert into L_Claim values(@claim , @name , @age , @gender , @type ,@phone ,@email , @msg) ", con); cmd.Parameters.AddWithValue("@claim", TextBox1.Text); cmd.Parameters.AddWithValue("@name", TextBox2.Text); cmd.Parameters.AddWithValue("@age", DropDownList1.Text); cmd.Parameters.AddWithValue("@gender", DropDownList2.Text); cmd.Parameters.AddWithValue("@type", DropDownList3.Text); cmd.Parameters.AddWithValue("@phone", TextBox3.Text);

43

cmd.Parameters.AddWithValue("@email", TextBox4.Text); cmd.Parameters.AddWithValue("@Msg", TextBox5.Text); con.Open(); int i = (int)cmd.ExecuteNonQuery(); if (i > 0) { Label8.Visible = true; Label8.Text = "Claim Successfully Posted , Please Note Down the Claim No."; } Load(); } protected void ImageButton1_Click(object sender, ImageClickEventArgs e) { Response.Redirect("/Vehical/new.aspx"); } } Life/New.aspx.cs: using using using using using using using using using using using System; System.Data; System.Data.SqlClient; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Life_New : System.Web.UI.Page { int i1; protected void Page_Load(object sender, EventArgs e) { Label10.Visible = false; Panel1.Visible = false; Load(); if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); } Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; }

44

protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } protected void Wizard1_FinishButtonClick(object sender, WizardNavigationEventArgs e) { if (TextBox1.Text == "" && TextBox2.Text == "" && TextBox3.Text == "" && TextBox4.Text == "") { Label10.Visible = true; Label10.Text = "Please Fill Up All The Entry"; } else { SqlConnection con = new SqlConnection(ConfigurationSettings.AppSettings["Con"]); SqlCommand cmd = new SqlCommand("insert into L_New values(@name , @Address , @Phone , @email , @Type ,@L_date , @R_No) con); cmd.Parameters.AddWithValue("@name", TextBox1.Text); cmd.Parameters.AddWithValue("@address", TextBox2.Text); cmd.Parameters.AddWithValue("@phone", TextBox3.Text); cmd.Parameters.AddWithValue("@email", TextBox4.Text); cmd.Parameters.AddWithValue("@Type", kk.Text); cmd.Parameters.AddWithValue("@L_Date", TextBox5.Text); cmd.Parameters.AddWithValue("@R_No", TextBox8.Text); con.Open(); int i = (int)cmd.ExecuteNonQuery(); if (i > 0) { Label10.Visible = true; Label10.Text = "Your Request is Accepted, Note Down Your Registration Nos."; } Load(); Panel1.Visible = true; } } public void Load() SqlConnection con = new SqlConnection(ConfigurationSettings.AppSettings["Con"]); SqlDataAdapter ad = new SqlDataAdapter("select * from L_New", con);

",

45

DataSet ds = new DataSet(); ad.Fill(ds, "new"); DataTable dt = new DataTable(); dt = ds.Tables[0]; i1 = dt.Rows.Count; if (i1 > 0) { DataRow dr = dt.Rows[i1 - 1]; //int m =Convert.ToInt32( dr[0].ToString()) % 10; int d = 1 + Convert.ToInt32(dr[6].ToString()); //int d = 1 + m; TextBox8.Text = d.ToString(); } else { TextBox8.Text = "1"; } } }

Life/Policies.aspx.cs
using using using using using using using using using using using System; System.Data; System.Data.SqlClient; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Life_Policies : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { Label2.Visible = false; Label3.Visible = false;

if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); }

Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; } protected void LinkButton1_Click(object sender, EventArgs e)

46

{ Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } protected void Button1_Click(object sender, EventArgs e) { GridView1.Visible = true; SqlConnection con = new SqlConnection(ConfigurationSettings.AppSettings["Con"]); SqlDataAdapter ad = new SqlDataAdapter("select * from L_new where R_No='" + TextBox1.Text + "'", con); DataSet ds = new DataSet(); ad.Fill(ds, "cl"); if (ds.Tables[0].Rows.Count == 0) { Label2.Visible = true; Label2.Text = "Record Does Not Exist"; GridView1.Visible = false; } else { GridView1.DataSource = ds.Tables[0]; GridView1.DataBind(); Label3.Visible = true; } } }

Life/Pol1.aspx.cs
using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Life_Pol1 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); } Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d);

47

Response.Expires = -1500; Response.CacheControl = "no-cache"; } protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } }

Life/Pol2.aspx.cs
using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Life_Pol2 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); } Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; } protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } }

Life/Pol3.aspx.cs
using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security;

48

using using using using

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

public partial class Life_Pol3 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); } Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; } protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } }

Life/Pol4.aspx.cs :
using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Life_Pol4 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); } Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; } protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null;

49

Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } }

Life/Renewal.aspx.cs :
using using using using using using using using using using using System; System.Data; System.Data.SqlClient; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Life_Renewal : System.Web.UI.Page { int i1; protected void Page_Load(object sender, EventArgs e) { if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); } Label10.Visible = false; Load(); Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; } protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx") } public void Load() { SqlConnection con = new SqlConnection(ConfigurationSettings.AppSettings["Con"]); SqlDataAdapter ad = new SqlDataAdapter("select * from L_renewal", con); DataSet ds = new DataSet(); ad.Fill(ds, "new"); DataTable dt = new DataTable(); dt = ds.Tables[0]; i1 = dt.Rows.Count; if (i1 > 0)

50

{ DataRow dr = dt.Rows[i1 - 1]; //int m =Convert.ToInt32( dr[0].ToString()) % 10; int d = 1 + Convert.ToInt32(dr[4].ToString()); //int d = 1 + m; TextBox5.Text = d.ToString(); } else { TextBox5.Text = "1"; } } protected void Button1_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationSettings.AppSettings["Con"]); SqlCommand cmd = new SqlCommand("insert into l_renewal values(@name , @Address , @Phone , @email , @registration ,@type ,@amount , @card_T, @card_N , @expiry) ", con); cmd.Parameters.AddWithValue("@name", TextBox1.Text); cmd.Parameters.AddWithValue("@address", TextBox2.Text); cmd.Parameters.AddWithValue("@phone", TextBox3.Text); cmd.Parameters.AddWithValue("@email", TextBox4.Text); cmd.Parameters.AddWithValue("@registration", TextBox5.Text); cmd.Parameters.AddWithValue("@Type", DropDownList1.Text); cmd.Parameters.AddWithValue("@amount", TextBox6.Text); cmd.Parameters.AddWithValue("@card_T", DropDownList2.Text); cmd.Parameters.AddWithValue("@card_N", TextBox7.Text); cmd.Parameters.AddWithValue("@expiry", BasicDatePicker1.Text); con.Open(); int i = (int)cmd.ExecuteNonQuery(); if (i > 0) { Label10.Visible = true; Label10.Text = "Your Request is Accepted,Your Vehical Insaurance is renewing soon."; } Load(); } protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e) { if (DropDownList1.SelectedItem.ToString() == "Child Insaurance") { TextBox6.Text = "550"; } else if (DropDownList1.SelectedItem.ToString() == "Whole Life") { TextBox6.Text = "650";

51

} else if (DropDownList1.SelectedItem.ToString() == "Endowment") { TextBox6.Text = "700"; } else if (DropDownList1.SelectedItem.ToString() == "Pension") { TextBox6.Text = "500"; }

else { TextBox6.Text = "800"; } } }

Vehical/Claim.aspx.cs
using using using using using using using using using using using System; System.Data; System.Data.SqlClient; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Vehical_Claims : System.Web.UI.Page { static int var, i1; protected void Page_Load(object sender, EventArgs e) { for (int i = 18; i <= 60; i++) { DropDownList1.Items.Add(i.ToString()); ; } if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); }

Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; Load();

52

} protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } public void Load() { SqlConnection con = new SqlConnection(ConfigurationManager.AppSettings["Con"]); con.ConnectionString = @"Data Source=.\SQLEXPRESS;AttachDbFilename=D:\lucky\Project\zip~\Insaurance\Insa urance\DataBase\Insaurance_Data.MDF;Integrated Security=True;Connect Timeout=30;User Instance=True"; SqlDataAdapter ad = new SqlDataAdapter("select * from claim", con); DataSet ds = new DataSet(); ad.Fill(ds, "cl"); DataTable dt = new DataTable(); dt = ds.Tables[0]; i1 = dt.Rows.Count; if (i1 > 0) { DataRow dr = dt.Rows[i1 - 1]; //int m =Convert.ToInt32( dr[0].ToString()) % 10; int d = 1 + Convert.ToInt32(dr[0].ToString()); //int d = 1 + m; TextBox1.Text = d.ToString(); } else { TextBox1.Text = Convert.ToString("1"); } } protected void Button2_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.AppSettings["Con"]); con.ConnectionString = @"Data Source=.\SQLEXPRESS;AttachDbFilename=D:\lucky\Project\zip~\Insaurance\Insa urance\DataBase\Insaurance_Data.MDF;Integrated Security=True;Connect Timeout=30;User Instance=True"; SqlCommand cmd = new SqlCommand("insert into Claim values(@claim , @name , @age , @gender , @type ,@phone ,@email , @about) ", con); cmd.Parameters.AddWithValue("@claim", TextBox1.Text); cmd.Parameters.AddWithValue("@name", TextBox2.Text); cmd.Parameters.AddWithValue("@age", DropDownList1.Text); cmd.Parameters.AddWithValue("@gender", DropDownList2.Text); cmd.Parameters.AddWithValue("@type", DropDownList3.Text); cmd.Parameters.AddWithValue("@phone", TextBox3.Text); cmd.Parameters.AddWithValue("@email", TextBox4.Text);

53

cmd.Parameters.AddWithValue("@about", TextBox5.Text); con.Open(); int i = (int)cmd.ExecuteNonQuery(); if (i > 0) { Label8.Visible = true; Label8.Text = "Claim Successfully Posted , Please Note Down the Claim No."; } Load(); } protected void DropDownList3_SelectedIndexChanged(object sender, EventArgs e) { i1++; if (DropDownList3.SelectedItem.ToString() == "2Wheeler") { TextBox1.Text = var.ToString(); } else if (DropDownList3.SelectedItem.ToString() == "3Wheeler") { TextBox1.Text =var.ToString(); } else if (DropDownList3.SelectedItem.ToString() == "4Wheeler") { TextBox1.Text = var.ToString(); } else { TextBox1.Text = var.ToString(); } } }

Vehical/Key_Benefit.aspx.cs
using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Vehical_Key_Benifit : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { if (Session["user"] == null) {

54

Response.Redirect("/Insaurance/Login.aspx"); } Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; } protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } } using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Vehical_Key_Benifit : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); } Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; } protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } }

Vehical/Motor.aspx.cs
using using using using using using using using using using System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Vehical_Motor : System.Web.UI.Page {

55

protected void Page_Load(object sender, EventArgs e) { if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); } Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; } protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } }

Vehical/Renewal.aspx.cs
using using using using using using using using using using using System; System.Data; System.Data.SqlClient; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Vehical_Renewal : System.Web.UI.Page { int i1; protected void Page_Load(object sender, EventArgs e) { if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); } Label10.Visible = false; Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; Load(); } public void Load() { SqlConnection con = new SqlConnection(ConfigurationManager.AppSettings["Con"]); con.ConnectionString = @"Data Source=.\SQLEXPRESS;AttachDbFilename=D:\lucky\Project\zip~\Insaurance\Insa urance\DataBase\Insaurance_Data.MDF;Integrated Security=True;Connect Timeout=30;User Instance=True";

56

SqlDataAdapter ad = new SqlDataAdapter("select * from renewal", con); DataSet ds = new DataSet(); ad.Fill(ds, "new"); DataTable dt = new DataTable(); dt = ds.Tables[0]; i1 = dt.Rows.Count; if (i1 > 0) { DataRow dr = dt.Rows[i1 - 1]; //int m =Convert.ToInt32( dr[0].ToString()) % 10; int d = 1 + Convert.ToInt32(dr[4].ToString()); //int d = 1 + m; TextBox5.Text = d.ToString(); } else { TextBox5.Text = "1"; } } protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e) { if (DropDownList1.SelectedItem.ToString() == "2 Wheeler") { TextBox6.Text = "550"; } else if (DropDownList1.SelectedItem.ToString() == "3 Wheeler") { TextBox6.Text = "650"; } else if (DropDownList1.SelectedItem.ToString() == "4 Wheeler") { TextBox6.Text = "700"; } else { TextBox6.Text = "800"; } } protected void Button1_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.AppSettings["Con"]); con.ConnectionString = @"Data Source=.\SQLEXPRESS;AttachDbFilename=D:\lucky\Project\zip~\Insaurance\Insa urance\DataBase\Insaurance_Data.MDF;Integrated Security=True;Connect Timeout=30;User Instance=True"; SqlCommand cmd = new SqlCommand("insert into renewal values(@name , @Address , @Phone , @email , @registration ,@type ,@amount , @card_T, @card_N , @expiry) ", con);

57

cmd.Parameters.AddWithValue("@name", TextBox1.Text); cmd.Parameters.AddWithValue("@address", TextBox2.Text); cmd.Parameters.AddWithValue("@phone", TextBox3.Text); cmd.Parameters.AddWithValue("@email", TextBox4.Text); cmd.Parameters.AddWithValue("@registration", TextBox5.Text); cmd.Parameters.AddWithValue("@Type", DropDownList1.Text); cmd.Parameters.AddWithValue("@amount", TextBox6.Text); cmd.Parameters.AddWithValue("@card_T", DropDownList2.Text); cmd.Parameters.AddWithValue("@card_N", TextBox7.Text); cmd.Parameters.AddWithValue("@expiry", BasicDatePicker1.Text); con.Open(); int i = (int)cmd.ExecuteNonQuery(); if (i > 0) { Label10.Visible = true; Label10.Text = "Your Request is Accepted,Your Vehical Insaurance will be renewing soon."; } Load(); } protected void TextBox5_TextChanged(object sender, EventArgs e) { } }

Vehical/View.aspx.cs
using using using using using using using using using using using System; System.Data; System.Data.SqlClient; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Vehical_View : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { GridView1.Visible = false; Label2.Visible = false; Label3.Visible = false; if (Session["user"] == null) { Response.Redirect("/Insaurance/Login.aspx"); }

Response.Buffer = true; Response.ExpiresAbsolute = DateTime.Now.AddDays(-1d); Response.Expires = -1500; Response.CacheControl = "no-cache"; }

58

protected void LinkButton1_Click(object sender, EventArgs e) { Session["user"] = null; Session.Abandon(); Response.Redirect("/Insaurance/Login.aspx"); } protected void Button1_Click(object sender, EventArgs e) { GridView1.Visible = true; SqlConnection con = new SqlConnection(ConfigurationManager.AppSettings["Con"]); con.ConnectionString = @"Data Source=.\SQLEXPRESS;AttachDbFilename=D:\lucky\Project\zip~\Insaurance\Insa urance\DataBase\Insaurance_Data.MDF;Integrated Security=True;Connect Timeout=30;User Instance=True"; SqlDataAdapter ad = new SqlDataAdapter("select * from claim where claim='"+TextBox1.Text+"'", con); DataSet ds = new DataSet(); ad.Fill(ds, "cl"); if (ds.Tables[0].Rows.Count == 0) { Label2.Visible = true; Label2.Text = "Record Does Not Exist"; GridView1.Visible = false; } else { GridView1.DataSource = ds.Tables[0]; GridView1.DataBind(); Label3.Visible = true; }

} }

59

Source code:
Login.aspx ( Source)
<%@ Page Language="C#" AutoEventWireup="true" Inherits="_Default" %> CodeFile="Login.aspx.cs"

<%@ Register assembly="AjaxControlToolkit" namespace="AjaxControlToolkit" tagprefix="cc1" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" > <head runat="server"> <title>Untitled Page</title> <style type="text/css"> table.t1 { background-color : olive ; } #form1 { height: 755px;

} .cc { color : Gray; } .style1 { width: 212px; height: 58px; } .style2 { height: 58px; } .style9 { width: 169px; } .style10 { width: 255px; height: 39px; } .style14 {

60

width: 212px; height: 39px; } .style15 { height: 39px; } .style22 { width: 255px; height: 26px; } .style25 { font-family: cursive; font-size: medium; color: #66FFFF; } .style28 { width: 212px; height: 26px; } .style29 { height: 26px; } p.MsoNormal {margin-top:0cm; margin-right:0cm; margin-bottom:10.0pt; margin-left:0cm; line-height:115%; font-size:11.0pt; font-family:"Calibri","sans-serif"; } .style30 { color: #FFCCFF; } .style31 { width: 212px; height: 38px; } .style32 { width: 255px; height: 38px; } .style33 { height: 38px; } .style34

61

{ height: 88px; } </style> <script language="javascript" type="text/javascript"> // <!CDATA[ function IMG1_onclick() { } // ]]> </script> </head> <body style="background-color: #336699" > <form id="form1" runat="server"> <div style="height: 249px"> <div style="height: 236px"> <asp:Image ID="Image1" runat="server" Height="242px" ImageUrl="~/Picture/head copy.png" style="text-align: center; margin-left: 108px" Width="1110px" /> </div> <br /> &nbsp;<br /> <table style="width: 100%; height: 231px;"> <tr> <td class="style9" rowspan="5">

<asp:Image ID="Image2" runat="server" Height="305px" Width="625px" ImageUrl="~/pic/mainImg.jpg" />

</td> <td class="style28"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <asp:Label ID="Label1" runat="server" Font-Bold="False" Font-Names="Comic Sans MS" Font-Size="Large" ForeColor="#000066" Text="Username :"></asp:Label> </td> <td class="style22"> <asp:TextBox ID="TextBox1" runat="server" Height="25px" ontextchanged="TextBox1_TextChanged" Width="170px" BackColor="White" ValidationGroup="aa"></asp:TextBox> <cc1:TextBoxWatermarkExtender ID="TextBox1_TextBoxWatermarkExtender"

62

runat="server" Enabled="True" TargetControlID="TextBox1" WatermarkText="____Username____" WatermarkCssClass="cc"> </cc1:TextBoxWatermarkExtender> </td> <td class="style29"> <asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server" ControlToValidate="TextBox1" ErrorMessage="Empty Field !" Display="None" EnableTheming="False" ValidationGroup="aa"></asp:RequiredFieldValidator> <cc1:ValidatorCalloutExtender ID="RequiredFieldValidator1_ValidatorCalloutExtender" runat="server" Enabled="True" TargetControlID="RequiredFieldValidator1"> </cc1:ValidatorCalloutExtender> </td> </tr> <tr> <td class="style31"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;<asp:Label ID="Label2" runat="server" Font-Names="Comic Sans MS" Font-Size="Large" ForeColor="#000066" Text="Password :"></asp:Label> </td> <td class="style32"> <asp:TextBox ID="TextBox2" runat="server" Height="25px" ontextchanged="TextBox2_TextChanged" Width="170px" BackColor="White" TextMode="Password" ValidationGroup="aa"></asp:TextBox> <cc1:TextBoxWatermarkExtender ID="TextBox2_TextBoxWatermarkExtender" runat="server" Enabled="True" TargetControlID="TextBox2" WatermarkText="Password" WatermarkCssClass="cc"> </cc1:TextBoxWatermarkExtender> </td> <td class="style33"> <asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server" ControlToValidate="TextBox2" ErrorMessage="Empty Field !" Display="None" EnableTheming="False" ValidationGroup="aa"></asp:RequiredFieldValidator> <cc1:ValidatorCalloutExtender ID="RequiredFieldValidator2_ValidatorCalloutExtender" runat="server" Enabled="True" TargetControlID="RequiredFieldValidator2"> </cc1:ValidatorCalloutExtender> </td>

63

</tr> <tr> <td class="style14"> </td> <td class="style10"> <asp:Button ID="Button1" runat="server" FontBold="True" ForeColor="#000099" Height="31px" onclick="Button1_Click1" Text="Login" Width="88px" ValidationGroup="aa" /> &nbsp;&nbsp;&nbsp;&nbsp;<asp:Button ID="Button2" runat="server" Font-Bold="True" ForeColor="#000099" Height="31px" onclick="Button2_Click1" Text="New User" Width="102px" /> </td> <td class="style15"> <asp:ScriptManager ID="ScriptManager1" runat="server"> </asp:ScriptManager> </td> </tr> <tr> <td class="style1"> <asp:Timer ID="Timer1" runat="server" ontick="Timer1_Tick"> </asp:Timer> </td> <td class="style2" colspan="2"> <asp:Label ID="Label6" runat="server" FontNames="Comic Sans MS" ForeColor="#CC0000" Height="25px" Width="271px"></asp:Label> </td> </tr> <tr> <td colspan="3" class="style34"> <asp:UpdatePanel ID="UpdatePanel1" runat="server" UpdateMode="Conditional"> <Triggers> <asp:AsyncPostBackTrigger ControlID="Timer1" EventName="Tick" /> </Triggers> <ContentTemplate> <br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<asp:Label ID="Label7" runat="server" BackColor="#336600" Font-Names="Comic Sans MS" Font-Size="XLarge" ForeColor="#CCFFFF" Height="52px" style="text-align: center; margin-top: 0px;" Width="200px"></asp:Label>

64

<br /> </ContentTemplate> </asp:UpdatePanel> </td> </tr> </table> &nbsp;<div class="style25" style="height: 158px"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0% EMI option available for ICICI Bank and Citibank credit card holders only at the discretion of ICICI Bank and Citibank. Bonus is redeemed during renewals&nbsp; <br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if done within 90 days Towing charges are subject to policy terms and conditions.For more details on coverage, terms and conditions please read Policy Document&nbsp; <br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;&nbsp;&nbsp; carefully beforeconcluding a sale.ICICI Lombard General Insurance Company Limited. Insurance is the subject matter of the solicitation.<br /> <br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs p;&nbsp;&nbsp; Registered Office: ICICI Lombard General Insurance Company Limited. ICICI Bank Towers, Bandra Kurla Complex,Mumbai - 400051;<br /> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs p;&nbsp;&nbsp; Mailing Address: ICICI Lombard General Insurance Company Limited. Zenith House, Keshavrao Khadye Marg,Mahalaxmi, Mumbai-400034.<br /> <hr style="width: 906px; margin-left: 165px" /> <br /> <div style="height: 21px"> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; <span class="style30">ALL RIGHT RESERVED </span></div> </div>

65

</div> </form> </body> </html>

Main_Form.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Main_Form.aspx.cs" Inherits="Main_Form" %> <%@ Register Src="WebUserControl.ascx" TagName="WebUserControl" TagPrefix="uc1" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" > <head runat="server"> <title>Untitled Page</title> </head> <body bgcolor="olive"> <form id="form1" runat="server"> <div> &nbsp;<uc1:WebUserControl ID="WebUserControl1" runat="server" /> <asp:LinkButton ID="LinkButton1" runat="server" OnClick="LinkButton1_Click" Style="z-index: 100; left: 903px; position: absolute; top: 0px">LogOut</asp:LinkButton> <asp:Image ID="Image2" runat="server" Height="52px" ImageUrl="~/Picture/logo1.JPG" Width="327px" /> <asp:Image ID="Image1" runat="server" Height="53px" ImageUrl="~/Picture/imgad.gif" Style="z-index: 101; left: 353px; position: absolute; top: 12px" Width="331px" /> <br /> <br /> <br /> <pre> <font size="2"> <table border="0" cellpadding="0" cellspacing="0" width="779" style="z-index: 102; left: 229px; position: absolute; top: 92px"><tr><td align="middle" valign="top" style="height: 195px"><table border="0" cellpadding="0" cellspacing="0" width="752"><tr><td align="middle" class="awardtextborder" valign="top" style="height: 166px"><table border="0" cellpadding="0" cellspacing="0" width="100%"><tr align="middle" valign="top"><td colspan="3" height="10" valign="center"></td></tr><tr align="middle" valign="top"><td rowspan="4" valign="center" width="12%"><img height="63" src="Picture/award1.gif" width="61" style="z-index: 101; left: 28px; position: absolute; top: 14px" /></td><td align="left" class="award-text" valign="center" style="color: white; width: 549px;">Lombard has been awarded <strong>'General Insurance company of the year 2007'</strong> across Asia,</td><td rowspan="4" valign="center" width="15%"><img height="56" src="Picture/award2.gif"

66

width="94" style="z-index: 100; left: 614px; position: absolute; top: 13px" /></td></tr><tr align="middle" valign="top"><td align="left" class="award-text" valign="center" style="color: white; width: 549px;">&nbsp; &nbsp; &nbsp; &nbsp;At the 11th Asia Insurance Industry Awards 2007 held in Singapore.</td></tr><tr align="middle" valign="top"><td align="left" class="award-text" valign="center" style="color: white; width: 549px;">ICRA has assigned an iAAA rating indicating <strong>highest claims paying ability</strong> to ILombard</td></tr><tr align="middle" valign="top"><td align="left" class="award-text" valign="center" style="color: white; width: 549px;">&nbsp;General Insurance Company Limited</td></tr></table></td></tr><tr><td align="middle" valign="top" style="height: 13px"></td></tr></table></td></tr><tr><td align="left" class="lead1" valign="center" style="color: white; height: 70px">** 0% EMI option available for ICICI Bank and Citibank credit card holders only at the discretion of ICICI Bank and Citibank<br /># Bonus is redeemed during renewals if done within 90 days<br />^ Towing charges are subject to policy terms and conditions <br /></td></tr><tr><td align="left" class="lead1" height="39" valign="center" style="color: white">For more details on coverage, terms and conditions please read Policy Document carefully before concluding a sale.<br />ICICI Lombard General Insurance Company Limited. Insurance is the subject matter of the solicitation.IRDA Reg. No.115 Motor 01<br /><font color="#a41c2b">Registered Office:</font>&nbsp; Lombard General Insurance Company Limited. Bank Towers, Bandra Kurla Complex,Mumbai - 400051. <br /><font color="#a41c2b">Mailing Address:</font> Lombard General Insurance Company Limited. Zenith House, Keshavrao Khadye Marg, Mahalaxmi, Mumbai 400 034.</td></tr><tr><td><script type="text/javascript"> var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www."); document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E")); </script><script src="http://www.googleanalytics.com/ga.js" type="text/javascript"></script><script type="text/javascript"> var pageTracker = _gat._getTracker("UA-129630-4"); pageTracker._initData(); pageTracker._trackPageview(); </script><!-- Advertiser 'Communicate2 - IN', Include user in segment 'Jan 08 Search Replay ICICI Lombard' - DO NOT MODIFY THIS PIXEL IN ANY WAY --></td></tr></table> </font> </pre> </div> </form> </body> </html>

67

Life/Claim.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Claim.aspx.cs" Inherits="Life_Claim" %> <%@ Register Src="../WebUserControl.ascx" TagName="WebUserControl" TagPrefix="uc1" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" > <head runat="server"> <title>Untitled Page</title> <script language="javascript" type="text/javascript"> <!-function Image3_onclick() { } // --> </script> </head> <body bgcolor="olive"> <form id="form1" runat="server"> <div style="height: 73px"> <asp:Image ID="Image1" runat="server" ImageUrl="~/pic/a (9).jpg" Style="z-index: 103; left: -13px; position: absolute; top: 8px; width: 735px; height: 94px;" /> &nbsp; <asp:LinkButton ID="LinkButton1" runat="server" CausesValidation="False" OnClick="LinkButton1_Click" Style="z-index: 100; left: 908px; position: absolute; top: 3px">LogOut</asp:LinkButton> <table cellpadding="3" cellspacing="3" style="z-index: 102; left: 249px; width: 314px; position: absolute; top: 105px; height: 212px"> <tr> <td style="width: 100px; height: 17px"> <asp:Label ID="Label1" runat="server" Font-Bold="True" ForeColor="White" Style="z-index: 100; left: 6px; position: absolute; top: 6px" Text="Claim No" Width="91px"></asp:Label> <asp:Label ID="Label2" runat="server" Font-Bold="True" ForeColor="White" Style="z-index: 100; left: 6px; position: absolute; top: 39px" Text="Full Name" Width="91px"></asp:Label> <asp:Label ID="Label3" runat="server" Font-Bold="True" ForeColor="White" Style="z-index: 100; left: 9px; position: absolute; top: 79px" Text="Age" Width="91px"></asp:Label>

68

<asp:Label ID="Label4" runat="server" Font-Bold="True" ForeColor="White" Style="z-index: 100; left: 6px; position: absolute; top: 113px" Text="Gender" Width="91px"></asp:Label> </td> <td style="width: 48px; height: 17px"> <asp:TextBox ID="TextBox1" runat="server" Enabled="False" Font-Bold="False" Font-Size="Medium" ForeColor="Red"></asp:TextBox></td> </tr> <tr> <td style="width: 100px; height: 30px"> </td> <td style="width: 48px; height: 30px"> <asp:TextBox ID="TextBox2" runat="server" Width="176px"></asp:TextBox> </td> </tr> <tr> <td style="width: 100px"> </td> <td style="width: 48px"> <asp:DropDownList ID="DropDownList1" runat="server"> </asp:DropDownList> <asp:DropDownList ID="DropDownList3" runat="server" AutoPostBack="True" Style="z-index: 100; left: 123px; position: absolute; top: 140px" Width="77px"> <asp:ListItem>Children</asp:ListItem> <asp:ListItem>Whole Life</asp:ListItem> <asp:ListItem>Endowment</asp:ListItem> <asp:ListItem>Pension</asp:ListItem> <asp:ListItem>Special</asp:ListItem> </asp:DropDownList> </td> </tr> <tr> <td style="width: 100px; height: 22px"> </td> <td style="width: 48px; height: 22px"> <asp:DropDownList ID="DropDownList2" runat="server" Width="79px"> <asp:ListItem Selected="True">Male</asp:ListItem> <asp:ListItem>Female</asp:ListItem> </asp:DropDownList> </td> </tr> <tr> <td style="width: 100px; height: 31px"> <asp:Label ID="Label5" runat="server" Font-Bold="True" ForeColor="White" Height="5px" Style="z-index: 100; left: 2px; position: absolute; top: 149px" Text="Complain Type" Width="101px"></asp:Label>

69

<asp:Label ID="Label6" runat="server" Font-Bold="True" ForeColor="White" Style="z-index: 100; left: 5px; position: absolute; top: 187px" Text="Phone" Width="91px"></asp:Label> <asp:Label ID="Label8" runat="server" Font-Bold="True" ForeColor="White" Style="z-index: 100; left: 16px; position: absolute; top: 331px" Width="280px"></asp:Label> </td> <td style="width: 48px; height: 31px"> &nbsp; &nbsp; &nbsp; </td> </tr> <tr> <td style="width: 100px"> </td> <td style="width: 48px"> <asp:TextBox ID="TextBox3" runat="server" Width="173px"></asp:TextBox> </td> </tr> <tr> <td style="width: 100px; height: 19px"> <asp:Label ID="Label7" runat="server" Font-Bold="True" ForeColor="White" Style="z-index: 100; left: 11px; position: absolute; top: 220px" Text="Email" Width="91px"></asp:Label> </td> <td style="width: 48px; height: 19px"> <asp:TextBox ID="TextBox4" runat="server" Width="170px"></asp:TextBox> </td> </tr> <tr> <td style="width: 100px; height: 19px"> <asp:Label ID="Label9" runat="server" Font-Bold="True" ForeColor="White" Height="19px" Style="z-index: 100; left: 0px; position: absolute; top: 258px" Text="Complain Msg" Width="110px"></asp:Label> </td> <td style="width: 48px; height: 19px"> <asp:TextBox ID="TextBox5" runat="server" TextMode="MultiLine"></asp:TextBox></td> </tr> <tr> <td colspan="2" style="height: 26px"> &nbsp; <asp:Button ID="Button2" runat="server" BackColor="#C0FFFF" Font-Bold="True" Style="z-index: 102; left: 101px; position: absolute; top: 304px" Text="Submit" OnClick="Button2_Click" /> &nbsp; </td>

70

</tr> </table> <uc1:WebUserControl ID="WebUserControl1" runat="server" /> <asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server" ControlToValidate="TextBox2" ErrorMessage="RequiredFieldValidator" ForeColor="Blue" Style="z-index: 103; left: 567px; position: absolute; top: 149px" Width="136px">Name Field is Blank</asp:RequiredFieldValidator> <asp:RequiredFieldValidator ID="RequiredFieldValidator3" runat="server" ControlToValidate="TextBox5" ErrorMessage="RequiredFieldValidator" ForeColor="Blue" Style="z-index: 104; left: 559px; position: absolute; top: 362px" Width="158px">Message Field is Blank</asp:RequiredFieldValidator> <asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server" ControlToValidate="DropDownList1" ErrorMessage="RequiredFieldValidator" ForeColor="Blue" Style="z-index: 105; left: 567px; position: absolute; top: 184px" Width="136px">Age Field is Blank</asp:RequiredFieldValidator> <asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server" ControlToValidate="TextBox4" ErrorMessage="Email is In Wrong Format" ForeColor="Blue" Style="z-index: 108; left: 560px; position: absolute; top: 310px" ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*" Width="159px"></asp:RegularExpressionValidator> <asp:Panel ID="Panel1" runat="server" BackColor="#C0FFFF" Height="1px" Style="z-index: 102; left: 779px; position: absolute; top: 249px" Width="143px"> DownLoad Claim Form Here....<br /> <a href="../Life%20Insaurance%20Claim.pdf">../Life Insaurance Claim.pdf</a><br /> </asp:Panel> <asp:Image ID="Image3" runat="server" Height="165px" ImageUrl="~/Picture/apna.jpg" Style="z-index: 106; left: 745px; position: absolute; top: 81px; width: 242px;" /> </div> </form> </body> </html>

Life/New.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="New.aspx.cs" Inherits="Life_New" %> <%@ Register Src="../WebUserControl.ascx" TagName="WebUserControl" TagPrefix="uc1" %>

71

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" > <head runat="server"> <title>Untitled Page</title> </head> <body bgcolor="olive"> <form id="form1" runat="server"> <div> <uc1:WebUserControl ID="WebUserControl1" runat="server" /> <asp:LinkButton ID="LinkButton1" runat="server" OnClick="LinkButton1_Click" Style="z-index: 100; left: 1040px; position: absolute; top: 3px">LogOut</asp:LinkButton> <asp:Image ID="Image2" runat="server" Height="60px" ImageUrl="~/Picture/imgad.gif" Style="z-index: 101; left: 348px; position: absolute; top: 2px" Width="389px" /> <asp:Image ID="Image3" runat="server" Height="60px" ImageUrl="~/Picture/logo1.JPG" Style="z-index: 102; left: 9px; position: absolute; top: 0px" Width="349px" /> <asp:Wizard ID="Wizard1" runat="server" ActiveStepIndex="2" BackColor="#C0C0FF" BorderColor="Red" BorderStyle="Solid" ForeColor="DarkBlue" HeaderText="Life Insaurance Form" Style="z-index: 103; left: 241px; position: absolute; top: 252px; height: 190px;" Width="360px" OnFinishButtonClick="Wizard1_FinishButtonClick"> <StepNextButtonStyle BackColor="#C0FFFF" Font-Bold="True" /> <StepStyle BackColor="#FFE0C0" /> <StartNextButtonStyle BackColor="#C0FFFF" Font-Bold="True" /> <FinishCompleteButtonStyle BackColor="#C0FFFF" FontBold="True" /> <FinishPreviousButtonStyle BackColor="#C0FFFF" FontBold="True" /> <WizardSteps> <asp:WizardStep runat="server" Title="Step 1"> <asp:Label ID="lbl1" runat="server" Style="z-index: 100; left: 105px; position: absolute; top: 26px" Text="Name"></asp:Label> &nbsp; <asp:Label ID="Label12" runat="server" BackColor="#C0FFFF" Font-Bold="True" Font-Size="Medium" ForeColor="Red" Height="114px" Style="z-index: 100; left: 0px; position: absolute; top: -162px" Text="&lt;font size=6&gt;Gift your family a healthy future. &lt;pre&gt;&lt;marquee&gt; Secure your family now!&lt;font size=5&gt;&lt;B&gt; Get a Call in 30 mins &lt;/B&gt;!&lt;/font&gt;&lt;/marquee&gt;&lt;/pre&gt; &lt;/font&gt;&lt;br&gt;&lt;font color=purple&gt;At ICICI Lombard we understand what your family means to you. Their health and security is always a matter of concern&lt;/font&gt;"

72

Width="478px" BorderColor="White"></asp:Label> &nbsp;&nbsp; <asp:TextBox ID="TextBox1" runat="server" Style="zindex: 101; left: 162px; position: absolute; top: 21px"></asp:TextBox> <asp:Label ID="Label1" runat="server" Style="z-index: 102; left: 104px; position: absolute; top: 57px" Text="Address"></asp:Label> <asp:TextBox ID="TextBox2" runat="server" Height="19px" Style="z-index: 103; left: 164px; position: absolute; top: 52px" TextMode="MultiLine"></asp:TextBox> <asp:Label ID="Label2" runat="server" Style="z-index: 104; left: 99px; position: absolute; top: 86px" Text="Phone No."></asp:Label> <asp:TextBox ID="TextBox3" runat="server" Style="zindex: 107; left: 164px; position: absolute; top: 86px"></asp:TextBox> <asp:Label ID="Label3" runat="server" Style="z-index: 105; left: 103px; position: absolute; top: 119px" Text="Email"></asp:Label> <asp:TextBox ID="TextBox4" runat="server" Style="zindex: 107; left: 165px; position: absolute; top: 116px"></asp:TextBox> </asp:WizardStep> <asp:WizardStep runat="server" Title="Step 2"> <asp:Label ID="Label4" runat="server" Style="z-index: 100; left: 101px; position: absolute; top: 71px" Text=" Click Next to Get New Form" Font-Bold="True" Height="31px" Width="213px"></asp:Label> &nbsp; &nbsp; &nbsp; &nbsp;</asp:WizardStep> <asp:WizardStep ID="WizardStep1" runat="server" Title="Step 3"> <asp:Label ID="Label8" runat="server" Style="z-index: 100; left: 75px; position: absolute; top: 87px" Text="Registration No"></asp:Label> <asp:Label ID="Label10" runat="server" FontBold="True" ForeColor="White" Style="z-index: 100; left: 3px; position: absolute; top: 205px" Text="Registration No" Width="362px"></asp:Label> &nbsp; &nbsp; <asp:TextBox ID="TextBox8" runat="server" Enabled="False" Style="z-index: 101; left: 204px; position: absolute; top: 86px"></asp:TextBox> <asp:TextBox ID="TextBox5" runat="server" Style="zindex: 101; left: 204px; position: absolute; top: 53px"></asp:TextBox> <asp:Label ID="Label6" runat="server" Style="z-index: 102; left: 74px; position: absolute; top: 28px" Text="InsauranceType"></asp:Label> &nbsp; <asp:Label ID="Label9" runat="server" Style="z-index: 103; left: 76px; position: absolute; top: 56px" Text="Request Date"></asp:Label>

73

<asp:DropDownList ID="kk" runat="server" Style="zindex: 104; left: 205px; position: absolute; top: 26px"> <asp:ListItem>Children</asp:ListItem> <asp:ListItem>Whole Life</asp:ListItem> <asp:ListItem>Endowment</asp:ListItem> <asp:ListItem>Pension</asp:ListItem> <asp:ListItem>Other</asp:ListItem> </asp:DropDownList> &nbsp; &nbsp;&nbsp;</asp:WizardStep> </WizardSteps> <HeaderStyle Font-Bold="True" ForeColor="#C00000" /> <StepPreviousButtonStyle BackColor="#C0FFFF" Font-Bold="True" /> </asp:Wizard> &nbsp;&nbsp; <asp:Image ID="Image1" runat="server" BackColor="#C0FFFF" Height="126px" ImageUrl="~/Picture/banner-left.gif" Style="z-index: 104; left: 730px; position: absolute; top: 94px" Width="143px" /> <asp:Image ID="Image9" runat="server" BackColor="#C0FFFF" Height="162px" ImageUrl="~/Picture/main_img.jpg" Style="z-index: 105; left: 241px; position: absolute; top: 93px" Width="492px" /> <asp:Image ID="Image7" runat="server" Height="221px" ImageUrl="~/Picture/banner_life.jpg" Style="z-index: 106; left: 733px; position: absolute; top: 216px" Width="140px" /> <asp:Image ID="Image4" runat="server" Height="50px" ImageUrl="~/Picture/No_paperwork.gif"

Style="z-index: 107; left: 601px; 253px; width: 135px;" /> <asp:Image ID="Image5" runat="server" ImageUrl="~/Picture/EMI_option.gif" Style="z-index: 108; left: 601px; 302px" Width="140px" /> <asp:Image ID="Image6" runat="server" ImageUrl="~/Picture/Instant_policy.gif" Style="z-index: 109; left: 601px; 346px" Width="140px" /> <asp:Image ID="Image8" runat="server" ImageUrl="~/Picture/apnainsurance_logo.jpg"

position: absolute; top: Height="46px" position: absolute; top:

Height="46px" position: absolute; top:

Style="z-index: 110; left: 601px; position: absolute; top: 392px; height: 51px;" Width="281px" /> <asp:Panel ID="Panel1" runat="server" BorderStyle="Solid" Height="35px" Style="z-index: 112; left: 326px; position: absolute; top: 490px" Width="187px"> <a href="../Lfe%20Insaurance%20Form.doc">../Lfe Insaurance Form.doc</a></asp:Panel>

74

</div> </form> </body> </html>

Life/Policies.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Policies.aspx.cs" Inherits="Life_Policies" %> <%@ Register Src="../WebUserControl.ascx" TagName="WebUserControl" TagPrefix="uc1" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" > <head runat="server"> <title>Untitled Page</title> <script language="javascript" type="text/javascript"> <!-function MARQUEE1_onclick() { } function TABLE1_onclick() { } // --> </script> </head> <body bgcolor="olive"> <form id="form1" runat="server"> <div> <uc1:WebUserControl ID="WebUserControl1" runat="server" /> <asp:LinkButton ID="LinkButton1" runat="server" OnClick="LinkButton1_Click" Style="z-index: 100; left: 923px; position: absolute; top: 1px">LogOut</asp:LinkButton> <asp:Image ID="Image1" runat="server" Height="53px" ImageUrl="~/Picture/imgad.gif" Style="z-index: 101; left: 340px; position: absolute; top: 13px" Width="331px" /> <asp:Image ID="Image2" runat="server" Height="52px" ImageUrl="~/Picture/logo1.JPG" Style="left: -19px; top: 1px" Width="327px" /> <asp:Panel ID="Panel1" runat="server" BorderColor="Black" BorderStyle="Solid" Font-Size="Larger" ForeColor="White" Height="342px" Style="z-index: 102; left: 244px; position: absolute; top: 102px" Width="266px">

75

<a href="Pol1.aspx"> <marquee behaviour="scroll" direction="up" onmouseout="this.scrollAmount=1" onmouseover="this.scrollAmount=0" scrollamount="1" scrolldelay="50" style="width: 273px; height: 38px; z-index: 105; left: -4px; position: absolute; top: 0px;" id="MARQUEE1" language="javascript" onclick="return MARQUEE1_onclick()">Children Policy Coverage</marquee> </a><a href="Pol2.aspx"> <marquee behaviour="scroll" direction="up" onmouseout="this.scrollAmount=1" onmouseover="this.scrollAmount=0" scrollamount="1" scrolldelay="50" style="width: 266px; height: 31px; z-index: 104; left: 0px; position: absolute; top: 153px;">Endowment policies</marquee> </a><a href="pol3.aspx"> <marquee behaviour="scroll" direction="up" onmouseout="this.scrollAmount=1" onmouseover="this.scrollAmount=0" scrollamount="1" scrolldelay="50" style="width: 262px; height: 39px; z-index: 103; left: 2px; position: absolute; top: 65px;">Whole Life Policy</marquee> </a> <a href="Pol4.aspx"> <marquee behaviour="scroll" direction="up" onmouseout="this.scrollAmount=1" onmouseover="this.scrollAmount=0" scrollamount="1" scrolldelay="50" style="width: 261px; height: 31px; z-index: 102; left: 1px; position: absolute; top: 232px;">Pension Policies</marquee></a> <a href="P5.aspx"> <marquee behaviour="scroll" direction="up" onmouseout="this.scrollAmount=1" onmouseover="this.scrollAmount=0" scrollamount="1" scrolldelay="50" style="width: 266px; height: 31px; z-index: 101; left: 0px; position: absolute; top: 308px;">Special Policies</marquee> </a> </asp:Panel> <asp:Panel ID="Panel2" runat="server" BorderColor="Black" BorderStyle="Solid" Font-Bold="True" ForeColor="White" Height="344px" Style="z-index: 104; left: 551px; position: absolute; top: 100px" Width="410px"> <table border="0" cellpadding="0" cellspacing="0" style="zindex: 100; left: 2px; position: absolute; top: 2px; width: 380px; height: 252px;"> <tr> <td align="middle" style="color: maroon; textdecoration: underline" valign="top"> Features<br /> </td> </tr> <tr>

76

<td align="left" class="bullet_txt" height="25" valign="center"> <span class="bullet_txt1">One Policy - One Premium</span> for your family.<br /> <br /> </td> </tr> <tr> <td align="left" class="bullet_txt" height="25" valign="center"> <span class="bullet_txt1">Sum Insured options</span> upto Rs. 4 lakhs.<br /> </td> </tr> <tr> <td align="left" class="bullet_txt" height="25" valign="center"> <span class="bullet_txt1">Hassle-free claim and no Medical checkup</span> upto the age of 55. #<br /> </td> </tr> <tr> <td align="left" class="bullet_txt" height="25" valign="center"> <span class="bullet_txt1">Income Tax benefits</span> under sections 80D.**<br /> </td> </tr> <tr> <td align="left" class="bullet_txt" style="height: 25px" valign="center"> <span class="bullet_txt1">5% discount on premium</span> for every claim-free year.<br /> </td> </tr> <tr> <td align="left" class="bullet_txt" height="25" valign="center"> <span class="bullet_txt1">Avail free health check</span> coupon.***<br /> </td> </tr> <tr> <td align="left" class="bullet_txt" valign="center" style="height: 1px"> <span class="bullet_txt1">Cashless hospitalization</span> across 4500+ network hospitals.<br /> </td> </tr> </table> </asp:Panel> <asp:Panel ID="Panel3" runat="server" BorderStyle="None" Height="64px" Style="z-index: 102; left: 41px; position: absolute; top: 467px" Width="184px">

77

<asp:Label ID="Label1" runat="server" Font-Bold="True" ForeColor="White" Style="z-index: 100; left: 8px; position: absolute; top: 9px" Text="Registration Number" Width="105px"></asp:Label> <asp:Label ID="Label2" runat="server" Font-Bold="True" ForeColor="White" Style="z-index: 100; left: -8px; position: absolute; top: 119px" Text="Claim Number" Width="207px"></asp:Label> <asp:Label ID="Label3" runat="server" Font-Bold="True" FontSize="Larger" ForeColor="White" Style="z-index: 100; left: 319px; position: absolute; top: 128px" Text="Request Is in Process" Width="207px"></asp:Label> <asp:TextBox ID="TextBox1" runat="server" Style="z-index: 101; left: 123px; position: absolute; top: 11px" Width="43px"></asp:TextBox> <asp:Button ID="Button1" runat="server" BackColor="#C0FFFF" Font-Bold="True" OnClick="Button1_Click" Style="z-index: 103; left: 119px; position: absolute; top: 34px" Text="Show " /> </asp:Panel> <asp:GridView ID="GridView1" runat="server" BackColor="AliceBlue" Font-Bold="False" Height="107px" Style="z-index: 104; left: 346px; position: absolute; top: 461px" Width="358px"> <HeaderStyle BackColor="#80FFFF" BorderColor="Red" BorderStyle="Solid" /> </asp:GridView> </div> </form> </body> </html>

Life/Pol1.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Pol1.aspx.cs" Inherits="Life_Pol1" %> <%@ Register Src="../WebUserControl.ascx" TagName="WebUserControl" TagPrefix="uc1" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" > <head runat="server"> <title>Untitled Page</title> </head> <body bgcolor="olive"> <form id="form1" runat="server"> <font color="white" size="3"> <div>

78

<hr size="1" /> <div align="center"> <div align="center"> <center> <asp:Image ID="Image1" runat="server" Height="53px" ImageUrl="~/Picture/imgad.gif" Style="z-index: 100; left: 339px; position: absolute; top: 3px" Width="331px" /> <asp:Image ID="Image2" runat="server" Height="52px" ImageUrl="~/Picture/logo1.JPG" Style="z-index: 101; left: 12px; position: absolute; top: 8px; width: 317px;" /> <asp:LinkButton ID="LinkButton1" runat="server" OnClick="LinkButton1_Click" Style="z-index: 102; left: 887px; position: absolute; top: 6px">LogOut</asp:LinkButton> <table border="0" cellpadding="3" cellspacing="0" width="50%"> <tr> <td valign="top" width="50%"> <table border="4" cellspacing="1" class="cmtable" style="z-index: 104; left: 244px; position: absolute; top: 96px" width="100%" bordercolor="#000000"> <tr> <td class="cmtableheader" colspan="2" style="height: 21px"> Profile - Children</td> </tr> <tr> <td class="cmtablesubheader" style="width: 126px"> Policy Name</td> <td class="cmtablesubheader"> Introduction</td> </tr> <tr> <td class="cmtabledatarow1" style="width: 126px"> <a href="http://www.capitalmarket.com/personal/insurance/insurance.asp?opt=po licyname&opt1=LicProfile&subopt=Bal Vidya&subopta=Children" style="text-decoration: none"><b>Bal Vidya</b></a> </td> <td class="cmtabledatarow1"> A single premium plan that provides money in monthly regular installments and lump sum at specific points of time to meet a child's schooling and college expenses</td> </tr> <tr> <td class="cmtabledatarow2" style="width: 126px">

79

<a href="http://www.capitalmarket.com/personal/insurance/insurance.asp?opt=po licyname&opt1=LicProfile&subopt=Children`s Deferred Assurance Plan&subopta=Children" style="text-decoration: none"><b>Children`s Deferred Assurance Plan</b></a> </td> <td class="cmtabledatarow2"> A low premium, high benefit plan for children aged 0-14 years where risk commences at 18 or 21 years</td> </tr> <tr> <td class="cmtabledatarow1" style="width: 126px"> <a href="http://www.capitalmarket.com/personal/insurance/insurance.asp?opt=po licyname&opt1=LicProfile&subopt=Children`s Money Back Assurance Plan&subopta=Children" style="text-decoration: none"><b>Children`s Money Back Assurance Plan</b></a> </td> <td class="cmtabledatarow1"> A specifically designed plan to provide for a child's higher educational expenses</td> </tr> <tr> <td class="cmtabledatarow2" style="width: 126px"> <a href="http://www.capitalmarket.com/personal/insurance/insurance.asp?opt=po licyname&opt1=LicProfile&subopt=Jeevan Baalya&subopta=Children" style="text-decoration: none"><b>Jeevan Baalya</b></a> </td> <td class="cmtabledatarow2"> A low premium endowment assurance plan for children aged 0-17 years, wherein, income benefits are provided to the child on death of the proposer till he attains 21 years</td> </tr> <tr> <td class="cmtabledatarow1" style="width: 126px"> <a href="http://www.capitalmarket.com/personal/insurance/insurance.asp?opt=po licyname&opt1=LicProfile&subopt=Jeevan Kishore&subopta=Children" style="text-decoration: none"><b>Jeevan Kishore</b></a> </td> <td class="cmtabledatarow1"> For children aged 1-12 years, where risk commences at the age of 7 or 2 years from the commencement of the policy, whichever is later</td>

80

</tr> <tr> <td class="cmtabledatarow2" style="width: 126px"> <a href="http://www.capitalmarket.com/personal/insurance/insurance.asp?opt=po licyname&opt1=LicProfile&subopt=Jeevan Sukanya&subopta=Children" style="text-decoration: none"><b>Jeevan Sukanya</b></a> </td> <td class="cmtabledatarow2"> Limited premium payment plan for the girl child aged between 1-12 years, wherein the girl on attaining 20 years gets the sum assured as survival benefit</td> </tr> <tr> <td class="cmtabledatarow1" style="width: 126px"> <a href="http://www.capitalmarket.com/personal/insurance/insurance.asp?opt=po licyname&opt1=LicProfile&subopt=New Children`s Deferred Assurance Plan&subopta=Children" style="text-decoration: none"><b>New Children`s Deferred Assurance Plan</b></a> </td> <td class="cmtabledatarow1"> A low premium, high benefit plan for children aged 5-12 years where risk commences at 12 years</td> </tr> </table> </td> </tr> <tr> <td align="right" width="65%"> </td> </tr> </table> </center> </div> <hr align="center" size="1" /> <div align="left" > <font size="1"></font> <p align="left"> <asp:Image ID="Image3" runat="server" Height="214px" ImageUrl="~/Picture/banner-ryte.gif" Style="z-index: 105; left: 878px; position: absolute; top: 174px" Width="220px" /> &nbsp;</p> <p> </p> <p>

81

<uc1:WebUserControl ID="WebUserControl1" runat="server" /> </p> </div> </form> </body> </html>

Testing Phase

The testing phase requires organizations to complete various tests to ensure the accuracy of programmed code, inclusion of expected functionality and the interoperability of applications and other network components. Through testing is critical to ensuring systems meet organizational and end user requirements. If organizations use effective project management techniques, they will complete test plans while developing applications, prior to entering the testing phase. Weak project management techniques or demand to complete projects quickly may pressure organizations to develop test plans at the starts of the testing phase. Test plans created during initials project phases enhance an organizations ability to create detailed tests. The use of detailed test plans significantly increases the likelihood that testers will identify weakness before products are implemented. Testing groups are comprised of technicians and end users who are responsible for assembling and loading representatives test data into a testing environment. The groups typically perform tests stages, either from a top down or bottom up approach. A bottom up approach tests smaller components first and progressively adds and tests additional components and systems. And top down approach first tests major components and connections and progressively tests smaller components and organizations. Bottom up tests often begin with functional (requirements based) testing. Functional tests should ensure that expected functional, security and internal control features are present and operating properly. Testers then complete integration and end to end testing to ensure application and system components interact properly. Users then conduct acceptance tests to ensure systems meet defined acceptance criteria. Testers often identify program defects or weakness during the testing process. Procedures should be in place to ensure programmers correct defects quickly and document all corrections or modifications. Correcting problems quickly increases testing efficiencies by decreasing testers downtime. It also ensures a programmer does not w aste time trying to debug a portion of a program without that is not working because another programmer has not debugged a defective linked routine. Documenting corrections and modifications is necessary to maintain the integrity of the overall program documentation. Organizations should review and complete user, operator and maintenance manuals during the testing phase. Additionally, they should finalize conversion, implementation and training plans. 82

Primary Tests Include:

Acceptance testing:
End users perform acceptance tests to assess the overall functionality and interoperability of an application.

End to end testing:

End users and system technicians perform end to end test to assess the interoperability of an application and other system components such as databases, hardware and software or communication devices.

Functional testing
End users perform functional tests to access the operability of a program against predefined requirements. Functional test include black box tests which assess the operational functionality of a feature against predefined expectations or white box testing which assess the functionality of a features code.

Integration testing
End users and system technicians perform integration tests to assess the interfaces of integrated software components.

Parallel testing
End users perform parallel tests to compare the output of a new application against a similar often the original application.

Regression testing
End users retest application to assess functionality after programmers make code changes to previously tested applications.

Stress testing
Technicians perform stress tests to assess the maximum limits of an application.

String testing
Programmers perform string tests to assess the functionality of related code modules.

System testing
Technicians perform system tests assess the functionality of an entire system.

Unit testing
Unit testing focuses verification on the smallest unit of software component or module. All the important control paths are tested to uncover errors with in the boundary of the module. 83

The programmer performs it. It uses the program specifications and the program itself as its source. Program specifications are used to verify that the program contains the logic to perform every function specified. It uses the program to test that the instructions execute correctly. Tests of data flow across a module interface are required before any test is initiated. It data does not enter and exit properly all other tests would become useless. Every module in our system has been tested to ensure that information properly flows into and out of the program unit under test. All independent paths through the control structure have been exercised to ensure that all statements have been executed at least once. Integrity of a temporary data throughout the execution of an algorithm has also been tested to be maintained.

84

Conclusion and Results

Provides benefits to survivors when an accident results in death.

It covers lawsuits, including legal fees brought against you as the result of an accident. Covers the bills of vehicle repairs due to damage caused in an accident. Covers damage caused by other than an accident for example, theft, fire, etc.

Convenient to be able to go online from the privacy of your own home and compare many auto insurance companies, their policies, and how much they charge for the premium. simplify the premium calculation and reimbursement of claims. help in customer retention before maturity of the policy.

help the administration of the organization to keep track of all policies, their maturity.

85

References
"Insurance Claim Quotes."Insurance Claim. Web. 11 Apr. 2012. <http://www.insurance.com/>. "Insurance Policy." Wikipedia. Wikimedia Foundation, 05 Apr. 2012. Web. 10 Apr. 2012. <http://en.wikipedia.org/wiki/Insurance_policy>. Schildt, Herbert. C# 4.0: The Complete Reference. New York: McGrawHill, 2010. Print. Shapiro, Jeffrey R. Microsoft SQL Server 2005: The Complete Reference. New York: McGraw-Hill, 2007. Print. Shukla, C., and A. Kumar. Barnwal. ASP.NET 2.0: Black Book. Scottsdale,AZ: Paraglyph, 2006. Web. "Web Development with Power, Productivity & Speed." Home : Official Microsoft Site. Web. 11 Apr. 2012. <http://www.asp.net/>. Williams, Mickey. Microsoft Visual C# .NET. Redmond, WA: Microsoft, 2002. Print.

86