University of Florida. New Life Insurance Company Requirements Specification

Transcription

1 University of Florida New Life Insurance Company Requirements Specification Sep, 2011 by Chaitanya Panuganti Raghavendra Reddy Madakkagari Mohammed Shafiq Ali Soumya Debabrata Pani UNIVERSITY OF FLORIDA, GAINESVILLE, FL

2 TABLE OF CONTENTS 1. SYSTEM OVERVIEW Current System Proposed system scope Objectives of the system Best Practices HIGH LEVEL DESIGN Roles Description Function Description Roles, Functions and its interdependence ARCHITECTURE

3 1. SYSTEM OVERVIEW One of the great uncertainties of life is that, usually, one does not know exactly when he or she will die. At any point in time, individuals may want to achieve goals and objectives that require financial resources beyond those they have already accumulated. Insurance is a form of risk management. One pays a small amount to a company that promises to cover the costs of a future catastrophe. New life Insurance Company is a way to insure the life against odds. We, at New Life Insurance Company, keep records of all our customers. 1.1 Current System To ensure sustainable growth, we have concentrated our focus on expansion of branch network, organising an efficient and well trained sales force, and setting up appropriate systems and processes with optimum use of technology. We maintain records of all the customers who have insured their lives. But till today we were doing it manually Overview Of Current System Currently at New life Insurance Company, we have engaged employees who take all the required information about our customers and keep records in separate files Limitation Of Current System Since the data is stored in the form of hard files, it is tedious job for the employees to search for the file in a heap of thousand files to make a transaction entry Proposed System The new proposed system for New life Insurance Company will help them to gain a huge market share. As it will provide our employees to maintain the data in database server where just by click of a button we can get the customers information. The web application will have different interface for Managers, Employees and Customers. The new system provides online data to different type of users and they can take decisions based on the data. This also reduces the manpower required for maintaining the data and improves business for the organization as it is more effective. 3

4 Login Invalid Valid Manager Employee Customer Transaction Screens 1) Approve/Reject Customer Registration 2) Add/edit/del 3) Add PolicyPlans 4) Add PolicyDetails/ Plan Amount 5) View customer details 6) View Insurance Plans 7) Policy Registration 8) View Policy registration 9) Accept Premium 10) View claim details 11) Approve Claims 12) Reports 13) Change password 14) Change others password 1) View/edit customer details 2) View Insurance plans 3) Policy Registration 4) View Policy registration 5) Accept Premium 6) Apply Insurance Claim 7) View claim details 8) Reports 9) Change password 1) Customer Registration 2) View/edit customer details 3) View Insurance plans 4) View Policy registration 5) Apply Insurance Claim 6) View Claim details 7) Reports 8) Change password Logoff Screen 4

5 1.2 Proposed system scope The proposed system will provide different functionalities to different users. Manager of New life Insurance Company can anytime login and see any of the customer s information. An employee can also do the same. Similarly, it would be helpful to customers as well, as they do not need to go the New Life's office to see the details. They can login to New Life's website using their logon credentials. 1.3 Objectives of the system More Efficient. Synchronized data at all branches. Less man power required. 1.4 Best Practices Appropriate design patterns are used to incorporate the best practices in the design of the system. System architecture is flexible, scalable and robust. User Interface is intuitive and easy to navigate for the end user. System is modularized and well documented so that it is easily maintainable. 5

6 2. HIGH LEVEL DESIGN 2.1 Role Description No. Role Description 1. Manager The manager who is responsible for the Entire business process 2. Employee The Employee who can access the system and perform Limited number of operations compared to the manger 3. Customer The registered customer who can access to find their Policy details 2.2 Function Description No. Function 1. Name: Customer Registration Description: The Customer can register online by entering the details. After that the customer has to submit his/her id to the manager to complete the registration. 2. Name: Approve/Reject Customer Description: The Manager has to approve the customer registration based on the verification of his/her identity. 3. Name: Edit Customer Description: The Manager/Customer can edit the customer details if some modifications are required 4. Name: Delete Customer Description: The Manager can change the status of a customer to delete. So that the customer is not considered for any operations on the system 5. Name: Add Policy Plans Description: The Manager can add more Policy plans based on the business requirements 6. Name: Add Policy Details Description: The Manager can add more Policy details based on the business requirements 7. Name: View Customer Details Description: The Manager /Employee/Customer can view customer details.manager/employee Can view all the customer details whereas customer can view only his own details. 8. Name: View Insurance Plans Description: The Manager /Employee/Customer can view different types of Insurance Plans from which they can choose the appropriate Insurance Plan. 9. Name: Register Policy Description: The manager/employee can register a customer based on the customer requirements 10. Name: View Claim details Description: The manager/employee/customer can view the status of a claim using claim Id. 11. Name: Accept Premium Description: The Manager/Employee can accept the premium from the customer 12. Name: Apply Insurance Claim Description: The Customer/Employee can apply for insurance claim either it is matured or death. 13. Name: Approve Claim Description: The manager can approve/reject a claim once it is claimed and based on the approval policies 14. Name: Change Password Description: All users can change their password and the manager can change all users password if they forget the password. 15. Name: Reports All Users can view different types of reports based on their role. 16. Name: Change Others Password Description: The Manager can reset the password of an Employee or a customer if they forgot their password. 6

7 2.3 Roles, Functions and its interdependence A web application is being designed to automate most of procedures followed by the Insurance companies. Firstly, there are three different types of roles that are present in this project. Those are New/Current Customer Employee Manager Each of these three different roles has different functions, and different permission levels assigned to them. The new customer is looking for an insurance plan that fit his preferences. The customer should be able to register with user name and password. Upon browsing through all of the given policies and its details, the customer will choose one of the plans that are best suited to his needs. Upon selection of the policy, he will now be redirected to a page asking for his personal information like name, date of birth, address and also his proof of identification that will be used for verifying the person s credentials. This proof must be submitted, in person, to the manager or employee for approval at the office of the New Life Insurance Company. This new customer becomes a current customer once the manager or employee approves his registration. This is when he will be able to access his utility services which include the following viewing or editing basic customer details like address and phone number, viewing and adding different insurance plans, viewing current policy details, applying for insurance claim, viewing past claims, able to view reports containing any event change and change his own password. The customer is limited to these functions based on the permission level of his role. The employee is the person working at the insurance Company and this role has access to some of the functions that are restricted for the employee. The employee will be able to view and edit the customer details and also the insurance plan details in case when the customer is unable to do so. Now when the customer sends his personal information and the details about the insurance plan that he has selected, the employee has the permissions to be able to approve the policy registration in order for the policy to be in effect. Also, the premium that is to be paid (monthly or annually) by the customer can be done through the employee, meaning the employee will have the permissions to clear the payment of the premium from the customer s account. In additional to this, he will also be able to view or edit the customer details, view insurance plans, viewing the customer s different plans taken, applying for the insurance claims on behalf of the customer, viewing the past claims of the customer, able to view reports of customer s event changes along with the access to change customer s password. The Manager is the person working at the Insurance Company who has the highest level of authorization and this role has access to all the functions available. The Manager will be able to approve or reject the customer once the customer has registered. He will also be able to add new policy plans and also be able to add policy plan amounts to the policy created. In addition to this the manager has access to all the functions that are available to employees and customers. 7

8 3. ARCHITECTURE In this the Client interacts with the database through the presentation and the business layer. Firstly the browser requests for a particular webpage through the internet. The web server receives the request and passes it to PHP engine for further processing. The PHP engine parses the script and then connects to the oracle database to send the query. The CISE Oracle database processes the query and returns the result to the PHP engine which executes the script and then passes the results to web server. The web server passes the results to browser for displaying the results in HTML. Presentation and Business Logic Browser Web Server PHP Engine CISE Oracle 8