SYNOPSIS

The project INSURANCE AGENT APPLICATION SYSTEM is designed using Microsoft Visual Studio.Net 2008 as front end and Microsoft SQL Server 200 as !ac" end. The coding language used is Visual #$ .Net.

1. INTRODUCTION
1.1 COMPANY PROFILE

1.2 PROJECT DESCRIPTION

2. SYSTEM ANALYSIS
2.1. EXISTING SYSTEM
The e%isting s&ste' is offline. The agents 'aintain polic& holders data in Microsoft (%cel. 2.1.1 DRAWBACKS OF EXISTING SYSTEM

The e%isting s&ste' has follo)ing disadvantages* More ti'e consu'ing for report generation. Send re'inders to all polic& holders are tough. #onsolidated reports can not !e prepared easil&. +ll ,nfor'ation cannot !e passed to polic& holders i''ediatel&.

2.2. PROPOSED SYSTEM

The proposed s&ste' is )e! oriented. The ne) approach helps in efficient process for their clients. The proposed s&ste' is to !e designed to overco'e all the pro!le's occurred in the e%isting s&ste'. 2.2.1 ADVANTAGES OF PROPOSED SYSTEM

The proposed s&ste' has follo)ing advantages* The polic& holders vie) all details through online. Less Ti'e #onsu'ing. +ccount su''ar& is possi!le at all ti'es. #onsolidated reports can !e prepared easil&.

2.3. SYSTEM SPECIFICATIONS

2.3.1. HARDWARE REQUIREMENTS This section gives the details and specification of the hard)are on )hich the s&ste' is e%pected to )or". -rocessor 2+M Monitor 0ard dis" 9e&!oard Mouse 2.3.2. SOFTWARE REQUIREMENTS This section gives the details of the soft)are that are used for the develop'ent. :perating S&ste' (nviron'ent .N(T @ra'e)or" 4evelop'ent Language 3ac"end . . . . . . >indo)s ?- -rofessional Visual Studio .N(T 2008 Version 2.0 +S-.Net #$.N(T MS SQL Server 200 . . . . . . -entiu' ,V 8// M01 2 / M3 S4 2+M 567 #olor 80 83 Standard502 "e&s L:8, T(#0 ;< 3uttons=

2.3.3. SOFTWARE SPECIFICATIONS THE .NET FRAMEWORK The .N(T @ra'e)or" is a ne) co'puting platfor' that si'plifies application develop'ent in the highl& distri!uted environ'ent of the ,nternet. OBJECTIVES OF .NET FRAMEWORK 5. To provide a consistent o!jectAoriented progra''ing environ'ent )hether o!ject codes is stored and e%ecuted locall& on ,nternetAdistri!uted* or e%ecuted re'otel&. 2. To provide a codeAe%ecution environ'ent to 'ini'i1es soft)are deplo&'ent and guarantees safe e%ecution of code. <. (li'inates the perfor'ance pro!le's. There are different t&pes of application* such as >indo)sA!ased applications and >e!A !ased applications. To 'a"e co''unication on distri!uted environ'ent to ensure that code !e accessed !& the .N(T @ra'e)or" can integrate )ith an& other code.

COMPONENTS OF .NET FRAMEWORK THE COMMON LANGUAGE RUNTIME CLR! The co''on language runti'e is the foundation of the .N(T @ra'e)or". ,t 'anages code at e%ecution ti'e* providing i'portant services such as 'e'or& 'anage'ent* thread 'anage'ent* re'oting and also ensures 'ore securit& and ro!ustness. The concept of code 'anage'ent is a funda'ental principle of the runti'e. #ode that targets the runti'e is "no)n as 'anaged code* )hile code that does not target the runti'e is "no)n as un'anaged code.

THE .NET FRAME WORK CLASS LIBRARY ,t is a co'prehensive* o!jectAoriented collection of reusa!le t&pes used to develop applications ranging fro' traditional co''andAline or graphical user interface ;8B,= applications to applications !ased on the latest innovations provided !& +S-.N(T* such as >e! @or's and ?ML >e! services. The .N(T @ra'e)or" can !e hosted !& un'anaged co'ponents that load the co''on language runti'e into their processes and initiate the e%ecution of 'anaged code* there!& creating a soft)are environ'ent that can e%ploit !oth 'anaged and un'anaged features. The .N(T @ra'e)or" not onl& provides several runti'e hosts* !ut also supports the develop'ent of thirdApart& runti'e hosts. ,nternet (%plorer is an e%a'ple of an un'anaged application that hosts the runti'e ;in the for' of a M,M( t&pe e%tension=. Bsing ,nternet (%plorer to host the runti'e to ena!les e'!eds 'anaged co'ponents or >indo)s @or's controls in 0TML docu'ents. FEATURES OF THE COMMON LANGUAGE RUNTIME The co''on language runti'e 'anages 'e'or&C thread e%ecution* code e%ecution* code safet& verification* co'pilation* and other s&ste' services these are all run on #L2. Securit& 2o!ustness -roductivit& -erfor'ance

SECURITY The runti'e enforces code access securit&. The securit& features of the runti'e thus ena!le legiti'ate ,nternetAdeplo&ed soft)are to !e e%ceptionall& feature rich. >ith regards to securit&* 'anaged co'ponents are a)arded var&ing degrees of trust* depending on a nu'!er of factors that include their origin to perfor' fileAaccess operations* registr&Aaccess operations* or other sensitive functions. ROBUSTNESS The runti'e also enforces code ro!ustness !& i'ple'enting a strict t&peA and codeA verification infrastructure called the co''on t&pe s&ste';#TS=. The #TS ensures that all 'anaged code is selfAdescri!ing. The 'anaged environ'ent of the runti'e eli'inates 'an& co''on soft)are issues. PRODUCTIVITY The runti'e also accelerates developer productivit&. @or e%a'ple* progra''ers can )rite applications in their develop'ent language of choice* &et ta"e full advantage of the runti'e* the class li!rar&* and co'ponents )ritten in other languages !& other developers. PERFORMANCE The runti'e is designed to enhance perfor'ance. +lthough the co''on language runti'e provides 'an& standard runti'e services* 'anaged code is never interpreted. + feature called justAinAti'e ;D,T= co'piling ena!les all 'anaged code to run in the native 'achine language of the s&ste' on )hich it is e%ecuting. @inall&* the runti'e can !e hosted !& highA perfor'ance* serverAside applications* such as MicrosoftE SQL ServerF and ,nternet ,nfor'ation Services ;,,S=.

DATA ACCESS WITH ADO.NET +s &ou develop applications using +4:.N(T* &ou )ill have different reGuire'ents for )or"ing )ith data. Hou 'ight never need to directl& edit an ?ML file containing data A !ut it is ver& useful to understand the data architecture in +4:.N(T. +4:.N(T offers several advantages over previous versions of +4:. ,nteropera!ilit& Maintaina!ilit& -rogra''a!ilit& -erfor'ance Scala!ilit&

INTEROPERABILITY +4:.N(T applications can ta"e advantage of the fle%i!ilit& and !road acceptance of ?ML. 3ecause ?ML is the for'at for trans'itting datasets across the net)or"* an& co'ponent that can read the ?ML for'at can process data. The receiving co'ponent need not !e an +4:.N(T co'ponent. The trans'itting co'ponent can si'pl& trans'it the dataset to its destination )ithout regard to ho) the receiving co'ponent is i'ple'ented. The destination co'ponent 'ight !e a Visual Studio application or an& other application i'ple'ented )ith an& tool )hatsoever. The onl& reGuire'ent is that the receiving co'ponent !e a!le to read ?ML. S:* ?ML )as designed )ith e%actl& this "ind of interopera!ilit& in 'ind.

MAINTAINABILITY ,n the life of a deplo&ed s&ste'* 'odest changes are possi!le* !ut su!stantial* +rchitectural changes are rarel& atte'pted !ecause the& are so difficult. +s the perfor'ance load on a deplo&ed application server gro)s* s&ste' resources can !eco'e scarce and response ti'e or throughput can suffer. @aced )ith this pro!le'* soft)are architects can choose to divide the serverIs !usinessAlogic processing and userAinterface processing onto separate tiers on separate 'achines. ,n effect* the application server tier is replaced )ith t)o tiers* alleviating the shortage of s&ste' resources. ,f the original application is i'ple'ented in +4:.N(T using datasets* this transfor'ation is 'ade easier. +4:.N(T data co'ponents in Visual Studio encapsulate data access functionalit& in various )a&s that help &ou progra' 'ore Guic"l& and )ith fe)er 'ista"es. PERFORMANCE +4:.N(T datasets offer perfor'ance advantages over +4: disconnected record sets. ,n +4:.N(T dataAt&pe conversion is not necessar&. SCALABILITY +4:.N(T acco''odates scala!ilit& !& encouraging progra''ers to conserve li'ited resources. +n& +4:.N(T application e'plo&s disconnected access to dataC it does not retain data!ase loc"s or active data!ase connections for long durations.

VISUAL STUDIO .NET

Visual Studio .N(T is a co'plete set of develop'ent tools for !uilding +S- >e! applications* ?ML >e! services* des"top applications* and 'o!ile applications ,n addition to !uilding highAperfor'ing des"top applications* &ou can use Visual StudioIs po)erful co'ponentA!ased develop'ent tools and other technologies to si'plif& tea'A!ased design* develop'ent* and deplo&'ent of (nterprise solutions. Visual 3asic .N(T* Visual #JJ .N(T* and Visual #$ .N(T all use the sa'e integrated develop'ent environ'ent ;,4(=* )hich allo)s the' to share tools and facilitates in the creation of 'i%edAlanguage solutions. ,n addition* these languages leverage the functionalit& of the .N(T @ra'e)or" and si'plif& the develop'ent of +S- >e! applications and ?ML >e! services. Visual Studio supports the .N(T @ra'e)or"* )hich provides a co''on language runti'e and unified progra''ing classesC +S-.N(T uses these co'ponents to create +S- >e! applications and ?ML >e! services. +lso it includes MS4N Li!rar&* )hich contains all the docu'entation for these develop'ent tools. VISUAL BASIC .NET Visual 3asic .N(T* the latest version of visual !asic* includes 'an& ne) features. The Visual 3asic supports interfaces !ut not i'ple'entation inheritance. Visual !asic.net supports i'ple'entation inheritance* interfaces and overloading. ,n addition* Visual 3asic .N(T supports 'ultithreading concept. COMMON LANGUAGE SPECIFICATION CLS! Visual 3asic.N(T is also co'pliant )ith #LS ;#o''on Language Specification= and supports structured e%ception handling.

#LS is set of rules and constructs that are supported !& the #L2 ;#o''on Language 2unti'e=. #L2 is the runti'e environ'ent provided !& the .N(T @ra'e)or"C it 'anages the e%ecution of the code and also 'a"es the develop'ent process easier !& providing services. Visual 3asic.N(T is a #LSAco'pliant language. +n& o!jects* classes* or co'ponents that created in Visual 3asic.N(T can !e used in an& other #LSAco'pliant language. ,n addition* )e can use o!jects* classes* and co'ponents created in other #LSAco'pliant languages in Visual 3asic.N(T .The use of #LS ensures co'plete interopera!ilit& a'ong applications* regardless of the languages used to create the application. GARBAGE COLLECTION 8ar!age #ollection is another ne) feature in Visual 3asic.N(T. The .N(T @ra'e)or" 'onitors allocated resources* such as o!jects and varia!les. ,n addition* the .N(T @ra'e)or" auto'aticall& releases 'e'or& for reuse !& destro&ing o!jects that are no longer in use. ,n Visual 3asic.N(T* the gar!age collector chec"s for the o!jects that are not currentl& in use !& applications. >hen the gar!age collector co'es across an o!ject that is 'ar"ed for gar!age collection* it releases the 'e'or& occupied !& the o!ject. OVERLOADING :verloading is another feature in Visual 3asic.N(T. :verloading ena!les us to define 'ultiple procedures )ith the sa'e na'e* )here each procedure has a different set of argu'ents. 3esides using overloading for procedures* )e can use it for constructors and properties in a class.

BACK END
FEATURES OF SQL"SERVER M#$%&'&() SQL S*%+*% is a relational 'odel data!ase server produced !& Microsoft. ,ts pri'ar& Guer& languages are TASQL and +NS, SQL.The :L+- Services feature availa!le in SQL Server version 6.0 is no) called SQL Server 200 +nal&sis Services. The ter' :L+Services has !een replaced )ith the ter' +nal&sis Services. +nal&sis Services also includes a ne) data 'ining co'ponent. The 2epositor& co'ponent availa!le in SQL Server version 6.0 is no) called Microsoft SQL Server 200 Meta 4ata Services. 2eferences to the co'ponent no) use the ter' Meta 4ata Services. The ter' repositor& is used onl& in reference to the repositor& engine )ithin Meta 4ata Services. MicrosoftE SQL ServerF 200 features include. I,)*%,*) I,)*-%.)#&, The SQL Server 200 data!ase engine includes integrated ?ML support. ,t also has the scala!ilit&* availa!ilit&* and securit& features reGuired to operate as the data storage co'ponent of the largest >e! sites. The SQL Server 200 progra''ing 'odel is integrated )ith the >indo)s 4N+ architecture for developing >e! applications* and SQL Server 200 supports features such as (nglish Quer& and the Microsoft Search Service to incorporate userAfriendl& Gueries and po)erful search capa!ilities in >e! applications. S$./.0#/#)1 .,2 A+.#/.0#/#)1 The sa'e data!ase engine can !e used across platfor's ranging fro' laptop co'puters running Microsoft >indo)sE K8 through large* 'ultiprocessor servers running Microsoft >indo)s 2000 4ata #enter (dition. SQL Server 200 (nterprise (dition supports features such as federated servers* inde%ed vie)s* and large 'e'or& support that allo) it to scale to the perfor'ance levels reGuired !& the largest >e! sites.

E,)*%3%#'*"L*+*/ D.).0.'* F*.)4%*' The SQL Server 200 relational data!ase engine supports the features reGuired to support de'anding data processing environ'ents. The data!ase engine protects data integrit& )hile 'ini'i1ing the overhead of 'anaging thousands of users concurrentl& 'odif&ing the data!ase. SQL Server 200 distri!uted Gueries allo) &ou to reference data fro' 'ultiple sources as if it )ere a part of a SQL Server 200 data!ase* )hile at the sa'e ti'e* the distri!uted transaction support protects the integrit& of an& updates of the distri!uted data. 2eplication allo)s &ou to also 'aintain 'ultiple copies of data* )hile ensuring that the separate copies re'ain s&nchroni1ed. Hou can replicate a set of data to 'ultiple* 'o!ile* disconnected users* have the' )or" autono'ousl&* and then 'erge their 'odifications !ac" to the pu!lisher. E.'* &( #,').//.)#&,5 2*3/&16*,)5 .,2 4'* SQL Server 200 includes a set of ad'inistrative and develop'ent tools that i'prove upon the process of installing* deplo&ing* 'anaging* and using SQL Server across several sites. SQL Server 200 also supports a standardsA!ased progra''ing 'odel integrated )ith the >indo)s 4N+* 'a"ing the use of SQL Server data!ases and data )arehouses a sea'less part of !uilding po)erful and scala!le s&ste's. These features allo) &ou to rapidl& deliver SQL Server applications that custo'ers can i'ple'ent )ith a 'ini'u' of installation and ad'inistrative overhead. D.). 7.%*8&4'#,SQL Server 200 includes tools for e%tracting and anal&1ing su''ar& data for online anal&tical processing. SQL Server also includes tools for visuall& designing data!ases and anal&1ing data using (nglishA!ased Guestions. There is no feature to process the tas" and 'anage the records through all nodes and save the records in server. The soft)are used to solve the pro!le' and develop the application is Microsoft Visual Studio.Net )ith V3 as progra''ing language and MSASQL Server 200

3. SYSTEM DESIGN
3.1. INPUT DESIGN
,nput design is the process of converting userAoriginated inputs to a co'puter understanda!le for'at. ,nput design is one of the 'ost e%pensive phases of the operation of co'puteri1ed s&ste' and is often the 'ajor pro!le' of a s&ste'. + large nu'!er of pro!le's )ith a s&ste' can usuall& !e trac"ed !ac"s to fault input design and 'ethod. (ver& 'o'ent of input design should !e anal&1ed and designed )ith ut'ost care.

The design of the input should !e 'ade the input as the over to the nu'erous net)or"s in the relia!le area that should !e passed as the installation in the re'ote net)or". ,t has the follo)ing constraints in the input data!ase.

+ll the files fro' the dis" should !e acGuired !& data. ,t is suita!le to 'ore availa!le data clearance and 'ade availa!le. The 'enu of design should !e understanda!le and it is in the right for'at.

The s&ste' ta"es input fro' the users* processes it and produces an output. ,nput design is lin" that ties the infor'ation s&ste' into the )orld of its users. The s&ste' should !e userA friendl& to gain appropriate infor'ation to the user. The decisions 'ade during the input design are*

The project gives the lo) ti'e consu'ption to 'a"e the sensitive application 'ade si'ple. >hen appl&ing the project it provides the lo) 'anApo)er attrition )ith the reasona!le output. The a'ount of fund that the co'pan& can spend into the research and develop'ent of the s&ste' is li'ited. The e%penditures 'ust !e justified. Thus the developed s&ste' as )ell

)ithin the !udget and this )as achieved !ecause 'ost of the technologies used are freel& availa!le. :nl& the custo'i1ed products had to !e purchased.

,n this s&ste' 'ainl& used to protect the s&ste' and files giving file path input option. Mail sending utilit& input as sends the ('ail to recipient )ith attach'ent. S&ste' anal&sis decide the follo)ing input design details li"e* )hat data to input* )hat 'ediu' to use* ho) the data should !e arranged or coded* data ite's and transactions needing validations to detect errors and at last the dialogue to guide user in providing input.

,nput data of a s&ste' 'a& not !e necessaril& is ra) data captured in the s&ste' fro' scratch. These can also !e the output of another s&ste' or su!s&ste'. The design of input covers all the phases of input fro' the creation of initial data to actual entering of the data to the s&ste' for processing. The design of inputs involves identif&ing the data needed* specif&ing the characteristics of each data ite'* capturing and preparing data fro co'puter processing and ensuring correctness of data.

,nput design is the process of converting userAoriginated inputs to a co'puterA!ased for'at. ,nput design is one of the 'ost e%pensive phases of the operation of co'puteri1ed s&ste' and is often the 'ajor pro!le' of a s&ste'.

+n& +'!iguit& in input leads to a total fault in output. The goal of designing the input data is to 'a"e data entr& as eas& and error free as possi!le.

,n the project* the for's are designed )ith eas& to use options such as selecting the 'aster records through dropdo)nlist in transaction for's. The coding is !eing done such that proper validations are 'ade to get the perfect input. No error inputs are accepted. The end users need not to give the id the'selves.

3.2. OUTPUT DESIGN

:utput design generall& refers to the results and infor'ation that are generated !& the s&ste' for 'an& endAusersC it should !e understanda!le )ith the enhanced for'at. The :utput of the soft)are is used to 'a"e the re'ote installation of the ne) soft)are in the s&ste' and* it is a)a"e the i''ediate alert to the s&ste' that should !e enhanced it as the input to the s&ste'. :utput is the 'ain reason for developing the s&ste' and the !asis on )hich the& evaluate the usefulness of the application. #o'puter output is the 'ost i'portant direct source of infor'ation to the user output design deals )ith for' design efficient output design should i'prove the interfacing )ith user. The ter' output applies to an& infor'ation produced !& an infor'ation s&ste' in ter's of displa&ed. >hen anal&st design s&ste' output* the& ,dentif& the specific output that is needed to 'eet the reGuire'ents of end user. -revie)ing the output reports !& the user is e%tre'el& i'portant !ecause the user is the ulti'ate judge of the Gualit& of the output and* in turn* the success of the s&ste' >hen designing output* s&ste' anal&sis acco'plishes 'ore things li"e* to deter'ine )hat applications* )e!sites or docu'ents )hether !loc"ed or allo)ed. +llo)ing should !e in various options. The output is designed in such a )a& that it is attractive* convenient and infor'ative. @or's are designed in V3.N(T )ith various features* )hich 'a"e the console output 'ore pleasing. +s the outputs are the 'ost i'portant sources of infor'ation to the users* !etter design should i'prove the s&ste'Ls relationships )ith user and also )ill help in decisionA 'a"ing. @or' design ela!orates the )a& output is presented and the la&out availa!le for capturing infor'ation. +s the outputs are the 'ost i'portant sources of infor'ation to the users* !etter design should i'prove the s&ste'Ls relationships )ith user and also )ill help in decisionA'a"ing. @or' design ela!orates the )a& output is presented and the la&out availa!le for capturing infor'ation. ,n the project* the custo'ers list* De)el stoc" updated list* order reGuests* transactions such as orders approved and pa&'ent received are displa&ed in grid vie) controls. The reports are prepared !ased on De)el categor& or !et)een t)o specified dates on reGuire'ent.

3.3. DATABASE DESIGN

3.3.1 DATA FLOW DIAGRAM

+d'in

+d'in

0ealthpla n (ntr&

childplan (ntr&

0ouseplan (ntr&

Life ,nsurance (ntr&

Vehicle ,nsurance (ntr&

2etire'ent plan (ntr&

healthplan

chaildplan

houseplan

insurance

vehicle

retier'ent

3.3.2 TABLE STRUCTURE WITH DESCRIPTION

9. TESTING .,2 IMPLEMENTATION

SYSTEM TESTING

+fter the source code has !een co'pleted and docu'ented as related data structures. #o'pleted the project has to undergo testing and validation )here there is su!title and definite atte'pt to get errors. The project developer treads lightl&* designing and e%ecution test that )ill de'onstrates that the progra' )or"s rather than uncovering errors* unfortunatel& errors )ill !e present and if the project developer doesnLt find the'* the user )ill find out. The project developer is al)a&s responsi!le for testing the individual units i.e. 'odules of the progra'. ,n 'an& cases developer also conducts integration testing i.e. the testing step that leads to the construction of the co'plete progra' structure. This project has undergone the follo)ing testing procedures to ensure its correctness. Bnit testing ,ntegration testing Validation testing Bser +cceptance Testing

UNIT TESTING

,n unit testing* )e have to test the progra's 'a"ing up the s&ste'. @or this reason* Bnit testing so'eti'es called as -rogra' testing. The soft)are units in a s&ste' are the 'odules and routines that are asse'!led and integrated to perfor' a specific function* Bnit testing first on the 'odules independentl& of one another* to locate errors. This ena!les* to detect errors in coding and logic that are contained )ith the 'odule alone. The testing )as carried out during progra''ing stage itself. The testing is carried out ever& 'odules such as plan 'odule* pre'iu' calculator* loan* clai' and report of the ,nsurance activities. The project source code is perfectl& error free and it is )or"ing as efficient.

INTEGRATION TESTING:

,ntegration testing is a s&ste'atic techniGue for constructing the progra' structure. >hile at the sa'e ti'e conducting tests to uncover errors associated )ith interfacing. The o!jective is to ta"e unit tested 'odules and !uild a progra' structure that has !een dictated !& design. ,n this integration testing its done using the 'ain 'odule and plan 'odule* pre'iu' calculator* loan* clai' and report of the ,nsurance activities are !ased on the t&pe of integration testing the su!ordinate stu!s are replaced one at a ti'e )ith actual 'odules.

VALIDATION TESTING:

,n the project Validation is 'ade )hile enter the phone nu'!er in the corresponding te%t!o% control* it !e validated. The te%t!o% 'a%length propert& is set and validated during this testing.

USER ACCEPTANCE TESTING:

,n these testing procedures the project is given to the user to test )hether all reGuire'ents have !een fulfilled and satisfied. ,f the user 'a"es reGuest for an& change and if the& found an& errors* those errors has to !e ta"en into consideration and to !e correct it to 'a"e the project as a perfect project.

SYSTEM IMPLEMENTATION

>hen the initial design )as done for the s&ste'* the client )as consulted for the acceptance of the design so that further proceedings of the s&ste' develop'ent can !e carried on. +fter the develop'ent of the s&ste' a de'onstration )as given to the' a!out the )or"ing of the s&ste'. The ai' of the s&ste' illustration )as to identif& an& 'alfunction of the s&ste'. +fter the 'anage'ent of the s&ste' )as approved the s&ste' i'ple'ented in the concern* initiall& the s&ste' )as run parallel )ith e%isting 'anual s&ste'. The s&ste' has !een tested )ith live data and has proved to !e error free and user friendl&. ,'ple'entation is the process of converting a ne) or revised s&ste' design into an operational one )hen the initial design )as done !& the s&ste'C a de'onstration )as given to the end user a!out the )or"ing s&ste'. This process is uses to verif& and identif& an& logical 'ess )or"ing of the s&ste' !& feeding various co'!inations of test data. +fter the approval of the s&ste' !& !oth end user and 'anage'ent the s&ste' )as i'ple'ented. S&ste' i'ple'entation is 'ade up of 'an& activities. The si% 'ajor activities as follo)s.

C&2#,#oding is the process of )here!& the ph&sical design specifications created !& the anal&sis tea' turned into )or"ing co'puter code !& the progra''ing tea'.

T*')#,:nce the coding process is !egin and proceed in parallel* as each progra' 'odule can !e tested.

I,').//.)#&,
,nstallation is the process during )hich the current s&ste' is replaced !& the ne) s&ste'. This includes conversion of e%isting data* soft)are* and docu'entation and )or" procedures to

those consistent )ith the ne) s&ste'.

D&$46*,).)#&,
,t is result fro' the installation process* user guides provides the infor'ation of ho) to use the s&ste' and its flo).

T%.#,#,- .,2 '433&%)

Training plan is a strateg& for training user so the& Guic"l& learn ne) s&ste'. The develop'ent of the training plan pro!a!l& !egan earlier in the project.

;. CONCLUSION AND FUTURE ENHANCEMENT

The end users are reGuired to have !asic co'puter "no)ledge to run this soft)are. The application is tested )ell so that the end users satisfaction is found to !e 'ore.

To 'ini'i1e the ti'e consu'ption and clerical )or" of the ,nsurance activities. The co'puteri1ed s&ste's )ill faster and easier. The reports )ill have the +ccurac& and error free calculation and st&lish* neat and clear presentation.

FUTURE ENHANCEMENT
The project provides a !est assistance in the net)or" !ased regi'e. ,t allo)s adding up the follo)ing facilities in future* The custo'er pre'iu' details are sent to the ad'inistrator through 'ail. :ffering ne) plans details are sent to the corresponding custo'er 'o!ile.

This allo)s the clients to send hisMher feed!ac".

<. BIBLIOGRAPHY
Deffre& 2.Shapiro ASP.NET: T8* C&63/*)* R*(*%*,$*7 Tata Mc8ra)A0ill -u!lishing #o'pan& Li'ited* 2002. 4ave Mercer7ASP.NET: B*-#,,*%=' -4#2*7 Tata Mc8ra) A0ill -u!lishing #o'pan& Li'ited* 2002. 2oger S .-ress'an 7S&()7.%* E,-#,**%#,-LN Mc8ra)A0ill -u!lications

(ilas M.+)ad 7S1')*6 A,./1'#' A,2 D*'#-,7 8alogoeia pu!lications;p=Ltd* lKK2*2L (dition.

WEB SITES http.MM))).'icrosoft.co'MdotnetMvisual !asic http.MM))).dotnetheaven.co' http.MM))).google.co' http.MM))).sunnet.co'

APPENDICES
A. SCREEN SHOTS HOME PAGE

B.

REPORTS