REQUIREMENTS DEFINITION

Functional Requirements

1. Registration Facilities
1.1 New users will be able to register as customers of the company directly through the
system.
1.2 The system will be able to verify new users upon signup.
1.3 Existing customers will also be able to access the system using their customer
information already existing on the database.
2. Searching for insurance plans
2.1 Customers will be able to search for available insurance plans using the system.
2.2 Customers who have made a quotation request will search using their reference
number.
2.3 A new search is made using the car type, No claim bonus (NCB), driving experience,
and involvement in any accident or conviction of any driving offence over a period of
5 years.
3. Quotation handling
3.1 Customers will be able to make quotation requests using the system (in the case
where customer inputs do not match regular insurance plans available on the
platform).
3.2 Customer quotation requests will be handled by a sales representative, and a tailor
made insurance plan will be made, and a reference number for the new plan will be
sent to the customer’s email address.
3.3 Customers will be able to purchase insurance plans presented by the system upon
receipt of their reference number.
4. Order and Payment for insurance
4.1 Customers will be able to make payment for their selected insurance plans using the
system.
4.2 A payment gateway will be made available to facilitate E-Payment.
4.3 Customers will also be able to renew their insurance plans using the system.

Non Functional Requirements

1. Operational
1.1 The database will be constructed to accommodate flexibility of insurance plans, as
user information may vary, as we expect to have users with a variety of car models,
driving experience, etc.
1.2 The system will run on a variety of web- enabled devices.
 1.3 In the event of failure of a transaction, or a process being incomplete, the system
should be able to restart the process and reverse funds where necessary.

2. Performance
2.1 The system will be user friendly and assures ease of use.
2.2 Search speeds will be optimal, as the system will be very responsive.
2.3 Payment will also be fast, as payment gateway will be efficient.

3. Security
3.1 Customer information will be secured.
3.2 Customer payment information will be kept safe as payment information will be
encrypted.

4. Cultural and Political

4.1 All policies regarding user confidentiality and protection of user information will be
closely studied and applied critically.
4.2 All legal requirements for operating such systems will be met.