[attachment=2433]

INSURANCE AGENT'S COMMISSION TRACKING
SYSTEM
MINI PROJECT REPORT
Submitted by
ANITHA.T.S GANGA JYOTHI
SAJITH.O.B YADHU.S.NAIR
ABSTRACT
An insurance company mainly deals with providing insurance to its customers like life time insurance, endowment insurances etc. the sales force of an insurance company comprises of a branch manager, sales manager, unit managers who are employees of the company and a team of advisors or agents who work on a commission basis. Agents working under unit managers play a key role in generating the business. Agents distribute policies to the clients and for every policy that is accepted, agent will be paid a certain sum as commission by the company.
In the Insurance Agents Commission Tracking Project, the project actually keeps track of the commission paid to the agents. The details of the commission are stored in a database which is updated regularly.
Project include two modules Insurance Company Module(ICM) and Insurance Agent Module(IAM).In the ICM, the employee of the insurance company manages details of the agents which includes recruitment, training and business generation. ICM could be used by authorized personnel of the company to accept or reject policies logged in by agents. In the IAM, the agent logs in the details of the policies sold by him. He is also able to track the status of policies issued. Agent could get the details of the commissions payable to him by the company.
TABLE OF CONTENTS
CHAPTER TITLE PAGE NO
LIST OF TABLES vii
LIST OF FIGURES Viii
1 INTRODUCTION 1
1.1 ABOUT THE PROJECT 1
2 SYSTEM STUDY 3
2.1 EXISTING SYSTEM 3
2.2 STUDY AND ANALYS THE
4
BUSINESS NEEDS
2.3 FEASIBILITY STUDY 4
2.3.1 TECHNICAL FEASIBILITY 4
2.3.2 OPERATIONAL FEASIBILITY 5
2.3.3 ECONOMICAL FEASIBILITY 5
2.4 SELECTION OF RESOURCES 5
2.4.1 HARDWARE REQUIREMENTS 5
2.4.2 SOFTWARE REQUIREMENTS 6
2.4.3 FRONT END 6
2.4.4 BACK END 7
3 SYSTEM DESIGN 8
3.1 INTRODUCTION 8
3.2 INPUT DESIGN 8
CHAPTER TITLE PAGE NO
3.3 INPUT VALIDATION 9
3.4 OUTPUT DESIGN 9
3.5 FILE DESIGN 9
3.6 DATABASE DESIGN 10 3.6.1 DATAFLOW DIAGRAM 11
3.7 OUTPUT SCREEN DESIGN 12
3.8 MENU DESIGN 12
3.9 TABLE DESIGN 12
4 CODING 18
4.1 FEATURES OF LANGUAGE 18
5 SYSTEM IMPLEMENTATION & TESTING 23
5.1 SYSTEM IMPLEMENTATION 23
5.2 SYSTEM TESTING 23
5.3 SYSTEM CHANGEOVER 24
5.4 SYSTEM SECURITY & MAINTAINACE 24
5.5 LIST OF FIGURES 25
6 CONCLUSION 33
APPENDICES 34
RESUME 36
REFERENCES 37
LIST OF TABLES
TABLE TABLE NAME PAGE
3.8.1 COMMISSION DETAILS 13
3.8.2 COMPANY DETAILS 13
3.8.3 CUSTOMER DETAILS 14
3.8.4 EMPLOYEE DETAILS 14
3.8.5 FIRST COMMISSION 15
3.8.6 NOMINEE REGISTER 15
3.8.7 POLICY MASTER 16
3.8.8 POLICY REGISTER 16
3.8.9 PREMIUM REGISTER 17
LIST OF FIGURES
FIGURE FIGURE NAME PAGES
3.1 LEVEL ZERO DFD 11
3.2 LEVEL ONE DFD 11
5.1 LOGIN FORM 25
5.2 USER DETAILS 26
5.3 CUSTOMER DETAILS 27
5.4 NOMINEE DETAILS 27
5.5 PLICY DETAILS 27
5.6 CHANGE PASSWORD 28
5.7 COMPANY DETAILS 28
5.8 PLICY APPROVAL 29
5.9 POLICY AUTHORIZATION 29
5.10 USER AUTHORIZATION 30
5.11 VIEW USERS 30
5.12 VIEW POLICIES 31
5.13 COMMISSION TRACKING 31
5.14 PREMIUM PAYMENT 32
CHAPTER 1
INTRODUCTION
1.1 ABOUT THE PROJECT
The main objective of the project, Insurance Agent's Commission Tracking System, is to track the commission paid to agent by an insurance company. The commission may vary according to the different types of policies, duration etc.
To make the task easy, the project has been divided into two modules.
1. Insurance Company Module
2. Insurance Agent Module
¢ Insurance Company Module:
Insurance company module mainly deals with the working of the company. The company module is based on a hierarchy which is rooted at the general manager .At the leaf end of the hierarchy we have the policy owners, customers. The other nodes of the hierarchy are sales mangers, unit managers and agents. Each node of this hierarchy has been assigned different functions.
General manager has the supreme authority of the entire system. Under him all other nodes of hierarchy comes.
Sales manager coordinates other levels of company. Sales manager is responsible for adding different users such as agents, unit managers. Sales manager authorize new policies . Processing of reports such as agent commission report, commission per policy reports have been done by sales manager. By referring the policy register table sales manager can evaluate the performance of himself, unit manager, and agents. Blocking of different policies, different users can be done by sales manager.
Unit manager controls all the agents under him. Tracking commission is done by the unit manager by considering the premium register table and policy register table. Unit manager can view the performance of each unit and each independent agent by referring the policy register table. Policies sold by different agents can be viewed by the unit manager. Payment done by different policy owners has been done by the unit manager.
Tracking commission:
1. First Commission Tracking
2. Second Commission Tracking.
First Commission is paid by the company to an agent if a new policy has been sold by the agent. Second Commission is paid each time the premium is paid by the policy owner. Second Commission is paid according to the premium getting through the policies sold by each agent.
After the policy has been completed the commission will be stopped.
¢ Insurance Agent Module:
In the IAM, the agent logs in the details of the policies sold by him. Agents are responsible for selling different policies to customers. They are paid commission according to the no: of policies sold, amount, and premium amount. He can view different reports . Agents can check whether their customers are paying premium in date by premium register table.
Insurance Agent Commission Tracking system is a correlation of these
two modules.
CHAPTER 2 SYSTEM STUDY
2.1 EXISTING SYSTEM
Once upon a time software development consisted of a programmer writing code to solve a problem or automate a procedure. Nowadays, systems are so big and complex that teams of architects, analysts, programmers, testers and users must work together to create the millions of lines of custom written code that drive our enterprises.
To manage this, a number of system development life cycle (SDLC) models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and synchronize and stabilize.
The oldest of these and the best known, is the waterfall: a sequence of stages in which the output of each stage becomes the input for the next. These stages can be characterized and divided up in different ways, including the following.
¢ Project planning, feasibility study: Establishes a high level view of the intended project and determines its goals.
¢ Systems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyses end user information needs.
¢ Systems design: Describes desired features and operations in details including screen layout, business rules, process diagrams, pseudo code and other documentation.
¢ Implementation: The real code is written here.
¢ Integration and testing: Brings all the paths together into a special testing environment, then checks for errors, bugs and interoperability.
¢ Acceptance, installation, deployment: The final stage of initial development where the software is put into production and runs actual business.
¢ Maintenance: What happens during the rest of the software's life - changes, correction, addition and moves to a different computing platform. This, the least glamorous and perhaps the most important step of all, goes on seemingly forever.
2.2 STUDY AND ANALYSE THE BUSINESS NEEDS
The project team supplemented by enterprise architecture or other technical experts if needed should analyze all feasible technical, business process, and commercial alternatives to meeting the business need. The alternatives should then be analyzed from a lifecycle cost perspective. The results of these studies should show a range of feasible alternatives based on lifecycle cost, technical capability, and scheduled availability. Typically, these studies should narrow the system technical approaches to only a few potential, desirable solutions that should proceed into the subsequent lifecycle phases.
The project team should develop high-level(baseline) schedule, cost, the performance measures which are summarized in the System Boundary Document. These high-level estimates are further refined in subsequent phases.
The acquisition strategy should be included in the SBD. The project team should determine the strategies to be used during the remainder of the project concurrently with the development of the CBA and feasibility study.
2.3 FEASIBILITY STUDY
Feasibility study is done by investigating the existing system in the area under investigation and generating idea about a new system. In the preliminary investigation there are three aspects of feasibility study. They are
¢ Technical feasibility
¢ Functional feasibility
¢ Economical feasibility
2.3.1 TECHNICAL FEASIBILITY
. It is the study of functional performance and constraint that may affect the ability to achieve an acceptable system. Technical feasibility centers on the existing system and what extent it can support the proposed system. C#.Net technique guarantee accuracy, reliability, ease of access and data security. Using C# it is relatively easier to construct and maintain windows applications.
2.3.2 OPERATIONAL FEASIBILITY
The proposed system is beneficial because it enables a person to purchase books sitting at his own workplace. A careful study is made about the feasibility of the system and final report of the study, that is, a feasibility report is maintained.
2.3.3 ECONOMICAL FEASIBILITY
The economical feasibility of the system is conducted to find out an estimate of the cost and time that will be incurred in constructing the system. This project was developed within a time span of two months at a reasonable cost with the available hardware.
2.4 SELECTION OF RESOURCES
2.4.1 HARDWARE REQUIREMENTS
PROCESSOR CLOCK SPEED SYSTEM BUS RAM HDD
MONITOR KEY BOARD MOUSE FDD
PENTIUM IV/AMD 500 MHZ
32 BIT
256 MB OR MORE
40 GB OR MORE SVGA COLOR
108 KEYS
LOGITECH 1.44 MB
2.4.2 SOFTWARE REQUIREMENTS
OPERATING SYSTEM PLATFORM FRONT END BACK END
WINDOWS XP/VISTA VISUAL STUDIO 2005 C# .NET
MS SQL SERVER 2005
2.4.3 FRONT END
¢ Introduction to .Net Framework:
.Net is a new set of technologies released from Microsoft Corporation. Microsoft published a white paper on these technologies by 1997. The .Net technology is one
of the most powerful and future oriented technologies based on the Internet. The entire concept of a .Net is built around the tool .Net framework. The .Net framework is the tool which contains the entire technology of .Net. All the future development of Microsoft tools(like MS office, SQL Server 2005) and Operating systems(long Horn Project) are based on .Net technology.
With the innovation of .Net Technology the Microsoft tools have crossed one of the main barriers of Platform independency issue. The architecture of .Net tools are designed in such a way that it can be made platform independent instead of depending on the Windows Operating system only as the previous Microsoft products used to do.
¢ C# language:
The C# is a newly introduced language by Microsoft. The languages combine the features of Java and C language and helps even Java and C programmers to switch to Microsoft Tools. The language was not noticed initially when the project was launched. But as the time progressed the language's popularity has grown a lot. Today C# is considered one of the industry standard languages by developers all over the world. The study conducted by various groups show that by end of year 2007 the total number of c# developers cross the total number of VB.Net developers all over the world. The language also attracts a lot of people from Java and C programming fields also due to the similarity in syntax and development styles of the C# language. Object Orientation is considered to be the buzzword of future programming. C# is a language which supports Object Orientation to the maximum development. The entire C# architecture is supporting Object Oriented features.
2.4.4 BACK END
SQL Server 2005 exceeds dependability requirements and provides innovative capabilities that increase employ effectiveness, integrate heterogeneousness. It ecosystems, and maximize capital and operating budgets. SQL Server 2005 provides the enterprise data management platform the organization needs to adapt quickly in a fast-changing environment.
With the lowest implementation and maintenance costs in the industry, SQL Server 2005 delivers rapid return on the data management investment. SQL Server 2005 supports the rapid development of enterprise-class business applications that can give the company a critical competitive advantage.
Benchmarked for scalability, speed, and performance, SQL Server 2005 is a fully enterprise-class database product, providing core support for Extensible Markup Language (XML) and Internet queries.
Revolutionary self tuning and dynamic self-configuring features optimize database performance, while management tools automate standard activities. Graphical tools and wizards simplify setup, database design and performance monitoring, allowing database administrators to focus on strategic business needs.
Unlike its competitors, SQL Server 2005 provides a powerful and comprehensive data management platform. Every software license includes extensive management and development tools, a powerful extraction, transformation, and loading (ETL)tool, business intelligence and analysis services, and new capabilities such as Notification Services. The result is the best overall business value available.
CHAPTER 3 SYSTEM DESIGN
3.1 INTRODUCTION
Design should improve the system's relationship with the user and help in decision-making. It is primarily required to communicate the user's input from client side to the server where a program will be run to process the input. Once the output requirements are determined, the system design can decide what to include in the system.
The most creative and challenging phase of the system life cycle is system design. System design is a process of developing specifications for a candidate system that meet the criteria established in the system analysis. Design requires a full understanding of the problem and hence there is need for analysis of requirement and resources. The acceptable design is likely to be a compromise among a number of factors particularly cost, reliability, accuracy, security, control, integration, and expandability.
The first step is to determine how the output is to be produced and in what format. Samples of output and the input are also presented. Second, input data and the database have to be designed to meet the requirement of the proposed output.
3.2 INPUT DESIGN
Input design determines the format and validation criteria for data entering in the system. It is a process of converting a user-oriented description of the inputs to a computer-based format. It is the point of contact for the user with the computer system. Several activities have to be carried out as part of the overall input process. They are data recording, data transcription, data verification, data control, data transmission, data validation and data correction. The following features have been incorporated into the input design of the proposed system.
¢ User Friendliness
User is left in a state of confusion as to what is happening. The overall look of the site is simple yet attractive.
¢ Easy Navigation
Appropriate links are provided appropriately so that the user can easily reach the desired destination
¢ Consistent Format
A consistent look and feel is maintained throughout the site.
¢ Security
A high level of security is maintained which prevents misuse of login accounts.
3.3 INPUT VALIDATION
The entered data is checked for accuracy by using different techniques. This is done to identify whether the data is acceptable or not. Duplicated data will not be accepted. Input is checked to determine whether the fields contain only valid data. Rejecting different details for the same number is analogue to their fact. Many computer systems have software packages that assist in the design and documentation process.
3.4 OUTPUT DESIGN
The output design is how to structure it so that the required output can be produced. For the proposed software it is necessary that output reports be compatible in format with the manual reports. The success or failure of software is decided by the integrity and correctness of the output that is produced from the system. One of the main objective behind the automation of business systems itself is the fast and prompt generation of reports in a short time period. In today's competitive world of business it is very important for companies to keep themselves up-to-date about the happenings in the business. Prompt and reliable reports are considered to be the lifeline of every business today. At the same time wrong reports can shatter the business itself and create huge and irreparable losses for the business. So the outputs/reports generated by the software systems are of paramount importance.
3.5 FILE DESIGN
After designing the input output, the designer begins to concentrate on file design or how data should be organized around the user requirements. How data are organized depends on the data and responses requirements that determine hardware configurations. Files can be mainly classified in to two types:-Master files and Transaction files. Master files as maintained throughout life cycle of the organization and the file contain permanent records of the system. Transaction files are temporary in nature and its main purpose is to update the master file.
3.6 DATABASE DESIGN
A Database is collections of interrelated data stored with a minimum of redundancy to serve much application. Instead of each program or user managing its own data, authorized users share data across applications with the database software managing the data as entity. Database design is one of the important parts in developing software. It is a process of developing conceptual model of data. Primary objectives of database design are: -
¢ Fast response time to inquiries.
¢ More information at low cost.
¢ Control of redundancy.
¢ Clarity and ease of use.
¢ Fast recovery.
¢ Privacy and security of information.
For designing a table the analyst must decide the fields of the tables, type of the fields, the field length, default values etc. For this first the entity and relationship must be identified, second their attributes must be specified. The method of organizing the data into table is known as Normalization. The six normalization rules are: -
1NF : - Each row or column must have a single value with no repeating values 2NF : - Each non-key column must depend on the primary key column. 3NF : - No non-key column can depend on another non-key column BCNF : - No attribute of a composite key can depend on the attribute of another composite key.
4NF :- An entity cannot have a 1:1 relationship between primary key columns. 5NF :- Break all tables into smallest possible pieces to eliminate all redundancy within a table.
In this project the database used is MS SQL Server 2005. The database contains nine tables. To avoid redundancy of data and easier manipulation of data the tables are normalized so as it can be efficiently used.
Fig: 3.2 Level One DFD
3.7 OUTPUT SCREEN DESIGN
Computer output is the most important and direct source of the information of the user. Output design is a process that involves designing necessary outputs in the form of reports that should be given to users according to their requirements. Efficient, intelligent output design should improve the system's relationship with the user and also help in decision making. Since the management for taking decision directly refers the reports and to draw conclusions, they must be designed with almost care and the details in the reports must be simple, descriptive and clear to the user.
Depending on the nature and future use of output required, they can be displayed on the monitor for immediate need and for obtaining the hard copy. The options for the output reports are given in the system's menu.
3.8 MENU DESIGN
There is a main window, which contain main menu. By using the appropriate menu option we select screens or windows for input data entry. Access protection is achieved through the password. The user can enter in to the main window only by giving the correct user name and password. One can login as a user.
¢ The Log In option allows to log in an existing user.
¢ The Add Details options provides registration for new user.
¢ The View Details allows the user to view all the products.
3.9 TABLE DESIGN
A well designed database is essential for the performance of the system. Several tables are manipulated for varying purposes. The table, also known as the relation, gives the information of the attributes regarding the specific entries. Normalizing of table is done to the extent possible. These tables help to store and retrieve the data very efficiently.
CHAPTER 4 CODING
4.1 FEATURES OF LANGUAGE
¢ Microsoft Visual Studio .Net
Visual Studio .NET is a complete set of development tools for building ASP Web applications, XML Web services, desktop applications, and mobile applications. Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrated development environment (IDE), which allows them to share tools and facilitates in the creation of mixed-language solutions. In addition, these languages leverage the functionality of the .NET Framework, which provides access to key technologies that simplify the development of ASP Web applications and XML Web services.
¢ The .NET Framework
The .NET Framework is a multi-language environment for building, deploying, and running XML Web services and applications. It consists of two main parts:
1. Common Language Runtime
Despite its name, the runtime actually has a role in both a component's runtime and development time experiences. While the component is running, the runtime is responsible for managing memory allocation, starting up and stopping threads and processes, and enforcing security policy, as well as satisfying any dependencies that the component might have on other components. At development time, the runtime's role changes slightly; because it automates so much (for example, memory management), the runtime makes the developer's experience very simple, especially when compared to COM as it is today. In particular, features such as reflection dramatically reduce the amount of code a developer must write in order to turn business logic into a reusable component.
2. Unified programming classes
The framework provides developers with a unified, object-oriented, hierarchical, and extensible set of class libraries (APIs). Currently, C++ developers use the Microsoft Foundation Classes and Java developers use the Windows Foundation Classes. The framework unifies these disparate models and give C#.net and JScript programmers access to class libraries as well. By creating a common set of APIs across all programming languages, the common language runtime enables cross-language inheritance, error handling, and debugging. All programming languages, from JScript to C++, have similar access to the framework and developers are free to choose the language that they want to use.
¢ Introduction to C#.NET
In brief, C#.NET a next generation of ASP (Active Server Pages) introduced by Microsoft. Similar to previous server-side scripting technologies, C#.NET allows to build powerful, reliable, and scalable distributed applications. C#.NET is based on the Microsoft .NET framework and uses the .NET features and tools to develop Web applications and Web services.
Even though C#.NET sounds like ASP and syntaxes are compatible with ASP but C#.NET is much more than that. It provides many features and tools, which helps to develop more reliable and scalable, Web applications and Web services in less time and resources. Since C#.NET is a compiled,. NET-based environment; we can use any .NET supported languages, including VB.NET, C#, JScript.NET, and VBScript.NET to develop C#.NET applications.
¢ Advantages of C#.NET
1. .NET Compatible
.NET compatibility feature of C#.NET provides applications to use the features provided by .NET. Some of these features are multi-language support, compiled code, automatic memory management, and .NET base class library. We have choice to select a programming language and can write Web applications using any .NET supported language, including C#, VB.NET, JScript.NET and VBScript .NET. All C#.NET code is compiled, rather than interpreted, which allows early binding, strong typing, and just-in-time (JIT) compilation to native code, automatic memory management, and caching.
The .NET base class library (BCL) provides hundreds of useful classes. This library can be accessed from any. NET supported language.
2. Web Forms and Rapid Development
Web Forms allows to build rapid Web GUI applications. Web Forms provides web pages and server side controls. We can use web forms and server side controls in VS.NET like we write Windows applications. VS.NET provides Windows application similar drag and drop features, which allows to drag server side controls on a page and set control properties and write event handlers by using wizard property page. The VS.NET framework writes code under the hood and the application is ready in no time.
3. Native XML Support and XML Web Services
XML is a vital part of entire .NET framework. . NET uses XML to store and transfer data among applications. The .NET base class library provides high-level programming model classes, which can be used to work with XML.
An XML Web service provides the means to access server functionality remotely. Web services use SOAP (Simple Object Access Protocol) to provide access to clients. Web services can be used to build different layers of distributed applications and we can use different layers remotely.
4. Databases and ADO.NET
ADO.NET is a new version of ADO (ActiveX Data Objects). Even though ADO.NET sounds like ADO, but it is a complete redesigned database access technology. ADO.NET allows to access different kinds of databases using only one programming model. We must be familiar with DAO, ADO, ODBC, RDO and other database access technologies previous to ADO.NET. Each of these technologies had its owns pros and cons. ADO.NET combines features of all of these techniques and provides a single higher level-programming model and hides all details. It makes the job much simpler and provides a way to write rapid development.
5. Graphics and GDI+
GDI+ is an improved version of GDI (Graphics Device Interface) to write Windows and Web graphics applications. The .NET base class library provides GDI classes to write graphics applications. Using these classes not only we can write Windows applications, but we can also write Web graphics applications.
6. Caching and State Management
One of the most important factors in building high-performance, scalable Web applications is the ability to store items, whether data objects, pages, or parts of a page, in memory the initial time they are requested. We can store these objects on the server or on the client machine. Storing data on a server or a client is called caching.
C#.NET provides two types of caching - page caching and request caching. We use request caching to improve code efficiency and to share common data across the pages and use page caching to provide fast access to the Web applications from clients.
C#.NET provides easy-to-use application-state and session-state management, which allows managing states of Web applications. C#.NET also provides cookie less state management, means we don't need to use cookies to for state storage.
7. Enhanced Security
C#.NET provide us to authenticate and authorize users for our applications. We can easily remove, add to, or replace these schemes, depending upon the needs of our application.
8. Mobile Device Development
New addition to C#.NET, Mobile SDK allows to write Web application that run on Wireless Application Protocol (WAP) and Wireless Mark-up Language (WML) and HDML compliant devices.
9. Messaging and Directory Services
C#.NET uses the Messaging services class library, which is a high-level programming wrapper for MSMQ messaging services. The .NET base class library also contains class wrappers for Active Directory that enables to access Active Directory
Services Interface (ADSI), Lightweight Directory Access Protocol (LDAP), and other directory services through C#.NET applications.
10. Migration from ASP to C#.NET
Even though C#.NET syntaxes are similar to ASP, but C#.NET is a new designed model and more object oriented. ASP pages won't work without modifying it. The only advantages ASP developers will have is familiar code syntaxes.
CHAPTER 5
SYSTEM IMPLEMENTATION AND TESTING
5.1 SYSTEM IMPLEMENTATION
System implementation is the process of bringing the developed system into operational use and turning it over to user. It can be the most crucial stage in achieving a successful new system and in giving the users confidence that the new system will work and be effective.
For a successful implementation of the system, implementation plan is necessary. Its major elements include test plan, training plans, an equipment installation plan and a conversion plan.
The test plan provides for the preparation of the test and for testing the system in a planned, structured manner. Training plan is necessary to ensure that all people who are associated with the computer related information system have the necessary to knowledge and skills. An important activity related to training is managemental orientation. Equipment implementation activities are site preparation, equipment installation and hardware-software checkout.
Conversion is the process of initiating and performing all the physical operation that results directly in the turnover of the new system to the user. There are two parts of conversion. The conversion plan is implemented throughout the development phase into the operational phase. The conversion plan includes procedural conversion, program conversion and file conversion. The changeover plan also specifies the method of change from old to new system. Choices of change over methods include parallel operation, immediate replacement and physical changeover.
5.2 SYSTEM TESTING
System testing is done to verify whether the system has met its design objectives. User is responsible for supplying the input data and participating in the evaluation of the system test results. Testing is done at two levels: testing individual modules and testing of individual system. During system testing system is used experimentally to ensure that the software will not fail. Testing ends when the users and programmers are satisfied that the current projects is running properly and producing correct results.
The new system was made operational. The performance was evaluated to determine whether the system achieved the results that were expected. The details are stored and with respect to the stored information, the system can generate error free reports. The system maintenance is essential to accommodate from expansion on demand for information.
5.3 SYSTEM CHANGE OVER
Change over is the stage of moving from the old system to the new system. System change over specifies the method of handover, giving detailed schedule of activities to be performed by the concerned personnel in the system. During this period, those who prepare input data and use output results must co-operate with data processing specialists if the new system is to be successful. The department personnel saw the executions of the program. If they are satisfied with the new system it can be handed over to the users. The users are trained before they handle the system. A user manual is also prepared for quick reference.
5.4 SYSTEM SECURITY AND MAINTANANCE
The change over the system even though it is fully correct and complete is not the end of matter. The system should be given proper security and maintenance in order to keep them efficient and up-to-date.
The system security is for protection against fraud and disaster. To avoid unauthorized access, password protection is highly recommended while running this new system. The password has to be maintained directly and files have to be kept very confidential.
Finally system and programs that have been successfully implemented are usually subjected to continuous change. The system should be made to adapt modifications and improvements to meet changing conditions. A first class maintenance effort requires the cooperation of the people served by the system or program and those responsible for maintaining it. Maintaining the good customer relations and data security contributes to the usability of computer related information system.
5.5 LIST OF FORMS
Fig: 5.2 USER DETAILS
This form is used to add details of a new user.
Fig: 5.3 CUSTOMER DETAILS
This form is used to add details of a new customer.
Fig: 5.4 NOMINEE DETAILS
This form is used to enter details of nominee.
Fig: 5.5 POLICY DETAILS
This form is used to enter details of new policies.
Fig: 5.6 CHANGE PASSWORD
This form is used to change password of the existing users.
Fig: 5.7 COMPANY DETAILS
This form is used to enter the company details.
Fig: 5.8 POLICY APPROVAL
This form is used for approving policies taken by various customers.
Fig: 5.9 POLICY AUTHORISATION
This form is used to authorize new policies introduced in the company.
Fig: 5.10 USER AUTHORISATION
This form is used to authorize new users of the company.
Fig: 5.11 VIEW USERS This form is used for viewing all authorized users of the company.
IS IACT5 - [view policy] BEE
Action Add Details View Details Edit Details Option Reports _ B X
APPROVED POLICIES
IACTS Policvk IACTS Pm Poller IACTS Pm Policy IACTS Pm Duratic IACTS Pm Policy jeevan anand yooo 5 Ye IACTS Pm Pendit IACTS Pm Fir*tcoi IACTS Pm Sscos 0 10 |
| PLCY00002 jeevan suraksha mm 6 Yes 0 15 8
PLCY00003 sun plus oop 10 Yes 10 10 4
PLCY00004 mmmm 8 No 500 15 1
* 1
CLOSE
Fig 5.12 VIEW POLICIES
This form is used for viewing all available policies in the company.
Fig:5.13 COMMISSION TRACKING
This form is used by the unit manager to calculate the commission that is payable for a particular agent.
B IACTS - [Premium payment form] E]lj[](B]|
Action Add Details View Details Edit Details Option
PREMIUM PAYMENT FORM
Customer id |C9T00005
Register id |REG00005 VIEW dates a^yjjkiMyai v
Policy id Due date |PLCY00003 B/16/200812:000A | 12/16/200812:00:00 ” 0/16/200912:00:00 i\S 12/16/200912:00:00” 0/16/201012:00:00/ 12/10/201012:00:00 6/16/2011 12:00:00/ _ 12/10/2011 12:00:00 Y-
Current date |6/18/2007 12:00:00 A
Premium amount 34250
Penality 10
Total amount |30610
| PAID | CANCEL |
Fig: 5.14 PREMIUM PAYMENT
This form is used for payment of premium. The premium payment dates of a corresponding customer can be viewed from this form.
CHAPTER 6
CONCLUSION
The project "Insurance Agent's Commission Tracking" is a small module of the complex insurance management system. The module's intention is to track the commission paid to agents in an insurance company. The system has been developed with much care that it is free of errors and at the same time it is efficient and less time consuming. . We have tried our level best to make the system as user friendly as possible. Also provision is provided for future developments in the system. The entire system is secured.
APPENDICES
OVERVIEW OF VISUAL STUDIO 2005 Introduction to Visual Studio .NET
In February 2002, software developers and architects worldwide; were introduced to Visual Studio .NET and the Microsoft .NET Framework. This landmark release, four years in the making, offered a unified development environment and programming model for constructing a range of software solutions. With the recent launch of Visual Studio .NET 2003, customers gained the benefits of enhanced tool and framework functionality, as well as increased performance, security and scalability for building enterprise-critical software.
Features of Visual Studio 2005
¢ Refractoring
Making changes to your code like, "pulling a large stretch of inline code into its own method" or "converting a field to be a property." The Refactoring support makes this easy to do The key tenet of Extreme Programming created by Kent Beck is constant Refactoring. Under this programming model, you are developing code rapidly and iteratively, but to keep your code from becoming a jumbled mess, you must constantly Refactor. Refactoring is a C# only feature.
¢ Edit and Continue
Visual Basic has always been about Rapid Application Development (RAD). One key feature is the ability to fix runtime errors on the fly. With Visual Basic .NET 1.0 and Visual Basic .NET 1.1, this powerful feature wasn't included. This feature is on-board for Whidbey. If you run into an exception at runtime, you get an exception helper that provides tips for fixing common errors, but more importantly, you can edit the code, select F5, and it continues right where you left off. Edit and Continue is VB .NET only feature.
¢ ClickOnce
ClickOnce make it easy to install applications and provide ongoing updates (Self-Updating), rather than forcing to distribute new versions of application, can just
deploy the portion of the application which has changed. In the .NET Framework 1.0 and 1.1, href-exes were not able to solve many deployment issues. Href-exes are also known as ''no-touch deployment, or zero impact deployment''.
Essentially, with versions 1.0/1.1, you can deploy an application to a Web server, allowing users to browse to the URL for the exe, as in: <a href=''someapp.exe''> You can run me by clicking this page link </a> When the user clicks the link, the application downloads to their Internet files cache and runs. To keep this from being a huge security hole, the application permissions are restricted based on the URL (Intranet applications get different permissions than Internet applications, for example), or other factors. This means that some applications no longer need to be deployed in the traditional sense; no more setup.exe or MSI 3 href-exes have a number of limitations
¢ The .NET Framework must be pre-installed on the client machine.
¢ There's no good way to bootstrap the .NET Framework down if it's not there.
¢ Most non-trivial applications consist of the main .exe and a number of assembly files. With href-exes, the assembly files are downloaded on demand, which is great for corporate Intranet applications, but there's no way to download the application in one shot so that you know it can be safely used off-line.
¢ Limited support for versioning.
¢ The application doesn't hook into Add/Remove Programs, and the application doesn't install Start menu shortcuts.
RESUME
The developed system is flexible and changes can be made easily. The system is developed with an insight into the necessary modification that may be required in the future. Hence the system can be maintained successfully without much rework.
One of the main future enhancements of our system is to include the entire functionalities of the insurance management system.
REFERENCES
1. c-sharpcorner.com
2. programmersheaven.com