0% found this document useful (0 votes)
124 views5 pages

Software Requirements Specification: 1.1 Purpose of The System

This document outlines the software requirements for an insurance management system. The system will allow administrators to register and store client details in a database for easy retrieval. It will provide a user-friendly interface to speed up the registration process. The system will have modules for customers, issues, assured dates, and login. It will run on Windows using MySQL database and PHP for the frontend. The document describes functional requirements like login, password change, and registration. It also covers the user interface, hardware requirements, and quality attributes like maintainability, availability, and security.

Uploaded by

Daisy Wangui
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
124 views5 pages

Software Requirements Specification: 1.1 Purpose of The System

This document outlines the software requirements for an insurance management system. The system will allow administrators to register and store client details in a database for easy retrieval. It will provide a user-friendly interface to speed up the registration process. The system will have modules for customers, issues, assured dates, and login. It will run on Windows using MySQL database and PHP for the frontend. The document describes functional requirements like login, password change, and registration. It also covers the user interface, hardware requirements, and quality attributes like maintainability, availability, and security.

Uploaded by

Daisy Wangui
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

SOFTWARE REQUIREMENTS SPECIFICATION

1. INTRODUCTION
1.1 Purpose of the system
This system for managing information and doing company analysis that makes information
about the people and resources used in insurance readily available. This system has excellent
dynamic features like search tools for insurance awareness articles and instruction.

1.2 Intended audience


The system is intended for developers, project managers, the admin as the main user, and the
testers of Madison Group Insurance company.. This project would offer an automated solution
for automating an insurance policy's workflow. The use of automated systems makes it possible
to solve issues quickly and with high levels of dependability. It preserves information regarding
the client while offering the user a user-friendly environment. Data is stored by an automated
system in a database for future use.

1.3 Scope
This system is implemented for the admin to be able to register and store the respective details
of clients in their respective database tables hence retrieval will be easier.
It will help in the accuracy of data since it is an error-free system.
It will avoid duplication of the user’s details.
Provide a user-friendly GUI that will speed up the registration process.

2. OVERALL DESCRIPTION
2.1 User classes and characteristics
This system will have various sectors, which are:
 Customer module-for managing customer’s policy details
 Issue module- for managing issue details
 Assured date module- for managing assured date information
 Login module-managing login details. It allows the administrator to use the
system. The administrator gives his credentials to enter into the system. If the
details are correct it allows the admin.
2.2 Operating environment
The system will use the following:
Windows operating system
The application type is Web Applications
The backend development environment is MySQL.
The front-end development environment is PHP.

2.3 Design and implementation limitations.


The system has the following limitations:
 The creation of ID cards is not automated.
 No 24-hour customer service is offered.
 Customer and administrator cannot communicate directly.
 Payment schedules are set and cannot be altered.
 The OTP facility is not using it.

2.4 User documentation.


The user documentation that will be delivered together with the software is a user manual.

2.5 Assumptions and dependencies


We require a browser with Java support, the server, and Oracle 10g as the database server in
order to run the application.

We don't use any virtual private networks(VPN), which are a type of network technology that
enables secure connections via public networks like the Internet or private networks run by
service providers.

For safe remote login and other secure network services over an unsecured network, we don't
use any protocols.
3. FUNCTIONAL REQUIREMENTS
REQ.1 Product requirements.

Login- allows the administrator to use the system whereby the admin enters the details and if
it is correct then he can access and if not otherwise.

Change password- allows admin to change password. It takes you to the old password and then
allows you to enter the new password that will be used for future use.

Registration- allows admin to enter details of client, that is the name, email address, home
address, assured date number etc.

REQ.2

3.1 System features

Database login page

The login interface is for entering the username and password fields for validating is the user is valid or
not.

User Interface: Login Form- Mandatory fields

 Username
 Password

Expected Input- Username and Password.

Expected Output  Display the operator home page if the user provides the valid username and
password.

Use case for registration

Registration interface is for entering the details of specific operator for persist the data permanently.

User Interface- Registration Form:

 First name
 Last name
 Email ID
 Mobile No
 Address
Expected Input - Expected input is after entering the mobile no computer operator performs a
search whether that mobile no already exists or not. If the mobile no already exists in the
database.

4.EXTERNAL INTERFACE REQUIREMENTS


4.1 User interface
 For customers, agents, and employees, the system shall provide a registration
form.
 The system will offer an interface so that employees in the department of
verification can send a status report to the departments of finance and legal
contracts. In case a user has trouble using the program, system will offer a help
link that will download a user manual and display it on the screen.
 The system will inform the client that their details have been recorded.

4.2 Hardware interfaces

The list of server-side basic requirements is shown below.

 Processing unit: Pentium III


 Memory: 256MB RAM, 1.0 GHz
 Hard Drive: 40GB Hard Drive with at least 4GB of empty space
 User Interface: Mouse and Keyboard and any computer that can operate a web browser
on the client side.

4.3 Software interfaces

 Browsers- Mozilla Firefox, Chrome, Internet Explorer


 Operating system- Windows, Linux
 Server- Php
 Database- MySQL.

4.4 NON-FUNCTIONAL REQUIREMENTS

Performance requirements

The system should satisfy standards like modern web techniques like caching should be used to
speed up the loading of dynamic pages. Each page on the site needs to load in a reasonable
amount of time. The number of simultaneous users will increase as a result of the quicker
connection release.
4.5 Software quality attributes

Maintainability- It is easier to understand and operate hence making it easier to maintain. Being
a dynamic system, we must generate high, professionally written dynamic output.

Availability- due to feasibility it is easier to access the system and operate.

Reliability- The web server on which the system will be housed, as well as the login procedures,
both affect the website's dependability.

Security-Due to the fact that all member data is confidential belonging to the client's
organization all required measures have been taken to ensure the system’s security using the
most recent technology.

REFERENCES

www.studocu.com

https://sites.google.com

https://www.scribd.com

www.w3schools.com

GLOSSARY

PHP- Hypertext Preprocessor" · PHP is a widely-used, open-source scripting language · PHP


scripts are executed on the server ·

MySQL-is an open-source relational database management system (RDBMS).

RDBMS- Relational Database Management System. A program used to maintain a relational


database.

VPN- Virtual Private Network. A VPN, in its simplest form, offers an encrypted server and
conceals your IP address from businesses, authorities, and would-be hackers. When using
shared or public Wi-Fi, a VPN secures your identity and keeps your data hidden from snooping
online eyes.

You might also like