SRS DOCUMENT

Introduction:
The following section of the Software Requirements
Specifications (SRS) document provides an overview of the entire SRS.

Purpose:
The SRS document will provide a detailed description for the
requirements for building the utility software. This SRS will provide the
foundation for the project. This SRS will allow for a complete understanding
of what is to be expected of the utility software to be constructed. The
understanding of the utility software and its functionality will allow for the
correct software to be developed for the end user and will be used for the
development of the future stages of the project.

Scope:
There are many operations that are to be done using the software.
The major operation of utility software is to provide the option for the user to
perform different tasks such as adding and employee, updating employees
record, database management system, attendance portal and admin control
to all operations.

Overview:
The SRS is organized into two main sections. The first is the
overall description and the second is the specific requirements. The overall
description will describe the requirements of the software from a general
perspective.

The overall description:

This section describes the general factors that affect

the product and its requirements. Instead it provides a background for
requirements or functionality and makes them easier to understand.

Product perspective:
The Bank Employee Management Portal is a new idea.
The project is designed to facilitate higher level authorities to keep check on
the employees attendance and to access their record. It will create a time
saving environment with full admin control.

Product functions:
The function of the product is to:
1) Adding employee in database.
2) Search facility in system.
3) Updating record of employee.
4) Employee can mark attendance and can view his record.
5) Employee can access his salary slip status.
6) Admin can access employees record and can modify it.

User classes and characteristics:

The users of this project include the administrators,
end-users and developers. The users have a differentiated access according
to its security level and availability. End-users are the employees.

Functional requirements:
After the portal is opened, the employee or admin
(user) will be asked for username and password also eye recognition will be
implemented on further demands so user could access the portal according

to the securities granted by developers and admin. There will be categorized

panel which would allow user to perform certain operations as mentioned
above.

Non-Functional requirements:
-

The system response time must be less than 10 seconds.

Once an error has occurred the system should
automatically save and log out.
All the data in the system must be backed up after every
24 hours and the copies must be stored safely also
changes should be backed up on account.
Admin should know about the attendance record of
employee easily.
The triple constraints (time, cost, scope) must be properly
discussed .The system shall be delivered as quickly as
possible and the financial limitations of resources input to
the project must be vast.

Software Quality Attributes:

-

Once the software is launched, it must be available for

banks.
The system must not require installation for users.
For the updates and maintenance of the system, the
source code must be well documented.
The system should provide accurate and updated
information for the users.
The system should be well designed to allow easy usage.
The GUI of the system must provide those buttons that
could be easily understandable by the users.