Professional Documents
Culture Documents
Version:
Date: 14-03-2011
Organization:
0.1
Version 0.1
http://www.ciit.net.pk
Page 1
Version:
Date: 14-03-2011
Organization:
0.1
Revision History
Date
21-02-2011
Version
0.1
Description
Initial Draft
http://www.ciit.net.pk
Author
Manzoor Ahmad
Page 2
Version:
Date: 14-03-2011
Organization:
0.1
Table of Contents
1. Introduction
1.1
1.2
Intended Audience
1.3
Scope
1.4
1.5
References
2.
Exective Summary
3.
Requirements Description
4.
3.1
Introduction
3.2
General Requirements
3.3
Specific Requirements
1.
2.
3.
4.
5.
6.
Payroll Module
7.
8.
9.
10.
Requirements Definition
4.1
http://www.ciit.net.pk
Page 3
Version:
Date: 14-03-2011
Organization:
0.1
4.2
Requirement Sources
4.3
2.
3.
4.
5.
6.
Payroll Module
7.
8.
9.
10.
http://www.ciit.net.pk
Page 4
Version:
Date: 14-03-2011
Organization:
0.1
1. Introduction
This document is a summary of a detailed analysis of the processes operating in Human
Resources and takes carried out by Human Resource department. The purpose of this document
is to define the scope of user requirements. It is important to note that this represents a broad
range of desirable user requirements, not all of which can necessarily be achieved. The existence
of an item/requirement in this document does not mean that it can be achieved, but that it has
been requested by users. The development priorities will be identified within the project plan.
1.1
Convey the software development teams understanding of the business needs of the
Human Resource department that can benefit from appropriate Information Technology
intervention, and
Provide the Senior Management Team of COMSATS IT Center with the System
Requirements Specification (SRS) for Human Resource Management System.
Collect, analyze, and define high-level needs and features of Human Resource
Management System. It focuses on the capabilities needed by the target users, and why
these needs exist. The nature of this report is kept as simple as possible so that the issues
can be understood by the audience
The SRS is intended for rigorous consideration by the Senior Management Team prior to
commencement of the design/implementation of the proposed Human Resource Management
System (HRMS) that is intended to satisfy the expressed needs of the Human Resource
department. This SRS outlines the requirements as obtained and understood by the CITC
software development team from meeting with HR officer and interviews conducted with HR
staff, direct observation of select aspects of HR departments business operations, review of
secondary sources of information/documentation, and interaction with existing HRMS solutions
owned and operated by HR department of COMSATS institute of Information Technology,
Abbottabad. To complete the verification aspect of this engagement, this was carefully review by
the Senior Management Team of the CITC.
Copyright 2011 CITC Abbottabad
http://www.ciit.net.pk
Page 5
Version:
Date: 14-03-2011
Organization:
1.2
0.1
Intended Audience
The intended audience of this document is the members of Project Team and Senior Management
Team of CITC and duly authorized representatives of the HR department that are directly
involved in the delivery of the proposed Human Resource Management System. This document
gives an overview to the audience about the requirements, what exactly is expected out of the
project. It includes:
Customer
Steering group
1.3
Scope
This document defines at a functional level the business activities that are encompassed by the
proposed Human Resource Management System. It also encompasses the key high-level technical
requirements of system required to support business processes within environment. This
document contains working and concepts implementation for our system. The specifications
provided in this document are based on a preliminary system analysis, and are not final.
The scope of the detailed analysis phase specifies that it will include:
Conduct systems analysis and document the System Requirements Specification (SRS)
complete with functional/non-functional specification for the design and implementation
of HRMS for Steering Group.
The scope of the analysis phase, for which this document forms the deliverable, does not
include technical software specification intended for software development team. These
specifications must be produced in the application delivery phase, based on the results of
the detailed analysis and feedback from the review and requirements sign off activities
which this document is intended to facilitate.
1.4
1.4.1 Definitions
Keyword
Project Manager
Copyright 2011 CITC Abbottabad
Definitions
Person responsible for team management and organization. He
http://www.ciit.net.pk
Page 6
Version:
Date: 14-03-2011
Organization:
0.1
Milestone
Steering Group
Definitions
Abbreviation
HRMS
SRS
CITC
CIIT
IS
Information System
ICT
HEC
TTS
1.5
References
There are some study material provided for studying rules and status as
2.
http://books.google.com/books?id=_Q_vQMuYeHQC&source=gbs_navlinks_s
http://en.wikipedia.org/wiki/Component-based_software_engineering
Executive Summary
Institutional
knowledge-
business
intelligence,
performance
and
http://www.ciit.net.pk
Page 7
Version:
Date: 14-03-2011
Organization:
0.1
As a means of addressing the above and in support of the delivery, operation and
maintenance of the Human Resource Management System, we recommend that
the CITC must setup an effective IT Governance mechanism, prioritize its ICT
investments and institutionalize appropriate ICT strategies, principles etc,
establish appropriate standard/protocols for data governance to ensure that data
is handled consistently across the organization, and institutionalize a human
resource management and recruitment program that will facilitate the
continuous development of requisite information literacy skills within the CIIT.
Information Systems delivery life cycle from identification of problems/needs, to
Copyright 2011 CITC Abbottabad
http://www.ciit.net.pk
Page 8
Version:
Date: 14-03-2011
Organization:
system
0.1
specifications,
to
system
procurement/development,
deployment,
http://www.ciit.net.pk
Page 9
Version:
Date: 14-03-2011
Organization:
0.1
3.
Requirements Description
3.1
Introduction
This System Requirement Specification (SRS) outlines the issues and business needs that must
be addressed for the successful implementation of the proposed Human Resource Management
System that will offer appropriate ICT support for the CITC to satisfy its mission and achieve the
strategic goal of Customer Satisfaction. It is important to note that the Human Resource
Management System, like all Information Systems (IS), is made up of six fundamental
components. These components are interdependent, and the weakness in any one component
determines the overall strength of the Information System. The six fundamental components are:
1. Software used to support the business functions
2. Hardware used to support the software and communication
3. Data to be processed
4. Business procedures and rules to ensure that data is processed accurately and
consistently
5. Technical support personnel to maintain the network, hardware and software
6. Users who input the data and retrieve output for decision making
This SRS is developed in view of all of the above components. All components must operate
optimally for the success of the Human Resource Management System.
3.2
General requirements
The Human Resource Management System must support and be compatible with
Data Conversion of existing data to electronic format suitable for integration into the
Human Resource Management System when it is commissioned
Control user access to data and functionality based on rolebased and userbased
permissions
http://www.ciit.net.pk
Page 10
Version:
Date: 14-03-2011
Organization:
0.1
All userinterfaces must be simple and intuitive to use (attention must be placed on
usability evaluation, taking into account Nielsens Usability User Interface Evaluation
guidelines)
Quality Customer Care, care training for staff with a high level of Customer contact
time. Overall, during the period of the maintenance, customer care appeared to be one of
the CITCs major strengths. Nonetheless, an institutionalized training program will
ensure that customers are treated consistently.
3.3
Specific Requirements
In this Section we elaborate the requirement specification for the proposed Human Resource
Management System. First, we discuss the high level requirements for the system, which are
classified in modules as follows:
1. Admin Control & User Management Module
2. Recruitment Processing Module
3. Employee Management Module
4. Leave Management Module
5. Establishment Activities Processing Module
6. Payroll Module
7.
http://www.ciit.net.pk
Page 11
Version:
Date: 14-03-2011
Organization:
0.1
Add/edit job status, grade types (Regular grade, TTS grade, foreign faculty grade etc.)
grade, designation, department, city, country,
http://www.ciit.net.pk
Page 12
Version:
Date: 14-03-2011
Organization:
0.1
Without an employee information management, it is a tedious job for the Human Resource
department of any company. Employee Management Module (EMM) aims to simplify the
Human Resource management of organization. EMM will store all the details of the
employees including
their background
information,
educational
qualifications, past
Full name
Employee Id (Personal File Number)
Photograph
Designation
Grade (Pay Scale/Grade)
Department
Address
Date of Birth
Date of Joining
Date of leaving
CNIC
Marital status
Dependents (Family member that are dependents on employee)
Contact number
Educational qualifications (graduation & above)
Past experience
Performance in the company
Miscellaneous information
Information about promotions
Gender
Projects worked on
job responsibility
Specialization
Email address
http://www.ciit.net.pk
Page 13
Version:
Date: 14-03-2011
Organization:
0.1
http://www.ciit.net.pk
Page 14
Version:
Date: 14-03-2011
Organization:
0.1
remuneration, and different reports against deduction and allowances on request of Higher
Management Authority.
7.
Document archiving & File Tracking will enable the Record Office, HR Office and other
divisional/departmental registries to effectively and securely manage and maintain
files/documents
originating
from
meetings,
correspondences
and/or
generated
from
engagements between the University, its employees and customers. This system will facilitate
the digitization and ease of circulation and tracking of files/documents checked in and out of
the respective departments, recording of annotations made on the original paperbased
documents, and reporting on the history of staff interaction with specific files/documents.
Further, system facilitate ease of access to files/documents, over the LAN/WAN, to alleviate
the major risks, such as deterioration of paper, lost and misplaced files, associated with
manual file/document filing and archiving systems.
Note: Software Requirement Specification of following module will be included in next version of
this document.
8. Research Project & Publication Module
9. Attendance & Shift Management Module
10. Performance Development Planning Module
http://www.ciit.net.pk
Page 15
Version:
Date: 14-03-2011
Organization:
4.
Requirements Definition
4.1
Identification
Requirement Group
ACUM
RP
Recruitment Processing
EM
Employee Management
LM
Leave Management
EAP
PR
Payroll
DAFT
RPP
ASM
PDP
4.2
0.1
Remarks
Requirement Sources
Source
Customers
Description
Remarks
Software Development
Team
4.3
http://www.ciit.net.pk
Page 16
Version:
Date: 14-03-2011
Organization:
0.1
the users to log in and identify themselves, typically with a password. Authorization relates to
the privileges that a user may be given in order to do something to (for example add, edit or
delete) a record.
User Management is an authentication feature that provides administrators with the ability to
identify and control the state of users logged into the system. This includes, but is not limited to,
the ability to query and filter users that are currently logged into the system, manually log out
users, and control user login counts and login times. Most security-conscious enterprises today
implement some form of authentication and authorization for accessing system. The benefits to
this approach are clear user permissions can be verified before granting access to system, and
user activity can be monitored through various logging mechanisms.
The management of user will be discussed, and this knowledge will be consolidated by creating a
new administrator or user and adding and removing their administrative/user privileges
Functional Requirements
Detail features of this module are described here;
ID
Status
Priority
ACUM-001
High
Description
Ability provide support to authenticated user to
Source
Customer
High
ACUM-003
High
Customer
role.
Ability to create/modify user and assign role to
Customer
user.
ACUM-004
High
Customer
ACUM-005
High
Customer
ACUM-006
High
Customer
ACUM-007
High
Customer
http://www.ciit.net.pk
Page 17
Version:
Date: 14-03-2011
Organization:
0.1
with candidates and clients. RPM will also reduce the amount of paper work required by HR
officer. RPM allows HR officer to follow the recruitment process from the candidates side and
from the clients side. This means that changes made in a clients process that are related to a
candidate will also show up in the candidates profile.
Recruitment of staff is guided by the University Recruitment and Selection policy. Recruitment
Processing Module provides a full recruitment and selection service, dealing with the majority of
all recruitment. There is a limited element of devolution where departments are responsible for
dealing some aspects of the recruitment process for certain types of posts, e.g. research. Posts can
be funded in different ways and this determines one of two routes for approval involving the
department management, Finance Office and HR department
Functional Requirements
An integrated module will available with the following functionality;
ID
Status
Priority
Description
Source
RP-001
High
Customer
High
Customer
High
Customer
High
Customer
High
Job/Position
appropriate
Classification;
pay
ranges;
identification
appropriate
of
Customer
status
High
Customer
closing,
job
descriptions,
SOPs
and
http://www.ciit.net.pk
Page 18
Version:
Date: 14-03-2011
Organization:
0.1
RP-007
RP-008
High
Customer
Customer
criteria.
RP-009
High
RP-010
Medium
Customer
Customer
of standard letters
RP-011
High
RP-012
High
Recording
of
placement
history
(position
Customer
Customer
offered/decline/rejection).
reporting
of
equal
opportunities
data,
High
Customer
RP-014
High
Constitution
Customer
of
selection
board/committee,
High
Customer
that post.
Contract acceptance by the successful
applicant will trigger the new employee
record and unique identifier at the time
acceptance received.
A current member of staff being appointed
to a new post will be correctly identified as
current staff and their identifier will be
retained.
RP-016
High
Customer
High
Customer
Page 19
Version:
Date: 14-03-2011
Organization:
0.1
RP-018
Medium
Collection
of
job
details
from
Customer
online
database,
then
once
recruitment system.
Provide the ability to hold job descriptions
associated with a vacancy as part of the
database. This would allow the data to be
re-used, for other recruitment or to refer to
RP-019
Medium
profile maintenance.
applicant
screening
o
o
employee
Applicant SelfService (applying,
viewing,
mapping
competencies,
and
for
skills
Customer
job
to
and
managing
Medium
Customer
Page 20
Version:
Date: 14-03-2011
Organization:
0.1
RP-021
Medium
Customer
Medium
Customer
The University requires accurate and up to date records of faculty, officer staff
and other individuals to be able to automate routine administrative actions
where possible. One of the major objectives is to ensure this information forms
the spine used across the institution. Contractual administration is a large
element of the routine work carried out jointly between administration, HR and
teaching departments
Functional Requirements
An integrated module will available with the following functionality;
ID
Status
Priority
Description
Source
EM-001
High
Customer
High
Customer
High
Customer
High
Customer
http://www.ciit.net.pk
Page 21
Version:
Date: 14-03-2011
Organization:
EM-005
0.1
High
Creation
of
contracts
of
employment.
This
Customer
Customer
High
Customer
leaving
and
destination.
Information
Medium
Customer
High
Customer
management
of
clinical
honorary
High
EM-011
Medium
Customer
Ability
medical
Customer
Customer
to
hold
pre-employment
information
EM-012
Low
Low
Customer
http://www.ciit.net.pk
Page 22
Version:
Date: 14-03-2011
Organization:
0.1
Status
Priority
LM-001
High
Description
Ability
to
define
organization
Source
calendar
Customer
High
Customer
LM-003
High
Customer
High
Customer
High
Customer
http://www.ciit.net.pk
Page 23
Version:
Date: 14-03-2011
Organization:
0.1
LM-006
High
Customer
High
leaves
online
using
web
Customer
browser.
LM-008
Medium
Leave
management
module
allows
managers
Customer
http://www.ciit.net.pk
Page 24
Version:
Date: 14-03-2011
Organization:
0.1
be stressed that this is not an establishment in terms of a set number of post to a department as
the staffing is dependent on that Faculty/Resource Units cash-limited budget and external funds.
It is only that the method of recording posts is by human resource department which can be
different from the financial ledger costing structure.
Organizational hierarchy is provided by an interfacing system and this requires to be developed
to record and maintain a true picture of the hierarchy including sub-departmental units as
required.
Functional Requirements
All above mention functionalities are addressed by Establishment Activities Processing Module.
Detail features of this module are described here;
ID
Status
Priority
EAP-001
High
Description
Source
Customer
notification
EAP-002
High
Customer
EAP-004
High
High
plenty etc.
Salary revision
Defer increment
Customer
Customer
High
Customer
designation
and
may
transfer
to
new
department.
EAP-006
High
Customer
http://www.ciit.net.pk
Page 25
Version:
Date: 14-03-2011
Organization:
0.1
EAP-007
High
Customer
EAP-008
High
Customer
High
Customer
EAP-010
High
Customer
High
Notices/Alert,
Discipline
and
Grievance
Customer
Customer
High
High
Customer
EAP-014
High
Customer
grievance issues
EAP-015
High
Customer
6. Payroll Module
Description & Priority
The Payroll section currently creates and amends employee records as well as carrying out
payroll responsibilities manually. The payroll department is part of the Finance/account Office.
Currently there are different payroll runs per month, and in future the payroll section will be
responsible for paying pensioners. Payroll is responsible for monitoring, controlling and paying
Copyright 2011 CITC Abbottabad
http://www.ciit.net.pk
Page 26
Version:
Date: 14-03-2011
Organization:
0.1
expenses each month. There is a considerable number of regular, Tenor Track System (TTS),
foreign faculty, daily wages casual staffs who are currently dealt with exclusively by Payroll and
this activity will be addressed by regularizing the situation in compliance with employment law,
and changes necessary to systems and processes will take account of this.
Pensions are housed within the Payroll section. The payroll record provides their source of
employee information and there is scope to improve the information flow.
Functional Requirements
This section details the Payroll sections main responsibilities after HR assume responsibility for
driving the system. The underlying principle is that processes HR drives are automated where
currently manual. There is a large knowledge base that must be transferred from Payroll to
Personnel with following functionalities;
ID
Status
Priority
PR-001
High
Description
Ability to add/view/update allowances/payments
Source
Customer
High
Customer
High
Customer
detail.
PR-004
High
Customer
High
Customer
records for;
Statutory Allowances/payments and
deductions such as Tax, Group insurance,
Copyright 2011 CITC Abbottabad
http://www.ciit.net.pk
Page 27
Version:
Date: 14-03-2011
Organization:
0.1
PR-006
High
Customer
statutory information
calculating adjustments for mid-month,
backdated changes
PR-007
High
Customer
PR-008
High
Customer
PR-009
High
Customer
High
Customer
High
Loan
management
of
employee
against
CP
Customer
fund/GP fund.
PR-012
high
Customer
http://www.ciit.net.pk
Page 28
Version:
Date: 14-03-2011
Organization:
0.1
Functional Requirements
The Document Archiving and File Tracking system must have following features;
ID
Status
Priority
DAFT-001
High
Description
Source
Customer
forms,
Applications,
and
High
Provide
mechanism/standalone
Customer
committee
decisions
and
circulation.
DAFT-003
High
Customer
High
Customer
High
Customer
These
annotations
must
Customer
http://www.ciit.net.pk
Page 29
Version:
Date: 14-03-2011
Organization:
0.1
DAFT-007
Customer
10.
Requirement status:
I = initial (this requirement has been identified at the beginning of the project),
D = dropped (this requirement has been deleted from the requirement definitions),
H = on hold (decision to be implemented or dropped will be made later),
A = additional (this requirement was introduced during the project course).
Action
Date
Comments
Requirement status:
D = dropped (this requirement has been deleted from the requirement definitions),
H = on hold (decision to be implemented or dropped will be made later),
A = added (this requirement was introduced during the project course).
Copyright 2011 CITC Abbottabad
http://www.ciit.net.pk
Page 30
Version:
Date: 14-03-2011
Organization:
0.1
http://www.ciit.net.pk
Page 31