Top-Rated Free Essay

Software Engineering User's Requirements
Topics: Insurance / Pages: 4 (943 words) / Published: Mar 15th, 2014

American University of Beirut
Department of Electrical and Computer Engineering
EECE 430: Software Engineering
Fall 2013-2014
Section 1

User’s Requirements Document: Home Insurance

Group 5
Nour Absi Halabi
Petra Chidiac
Amal Hneine
Mohamed Itani
Suzanne Saleh
1|Page

Table of Contents
A. Introduction...............................................................................................1
1. Purpose ....................................................................................................3
2. Process ....................................................................................................3
3. Sources ....................................................................................................3

B. User’s Requirements Definition ..............................................................4
1. Authentication .........................................................................................4
2. Display General Records ........................................................................................... 4
3. Display Clients’ Information .................................................................................... 4
4. Add Client ........................................................................................................................ 5
5. Delete Client.................................................................................................................... 5
6. Risk Calculation............................................................................................................. 5
7. Add Quote ....................................................................................................................... 6
8. Update Quote .................................................................................................................. 6
9. Add Claim ........................................................................................................................ 6
10.Display Policy Details ................................................................................................. 7

C. Conclusion .................................................................................................7
D. Glossary .....................................................................................................8
E. References ..................................................................................................8

2|Page

A. Introduction:

1. Purpose
The purpose of this document is to define the user requirements for the system of a “Home
Insurance” Company.

2. Process
Several sources were used to define and categorize the requirements. The users’ needs, preferences and recommendations helped arrange these requirements in order of importance. Several meetings were held in order to be able to satisfy the mentioned purpose. 3. Sources
The requirements were defined according to three users’ categories: Employees, Clients and Public Users. Moreover, they are based on interviews done with people concerned.

3|Page

B. User Requirements Definition

1. Authentication
1.1 Description:
The system must provide the choice of logging in as:
 An employee
 A client
 A public user
1.2 Rationale:
The system shall provide different options based on the type of user who logged in: an employee, a client, or a public user.

2. Display general records
2.1 Description:
The system must display general company records including the list of clients and financial flows.
2.2 Rationale:
The employee shall have access to the company’s general records including list and number of clients, and the financial flows.

3. Display clients’ information
3.1 Description:
The system shall display clients’ records including contact, policy, and billing information upon request.
3.2 Rationale:
The client should be able to view his own insurance profile. The employees as well should be able to view all the records of all the clients.

4|Page

4. Add client
4.1 Description:
The system shall be able to add a new client’s record to the system and save the information.
4.2 Rationale:
The system should be able to add a new client with all the contact, policy, and billing information.

5. Delete client
5.1 Description:
The system shall provide the ability to delete a client or automatically cancel his insurance coverage if the client does not pay on time of renewal.
5.2 Rationale:
The system should keep track of every client’s insurance coverage period.

6. Risk calculation
6.1 Description:
The system shall calculate the risk to the client’s property based on specific information about the property provided by the client (type, net worth ...).
6.2 Rationale:
The system shall present an offer of the ideal insurance policy to the package the client chose.

5|Page

7. Add quote
7.1 Description:
The system shall provide the possibility of requesting a quote.
7.2 Rationale:
If the quote is requested by the client, the request shall be approved or rejected. The quote could be requested by the employee, hence approved automatically. 8. Update quote
8.1 Description:
The system shall provide the option of renewing one’s insurance or switching to a different insurance policy.
8.2 Rationale:
At the end of each insurance term, the client shall be able to renew his insurance, or switch to a different type of insurance policy.

9. Add claim
9.1 Description:
The system shall support the raising of a claim by a client or recording it by an employee.
9.2 Rationale:
The client should be able to raise a claim and support it with evidence (upload photos); the claim will later be either approved or rejected by the company.
Employees of the company should also be able to record or register a claim raised by a client to cover it later on.

6|Page

10. Display policy details
10.1 Description:
The system shall be able to display the policy details of clients upon the entering of the client’s policy number.
10.2 Rationale:
Employee should be able to display the policy details of the client such as the policy type (home insurance in our case), effective and cancellation dates of the policy, assessment of the house value, any amendments to the policy
(coverage of furniture, jewelry, appliances…), and the liability of a third party. C. Conclusion
The users’ requirement document provides a full description of the requirements for the
“Home Insurance” Company System. The goal of the project is to satisfy the users’ needs by providing them with an insurance policy that combines multiple personal insurance protections and to create a system that shall be effectively reliable and user friendly.
Moreover, the system synchronizes the efforts of the employees and clients in order to complete their tasks in a smooth and effortless way. This document can be used for the design and implementation steps of the Insurance System.

7|Page

D. Glossary


Claim: “A formal request to an insurance company asking for a payment based on the terms of the insurance policy. Insurance claims are reviewed by the company for their validity and then paid out to the insured or requesting party (on behalf of the insured) once approved”.



Coverage: “The amount of risk or liability covered for an individual or entity by way of insurance services. Insurance coverage is issued by an insurer in the event of unforeseen or unwanted occurrences”.



Insurance Policy: “Formal contract-document issued by an insurance company to an insured. It puts an indemnity cover into effect, serves as a legal evidence of the insurance agreement, sets out the exact terms on which the indemnity cover has been provided, and states associated information such as the specific risks and perils covered, duration of coverage, amount of premium, mode of premium payment, and deductibles, if any”.



Quote: “A statement of the amount of money that an insurance company calculates as the cost of providing insurance for something”.

E. References http://www.businessdictionary.com http://www.investopedia.com

8|Page

References: http://www.businessdictionary.com http://www.investopedia.com 8|Page

You May Also Find These Documents Helpful

  • Methodology: Software Engineering and Requirements Gathering
  • Software Engineering
  • Software Engineering
  • Requirements Engineering
  • Software Requirement Engineering Through Use Case
  • Software Engineering
  • Software Engineering
  • Software engineering
  • Software Engineering
  • Software Engineering