LightBlog
Contact at mumbai.academics@gmail.com or 8097636691/9323040215
Responsive Ads Here

Wednesday, 14 February 2018

Insurance project


Insurance project

PURPOSE OF THE PROJECT
·     To develop a common interface for all the agents in the insurance firm.
·     The system should provide means to manage different customers and their respective policies.
·     Instant status of involvements of a person in the task.
·     To provide details of all available policies and agents to the visitors.
·     Security to the confidential information.
·     Reduce the redundancy of making the entries of the activities, which are previously done manually.
·     To speed up the processing within the firm.
PROBLEMS IN THE EXISTING SYSTEM
·        The current system is a manual one where in the firm maintains all the information in the form of records. There by collecting necessary information by searching becomes manual.
·        Transfer of information between different sections of the enterprise is in the form of documents or letters. Drafting letters will take time.
·        Manually approaching the person and confirming the person for a policy is a tedious job.
·        Due to mismanagement the work is delayed to later date than the due date.
·        Unavailability of proper information to different levels of employees with in the firm.
THE PROPOSED INSURANCE SYSTEM
·     The information of the entire firm will be maintained at a centralized data base so any changes made will be replicated to all other users of the
·     Provides Interactive interface through which a user can interact with different areas of application easily.
·     Deploy the application on a single system and make it available on all the systems within the network, thereby reducing the maintenance cost of software.
SCOPE OF THE PROJECT     
·        The application is made as simple as surfing a website. There by non-technical persons can also interact with the processing on the application easily.
·        Provides instant information regarding the work under process within the company.
·        Easy management of data as located at a server.
The complete system can be divided into two halves on basis of access levels.
A) Administrator
B) Agent
C) Customer
Administrator:
An Administrator falls into the higher hierarchy when compared with the Agent and Customer. The Administrator can add agents, access available policies and their details, can select an Agent and view his customer details. The Administrator can delete Agents and also can transfer a customer from one Agent to another Agent. Once the Agent is added he is bounded with the respective policies.
Agent:
The Agent can see his/her profile and may update it if necessary. He may request for tasks of his choice. The Agent can add users, mark progress of assigned policy. He must calculate the termly premium reports of his customers and inform them accordingly. He can add, delete Customers. He can assign policies to and delete policies from a Customer. He can view all his Customer details.
Customer:
The Customer falls into the lowest level of hierarchy. The Customer can visit the site and select his policy and its corresponding agent. He can update his profile and can manage his policy in accordance to his agent.
ACCESS CONTROL FOR DATA WHICH REQUIRE USER AUTHENTICATION
The following commands specify access control identifiers and they are typically used to authorize and authenticate the user (command codes are shown in parentheses)
USER NAME
The user identification is that which is required by the server for access to its file system. This command will normally be the first command transmitted by the user after the control connections are made (some servers may require this).
PASSWORD: 
This command must be immediately preceded by the user name command, and, for some sites, completes the user's identification for access control. Since password information is quite sensitive, it is desirable in general to "mask" it.
HARDWARE & SOFTWARE SPECIFICATIONS
HARDWARE REQUIREMENTS:
  • Pentium III.
  • 128 MB Ram
  • 512 KB Cache Memory
  • Hard disk 20 GB
  • Microsoft Compatible 101 or more Key Board
SOFTWARE REQUIREMENTS:
  • Operating System                               :           Windows 2000/NT/XP
  • Back End                                            :           SQL Server-2000
  • Front End                                            :           ASP.Net using C#.Net
  • Server                                                  :           IIS

No comments:

Post a Comment