Sei sulla pagina 1di 4

167084 Pratigya Sharma

Chapter Write Up

Systems Considerations in the Design of a Human Resource Information System

The chapter talks about the importance of understanding the system development process for
HRIS to improve the design of HRIS. We are already familiar with the fact that we are not
supposed to rush through the system development process starting from design to
implementation to evaluation. Therefore, this chapter makes us focus on such critical
considerations that are to be taken while developing a system. Even when the system is perfect
from the design point of view, it might not be enough. Proper understanding of the users/clients
is very necessary to make sure that our software is a good fit of the organization.

HRIS Customers/Users: Data Importance

The users of such system can be divided into two groups; employees and non-employees. More
groups can be formed according to the requirement of the organization.

Employees: The users that need to be using the software (frequently or seldom) from inside the
organization fall under this category. They work for the organization therefore for the day to day
operation they need to be using this HRIS software. Some of the users of HRIS software that fall
under this category are; managers, CEOs, HR managers, employees etc.

Non-employees: The users that do not belong to the organization but still are related to the
organization fall under this category. They are not really frequent users of the software but they
must also be taken under consideration while designing this HRIS software. For example;
suppliers, partners, outsourcing companies etc.

As is apparent in the past areas, every client or client of the HRIS has various necessities with
respect to what data the individual in question will utilize. A few clients just info information
and data, a couple just gander at information and data gave as reports, while a couple of others
investigate the information furthermore, data to decide. What these clients all share for all intents
and purpose is that all the data is about potential and current workers with an emphasis on
dealing with the association's human cash-flow to improve dynamic and help to accomplish vital
hierarchical objectives.
167084 Pratigya Sharma

HRIS Architecture

The HRIS “Dinosaur”

Mainframe computers were used to usually do work related to payroll. The users could access it
through their desktops but cannot do any processing. This is called single tier architecture. One-
tier architecture involves putting all of the required components for a software application or
technology on a single server or platform. Basically, one-tier architecture keeps all of the
elements of an application, including the interface, Middleware and back-end data, in one place.

Client-Server (Two-Tier) Architecture

Previously large mainframe computers were used for processing; they realized that it could be
done in their personal computers reducing the cost. Therefore they introduced this client server
architecture. A two-tier architecture is a software architecture in which a presentation layer or
interface runs on a client, and a data layer or data structure gets stored on a server. Separating
these two components into different locations represents two-tier architecture, as opposed to a
single-tier architecture. After introduction of this, high powered work would still be done in the
large mainframe computers but the day to day operations were at ease by using PCs.

And the process of development did not stop at all. It continued to grow. Through this process of
trial and error architectures such as three tires and n-tiers were introduced and used by
companies. This definitely reduced the load.

Cloud Computing

In the latter half of the 2000 decade, a new architectural model has become prevalent, called
cloud computing. Cloud computing can be defined as a computing architecture that uses the
Internet and central remote servers to maintain data and applications. Hosted services are then
delivered over the Internet. Cloud computing technology allows businesses to use applications
without having to go through the complex installation process. Companies provide the following
services:

• Infrastructure as a Service (IaaS)


167084 Pratigya Sharma

 Platform as a Service (PaaS)


 Software as a Service (SaaS)

The cloud service providers now maintain sensitive corporate data. So when choosing a cloud
solution, the evaluation process must include a thorough security analysis.

Security Challenges

• Reveal of delicate finance and advantages information between workers


• Loss of touchy work force information outside the venture, (for example, Social Security
numbers)
• Unauthorized updates of key information, for example, compensation sums, investment
opportunities (both amount and dates), and so on.
• Sharing of work force or candidate audit remarks with unapproved representatives
• Sharing information with outside associations and specialist co-ops

Best of Breed

An architecture that combines products from multiple vendors is called best of breed (BOB). For
them to work properly the following conditions need to work out:

• First, there should be a perceived need for a specialized solution.


• Second, a universally agreed-on set of guidelines for interoperability must exist between
applications
• Third, applications need to “speak the same language.”

If the above conditions are met, HRIS applications should be able to interoperate with many
point solutions for any of the HR programs in the organization such as:

Recruitment

Time collection

Payroll

Benefits
167084 Pratigya Sharma

Planning for System Implementation

There are many authors spread far and wide all over the world that suggest 14 steps or 8 steps
long process of implementation. This clearly tells us the importance of implementation. In those
steps the first step is always planning. This is a totally basic advance in any business procedure
and particularly in the structure of any huge scope programming execution including numerous
procedure interfaces. Note that plamming doesn't ensure achievement—rather, it builds the
likelihood that the usage will be effective.

The chapter finishes up with a general conversation of the means that associations may take to
plan and actualize an HRIS and of the elements that can influence these procedures. A short
conversation of the change ways to deal with "going live" with the new HRIS represents the
decisions accessible to associations when exchanging over to the new framework. In outline,
associations that can deal with the individuals, procedures, and innovation engaged with a HRIS
execution ought to be bound to find that the new HRIS can meet their objectives all the more
viably as far as spending plan, usefulness, and ease of use