Design and Implementation of Life Insurance Assets Management methods using Create Insurance System

Transcription

1 22 Design and Implementation of Life Insurance Assets Management methods using Create Insurance System Sai Divya Kalagatla 1, Chandra Babu. K 2 and Mohana Roopa. Y 3 1 Department of Computer Science, JNTUniversity-Anantapur/Annamacharya Institute of Technology & Science, Tirupati, Andhra Pradesh / India 2 Asst. Prof., Department of Computer Science, JNTUniversity-Anantapur/Annamacharya Institute of Technology & Science, Tirupati, Andhra Pradesh / India 3 Assoc. Prof., Department of Computer Science, JNTUniversity-Anantapur/Annamacharya Institute of Technology & Science, Tirupati, Andhra Pradesh / India Abstract The main target of LIAM is to control risk of operationautomation through online, assure policies registrations by the customers, maintain policy bonus in flexible periods, arrange facilitates the premiums flexi-pay modes, collect assets information (customer pay, details of branch and dues) and logistics. LIAM is an entire system which makes sure the entire process of business flow works diligently and smoothly. The software CIS: LIAM is a WEB2.0 application software which is developed based on JAVA technology. LIAM system has unique policy schemes, different premiums can be integrated into one system. The integrity of these policy schemes is useful for LIAM to monitor the modules (e.g. chairman, manager, agent and customer) and also improves the trust among customers, decrease manpower and process time for the organization. LIAM has four main factors to run the organization successfully which are chairman, manager, agent and customer. The chairman s part is responsible to oversee that the whole system runs well and to monitor the type of policy, terms and conditions, payment and registration of different branch managers. The manager is responsible for the operation of premiums, dues and commissions. The agents are the responsible for customer registration and to achieve their targets and the customers in turn are the main resource for the system. CIS will promote the assets management control, digitize assets information, and monitor the premium process. In a word, LIAM will be helpful for company to create their own competitive strength. How should and how the software be managed? What is the management concept or paradigm? Software professionals, if they think about management of software at all, think in terms of Configuration Management. This is not a method for over-all software management, but it merely controls software items versions. This is much too fine a level of granularity. LIAM begins with accurate and timely information. Managers tend to view software as something fortunately very necessary but troubling because, they have very little real information about it and control is still nebulous. Policy accounts and accountants view software as an incomprehensible intangible, neither wholly an expense nor really an asset. They do not have, nor do they produce information concerning it. Their data concerning software barely touches on direct outlays and contains no element of effort. Keywords: LIAM System, CIS, JAVA WEB, 1. Introduction Now a day s information technology plays an important role in many organizations. Worldwide IT related expenditure has been on the rise. A wide range of modern software systems present typical characteristics. A nonexhaustive list of application domains that illustrates this scenario includes personal-assistance, life insurance, simulation, medical-record processing and e-commerce. Source code: The term IT-portfolio embraces various entities relating to IT such as projects, computer hardware, systems, licenses, people (knowledge), networks, and more [1]. This project initiates our research in life/insurance management, more specifically, in assets management system area. Modern software engineering approaches, such as generative programming and software factories, motivate the configuration knowledge representation and automatic product derivation through the adoption of domain-specific languages (DSLs) and code generators. Several generative product derivation tools have already been proposed and are used in the industry. Although the code-oriented approaches support the automatic product derivation of MAS-PLs, they do not allow explicitly specifying agent-oriented abstractions and instantiation rules in the configuration knowledge [2, 3].

2 23 Insurance system automates the management of insurance activities, which involves defining policies, schemes, policy specification, policy terms and conditions, policies registrations by the customers, facilitates the premiums flexi-pay modes, and policy bonus in flexible periods [5,6]. The agents are involved in the process of the customer policy registration and the commissions are based on the targets achieved by the agents. Insurance system also maintains the database of the branch managers who deals with the agents which in turn deals with the customers. The main theme of this project is automation of the Insurance system and processes the all activities through on line, the system mainly concentration of these factors - chairman, manager, customer and agent. income can be in terms of money or goodwill, since the software brings in both, the system is highly viable. 2.2 System design The work-flow acts as a bridge between the requirement specification and the final solution satisfying the requirements. 2. System Analysis Over the past five to eight years, software has become a vital component of almost every business as well as the national economies; one of the most difficult tasks is that, the selection of the software, once system requirement is know it is to determine whether a particular software package fits the requirements. After initial selection further security is needed to determine the desirability of particular software compared with other candidates. This section first summarizes the application requirement question and then suggests more detailed comparisons. 2.1 Feasibility study To evaluate the feasibility of a project at the earliest possible time, there may be different ways of checking whether a system is feasible or not. Operational feasibility; the operational scope of the system is checked. The system under consideration should have enough operational reach. It is observed that the proposed system is very user friendly and since the system is built with enough help, even person with little knowledge of windows can find the system very easy. Technical feasibility; the performance and it constraints that may affect the ability to achieve an acceptable system, it begins with an assessment of the technical viability of the proposed system [4]. Users to be accessed are the need of various kinds of resources for the successful implementation for the proposed system. Economic feasibility; an evaluation of development cost weighed against the ultimate income or benefit derived from the development of the proposed system is made, care must be taken that incurred in the development of the proposed of the system should not exceed from the system. The Fig. 1 Collaboration within LIAM Web-service Policy s. The system needs to be a web-based system so that it allows the chairman, branch managers, agents and customers to access the company database over the internet. Being a web-based system also enables the company staff to communicate with other users. An added advantage is chairman communicate with other employees over the net since there could be instant responses from the suppliers. The whole process depends on communication between chairman, manager and between customer and agents. If all these communications are done through a web-based system, then the time period for the whole process can be considerably brought down. Fig. 2 Requirement Analysis with URL: Chairman

3 System details The system needs to store the company details: 1. The system needs to store the details of all the premiums that are available of the company and the entire branch manager s, customers and agents held in the company warehouse. Web-based system, a login authorization should be providing, so that 4 factors will able to look up and use option that are specific to them. 2. It allows the agent s statistics and customer visible their next premium data, bonus, dues and related information. 3. It provides a customer and agents reports to estimate their performance, above information to store in premium details of the customer for future updates. Fig. 3 Requirement Analysis with URL: Manager The main theme of this project is automation of the Insurance system and processes the all activities through on line, the system mainly concentration of these factors - chairman, manager, agent and customer. Fig. 5 Requirement Analysis with URL: Customer 3. Data Dictionary The logical characteristics of current system data are stores, including name, description, aliases, content and organization. Identifies processes where the data are used and where immediate access to information needed. 1. To manage the detail in large systems 2. To communicate a common meaning for all system elements 3. To document the features of the system 4. To facilitate analysis of the details in order to evaluate characteristics and determine where system changes should be made 5. To locate errors and omissions in the systems 3.1 Agents To register of customer policy details and informs their due dates in time act like protector until finish their bonds and get commission. Agent involves in the customer policy registration process, personal details and manager details, as shown in figure 6. Fig. 4 Requirement Analysis with URL: Agent Fig. 6 Interface in Agents

4 25 Table 1: Information of agent Name Null? Type AGENT ID NOT NULL NUMBER (11) AGENT NAME AGENT FNAME AGENTAGE AGENTSEX AGENTQUAL AGENT OCCUPATION AGENTADDRESS AGENTREGDATE AGENT SECURITYDEPOSIT BRANCHMGRID NUMBER(3) VARCHAR2(1) DATE NUMBER (10,3) NUMBER(7) amounts, establishing the different branch and registration of the branch managers. The chairman defines the policy commission rates for the agents who involves in the customer policy registration process, as shown in figure 8. Fig. 8 Collaboration within LIAM Web-service branch 3.2 Customer The customers are a main source, on his interest and benefits of policy, can take more than one policy up to their requirement. After login the information obtain; premium dates, bonus dates, policy details and it display reports premiums, bonus an payments, as shown below figure 7. Table 3: Login ID for branch Name Null? Type BRANCHID NOT NULL NUMBER (5) BRANCHNAME LOCATION BRANCHDATE PHONE STATE VARCHR2(22) NUMBER(12) 4. System Evaluation Fig. 7 Collaboration within LIAM Web-service Customer It is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. Testing presents an interesting anomaly for the software engineer. Table 2: Login ID for customer Name Null? Type USER ID NOT NULL NUMBER (11) PASSWORD TYPE 3.3 Manager and Chairman 4.1 Compilation of Code When you compile the code, the Java compiler creates machine code for a hypothetical machine called Java Virtual Machine (JVM). The JVM is supposed to execute the byte code. The JVM is created for overcoming the issue of portability. The code is written and compiled for one machine and interpreted on all machines. This machine is called Java Virtual Machine. The manager to calculate the premium amounts, interests, dues, and bonus and agent commission. Chairman is the super user of the whole system, to handle the policies, policies terms and conditions, policies amounts, face

5 Test should be planned long before testing begins 3. Testing should begin on a small scale and progress towards testing in large 4. Exhaustive testing is not possible Fig. 9 Structure of Database Table in LIAM During run-time the Java interpreter tricks the byte code file into thinking that it is running on a Java Virtual Machine. <html> <head> My first JavaScript </head> <body><br> This is a normal HTML document <br> <script language= JavaScript > Document.write ( this is a java script ) </script><b r> Backing HTML again </body> </html> 5. To be most effective testing should be conducted by a independent third party 4.3 Testing Strategies Fig. 11 Homepage of Agent details A strategy for software testing integrates software test case into a series of well-planned steps that result in the successful construction of software. Software testing is a broader topic for what is referred to as Verification and Validation. Verification refers to the set of activities that ensure that the software correctly implements a specific function Validation refers he set of activities that ensure that the software that has been built is traceable to customer s requirements such as unit testing, integration (top-down, bottom-up), validation, recovery, security and performance testing. 4.2 Testing objectives Fig. 10 Homepage of LIAM Testing is process of executing a program with the intent of finding an error. A good test case is one that has a probability of finding an as yet undiscovered error. A successful test is one that uncovers an undiscovered error. 1. All test should be traceable to end user requirements Unit testing focuses verification effort on the smallest unit of software design that is the module, using procedural design description as a guide, important control paths are tested to uncover errors within the boundaries of the module. The unit test is normally white box testing oriented and the step can be conducted in parallel for multiple modules. Integration testing is systematic technique for constructing. The objective is to take unit tested methods and build a program structure that has been dictated by design. Top-down integrations an incremental approach to construction of program structure. Modules are integrated by moving downward

6 27 through the control hierarchy, beginning with the main control program. Modules subordinate to the main program are incorporated in the structure either in the breath-first or depth-first manner. Recovery testing system tests that forces the system to fail in a variety of ways and verities that the recovery is properly performed. Bottom-up integration as the name suggests, begins construction and testing with atomic modules i.e., modules at the lowest leveling the program structure, because the modules are integrated in the bottom up manner the processing required for the modules subordinate to a given level is always available and the need for stubs is eliminated. At the end of integration testing software ids completely assembled as a package. Validation testing is the next stage which can be defined as successful when the software functions in the manner reasonably expected by the customer. Reasonable expectations are those defined in the software requirements specifications. Information contained in those sections form a basis for validation testing approach. System testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system. Although each test has a different purpose, all work to verify that all system elements have been properly integrated to perform allocated functions. Security testing attempts to verify the protection mechanisms built into the system. Performance testing method is designed to test runtime performance of software within the context of an integrated system. 5. Conclusions To this end, the paper has designed and developed for conducting policy related task and processes the all activities through online. The main advantage of this system is to access this database globally for authorized users. The customers pay their payment at any branch and also know their details at any branch. Dynamically generated the reports like premium payment details, bonus details, due details. To reduce the time and manpower these two factors to improve the quality of organization. The database system must provide for the safety of the information stored, despite system crashes or attempts at unauthorized access. If data are to be shared among several users, the system must avoid possible anomalous results. Finally, LIAM system is designed and created with JAVA as web application software. This software will be useful for LIAM system References [1] [1 Kwiatkowshi, L.M, and Verhoef, C Recovering management information from source code. Science of Computer Programming. 78, DOI: /j.scico [2] Elder, C., Nunes, I., Kuleza,, U., and Lucena, C Automating the product derivation process of multi-agent systems product lines. The Journal of System and Software. 85, DOI: /j.jss [3] Pei-Chi C., and Hung-Min Sun Multi-agent based cloud utilization for the IT office-aid asset distribution chain: An empirical case study. Information Sciences, 245, DOI= [4] Ben-Menachem, M Towards management of software as assets: A literature review with additional sources. Information and Software Technology, 50, DOI= [5] Sylvain, G., and Mukund, G.D Asset/Liability Management and Innovative Investments. 8 th Global Conference of Actuaries, (Mumbai, India, March 10-11, 2006).IAA [6] Standard on Asset-Liability Management International association of Insurance supervisors (Beijing, China, October 26, 2006), Society of Actuaries, Specialty Guide on ALM (2003) Sai Divya Kalagatla currently is a master s student in the department of computer science and engineering at Annamacharya Institute of Technology and Science, JNTUniversity, India, while holding a Bachelor s in computer science engineering. Her research interests are web design and cloud computing. Fig. 12 Customer Registration Form Chandra Babu. K currently working as a Asst. Prof., in Department of Computer Science and Engineering Annamacharya Institute of Technology and Science, JNTUniversity, India. Mohan Roopa. Y currently working as a Assoc. Prof., and Head of Department of Computer Science and Engineering Annamacharya Institute of Technology and Science, JNTUniversity, India.