Leave Management System: (Type The Document Subtitle)

KINGSTON PUBLIC HOSPITAL
Leave Management System

[Type the document subtitle]
Group 8
This is a leave management system that is critical for HR tasks and keeps the record of vital
information regarding working hours and leaves. It intelligently adapts to HR policy of the
management and allows the nurses and the Executive nurses to manage leaves and
replacements (if required). The Human Resource Manager (HRM) will have permissions to
look after data of every nurse in each ward of the hospital. HRM can approve leave through
this application and can view leave information of every individual. This will also allow nurses
to view their work schedule and leave days available.
1. INTRODUCTION
The following subsections of the Software Requirements Specifications (SRS) document provide
an overview of the entire SRS.
1.1 DOCUMENT PURPOSE

The purpose of this document is to show the software requirements of the Leave Management
software. The functionality and scope of this software are described in this SRS document.
1.2 PRODUCT SCOPE

The Leave Management software aims at helping the HRM to address issues from multidisciplinary angles related to leave management.
The major benefits of this software are
1.It is a unique software which helps to organize event without the need for paperwork.
2.It has a wide variety of Modules.
By just a few clicks nurses can check the leave status, leave balance, notices and apply for and
grant leave accordingly.
1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW

This SRS document is intended for nurses, executive nurses of the Kingston Public Hospital. The
rest of the document contains the functional and non-functional requirements of Leave
Management System.
1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

LMS - Leave Management System.
LB Leave balance.
SRS- Software Requirement Specification.
Servers: Machines that store all the information and records.
2. OVERALL DESCRIPTION
Describes the general factors that affect the product and its requirements. This section
does not state specific requirements. Instead it provides a background for those
requirements, which are defined in section 3, and makes them easier to understand.
2.1 PRODUCT PERSPECTIVE

It is aimed at replacing the tedious paper works that the companies or colleges currently use. The
system will collect data and store it for fast and easy reference. The system will provide users
with complete record of the attendance and leaves. It will also provide information about the
leave balance (availability).The system is thus helpful to reduce the time and complexity of
maintaining the records.
1
2.2 PRODUCT FUNCTIONALITY

Some major product functionalities of the system are as follows:
Information about the employee/student/staff attendance.
Check for leave availability.
Maintain employee leave record.
Display notices.
Apply for leave.
Approve or reject leave application.
2.3 USERS AND CHARACTERISTICS

Primary users of the system will be nurses, executive nurses, HRM, Admin. Very little technical
expertise is required for reading the outputted data since it is in graphical/tabular form.
Educational level of LMS computer software Low
Experience of LMS software None
Technical Expertise Little
2.4 OPERATING ENVIRONMENT

Open source, Windows, HTML.
2.5 DESIGN AND DEVELOPMENT CONSTRAINTS

Cost to develop, Minimal training, User-friendly, Security based System, Validation of Users,
very fast response time, Hardware Cost.
2.6 USER DOCUMENTATION

A link is provided for help and very easy User Interface.
2.7 ASSUMPTIONS AND DEPENDENCIES

Assume that all the information entered by the user will be correct. If any wrong information
found then system will notify an alert. The system is required to save generated reports.
3. SPECIFIC REQUIREMENTS
3.1 External Interface Requirements
3.1.1 User Interfaces
The User Interface Screens are described in table 1.
Table 1: Leave Management User Interface Screens
Screen Name
Description
Login
Log into the system.
Nurse
Display attendance of nurses, number of leaves, leave balance.
Add or update employee records.
Apply for leave
Display leave availability, application for leave, cancel
application. Add or update leave allotment records
Leave records
Display leave history.
Approve/reject leave
Display leave availability and application form. Add or update
2
Screen Name
Application
HRM
Description
records.
Add or update staff records Create, modify, and delete staff
member.
Select, view, save, and delete reports
Reports
3.1.2 Hardware Interfaces

The system shall run on:
Operating system: Any Windows OS.
Scripts which supports CGI, HTML & JavaScript.
Web Browser: Google Chrome, Mozilla Firefox, Internet Explorer and Opera.
3.1.3 Software Interfaces

The system shall interface with an Oracle or Access database.
To implement the project we have chosen HTML language for its more interactive and easy to
understand support.
3.1.4 Communications Interfaces

This System supports Google chrome and Mozilla Firefox web browsers.
This System involves FAQ forms for the requesting information, queries and problems etc.
3.2 Functional Requirements
System will keep nurse records

System provides Information about the leave approval and leave availability.
Display leave history.
Display work schedule.
4. NON-FUNCTIONAL REQUIREMENTS
Non-functional requirements define the needs in terms of performance, logical database
requirements, design constraints, standards compliance, reliability, availability, security,
maintainability, and portability.
4.1 PERFORMANCE REQUIREMENTS

Performance requirements define acceptable response times for system functionality.
The load time for user interface screens shall take no longer than two seconds.
The log in information shall be verified within five seconds.
Queries shall return results within five seconds
The system shall consume very little of primary memory
4.2 SECURITY REQUIREMENTS

Nurses and Managers will be able to log in to the Leave Management System. Customer Service
Representatives will have access to the leave management and scheduling subsystems. Managers
will have access to the Management subsystem as well as the leave management and scheduling
subsystems. Access to the various subsystems will be protected by a user log in screen that
requires a valid UserId.
4.3 SOFTWARE QWALITY ATTRIBUTES

4.3.1 Standards Compliance
There shall be consistency in variable names within the system. The graphical user
interface shall have a consistent look and feel.
4.3.2
Reliability
Specify the factors required to establish the required reliability of the software system at time of
delivery.
4.3.3 Availability
The system shall be available 24/7.
4.3.4 Maintainability
The Leave Management System is being developed in Java. Java is an object oriented
programming language and shall be easy to maintain.
4.3.5 Portability
The Leave Management System shall run in any Microsoft Windows environment that contains
Java Runtime and the Microsoft Access database.
CRITERIA
ALTERNATIVE A
ALTERNATIVE B
ALTERNATIVE C
(IN-HOUSE
Developers)
(PACKAGED
SOFTWARE
PRODUCERS)
(CLOUD COMPUTING)
YES
YES
YES
YES
YES
YES
YES
YES
YES
REQUIREMENTS
1. Easy real-time
entry of nurse
records
2. Display leave
approval and
leave
availability.
3. Display leave
history
4. Display
working hours.
CONSTRAINTS
Cost to develop
NONE
$10,000
$4,000 per month
Minimal
training
required
1 Hours
1.5 Hours
1.2 Hours
User Friendly
(rated out of 5)
4.5
Fast Response
Time
(rated out of 5)
YES
YES
YES
Validates users
CRITERIA
WEIGHT
ALTERNATIVE A
ALTERNATIVE B
ALTERNATIVE
Rating
Score
Rating
Score
Rating
Scor
REQUIREMENTS
Real time data
entry
14
70
70
70
Leave approval
and availability
14
70
70
56
Leave history
12
36
36
36
Working hours
10
50
50
50
226
226
212
Constraints
Development cost
14
70
49
2.5
35
Ease of Training
20
16
4.5
18
User-friendly
32
4.5
36
32
Response Time
32
40
40
Validate User
30
18
4.5
27
Hardware Cost
10
50
30
50
Total
100
234
189
202
460
415
414
Weighted approach for comparing the three alternative systems for the leave
management system.
Alternative A would be the best choice because it has the highest score.

Leave Management System: (Type The Document Subtitle)

Uploaded by

Copyright:

Available Formats

Leave Management System: (Type The Document Subtitle)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Leave Management System: (Type The Document Subtitle)

Uploaded by

Copyright:

Available Formats

KINGSTON PUBLIC HOSPITAL

Leave Management System

1.1 DOCUMENT PURPOSE

1.2 PRODUCT SCOPE

1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW

1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

2.1 PRODUCT PERSPECTIVE

2.2 PRODUCT FUNCTIONALITY

2.3 USERS AND CHARACTERISTICS

2.4 OPERATING ENVIRONMENT

2.5 DESIGN AND DEVELOPMENT CONSTRAINTS

2.6 USER DOCUMENTATION

2.7 ASSUMPTIONS AND DEPENDENCIES

3.1.2 Hardware Interfaces

3.1.3 Software Interfaces

3.1.4 Communications Interfaces

3.2 Functional Requirements

System will keep nurse records

4.1 PERFORMANCE REQUIREMENTS

4.2 SECURITY REQUIREMENTS

4.3 SOFTWARE QWALITY ATTRIBUTES

$4,000 per month

You might also like