Insurance Policy Management System Project

Insurance Policy Management System Project

INTRODUCTION:    

         The project entitled INSURANCE  MANAGEMENT  is a pilot project for small insurance company to manage their administration .

PROJECT: 

        INSURANCE  MANAGEMENT  is a software application maintain the records related to Insurance Products.  

OBJECTIVE:

       The main objective of the application is to automate the existing system of manually maintaining the records agents, policies, premium, maturity, etc.,  

SCOPE:

       This application can be used by any Insurance company to maintain the Insurance management, daily transactions, policy registration etc.

PROBLEM DEFINITION:

         The transactions related to Insurance policies,  premiums, policy maturity, agents management, agent commission calculation etc.,.

          All these are to be automated and an application is required to relate all of them relatively and logically so that the current system can be replaced and accepted without major changes and problems.

          The application should provide quick access to the records maintained and must reveal the important reviews about the business so that the growth can be easily compared and should provide with the various reports showing the related details so that the important decisions could be taken easily.

SOFTWARE REQUIREMENT SPECIFICATION:

An SRS is basically an organization's understanding (in writing) of a customer or potential client's system requirements and dependencies at a particular point in time (usually) prior to any actual design or development work. It's a two-way insurance policy that assures that both the client and the organization understand the other's requirements from that perspective at a given point in time.
The SRS document itself states in precise and explicit language those functions and capabilities a software system must provide, as well as states any required constraints by which the system must abide. The SRS also functions as a blueprint for completing a project with as little cost growth as possible. The SRS is often referred to as the "parent" document because all subsequent project management documents, such as design specifications, statements of work, software architecture specifications, testing and validation plans, and documentation plans, are related to it.
It's important to note that an SRS contains functional and nonfunctional requirements only; it doesn't offer design suggestions, possible solutions to technology or business issues, or any other information other than what the development team understands the customer's system requirements to be.
A well-designed, well-written SRS accomplishes four major goals:

• It provides feedback to the customer. An SRS is the customer's assurance that the development organization understands the issues or problems to be solved and the software behavior necessary to address those problems. Therefore, the SRS should be written in natural language, in an unambiguous manner that may also include charts, tables, data flow diagrams, decision tables, and so on.
• It decomposes the problem into component parts. The simple act of writing down software requirements in a well-designed format organizes information, places borders around the problem, solidifies ideas, and helps break down the problem into its component parts in an orderly fashion.
• It serves as an input to the design specification. As mentioned previously, the SRS serves as the parent document to subsequent documents, such as the software design specification and statement of work. Therefore, the SRS must contain sufficient detail in the functional system requirements so that a design solution can be devised.
• It serves as a product validation check. The SRS also serves as the parent document for testing and validation strategies that will be applied to the requirements for verification.

SRS are typically developed during the first stages of "Requirements Development," which is the initial product development phase in which information is gathered about what requirements are needed--and not. This information-gathering stage can include onsite visits, questionnaires, surveys, interviews, and perhaps a return-on-investment (ROI) analysis or needs analysis of the customer or client's current business environment. The actual specification, then, is written after the requirements have been gathered and analyzed.
The National Bureau of Standards, IEEE (Standard No: 830-1984), and the U.S Department of Defense have all proposed candidate formats for software requirements specifications. The general structure is implemented with the related software application               

INTRODUCTION:   

         The project entitled INSURANCE  MANAGEMENT  is developed as pilot project to manage Insurance Company transactions. It is a software application marinating the records related to all the transactions occurring at the company.

OBJECTIVE:

       The main objective is to maintain the inventory records of a generic shop which deals in musical tapes.

• To keep accounts Agents, Policies, Premiums
• To generate the monthly, Quarterly, Half Yearly and Yearly premiums
• Agents Commission Management
• Branch transaction details

SCOPE:

      As this is generic software it can be used insurance company basically it is a pilot project to manage insurance company transaction. On approval it can build as full fledged software, later it can be customizable to any other insurance companies.

GOAL:

         The main goal of the application is to maintain the records of  policies, policy holders, premiums, premium calculations, agents, agents commission management. Brach details management etc.,

Hardware Requirements

Processor                                 :           Pentium IV 2GHz and Above

RAM                                       :           2GB RAM

Monitor                                   :           15” Color Monitor

Keyboard

Mouse

Software Requirements

Operating System.      :           Windows XP

Developing Tool                     :           Visual Basic 6.0

Database                                 :           MS Access