Professional Documents
Culture Documents
Chapter 04
Chapter 04
What are some critical success factors for effectively conducting an analysis of HRIS
needs?
1. Define objectives and goals: Before conducting an analysis of HRIS needs, it is essential to
define the objectives and goals of the organization. This will help in identifying the
functionalities required in an HRIS system.
2. Involve stakeholders: Involve all stakeholders, including HR managers, IT professionals, and
end-users, in the analysis process. This will help in identifying the requirements and challenges
faced by each stakeholder and finding a solution that meets everyone's needs.
3. Assess current processes: Conduct a thorough assessment of the current HR processes,
including recruitment, training, performance evaluation, and compensation. This will help in
identifying the areas that require improvement and the functionalities required in an HRIS
system.
4. Prioritize requirements: Prioritize the requirements based on their importance and the impact
they will have on the organization. This will help in selecting an HRIS system that meets the
critical requirements.
5. Consider scalability: Consider the scalability of the HRIS system. The system should be able to
handle the organization's growth and expansion.
6. Consider user-friendliness: The HRIS system should be user-friendly and easy to use. It should
not require extensive training for the end-users to use the system.
7. Consider cost: Consider the cost of the HRIS system, including the implementation cost,
maintenance cost, and training cost. Select an HRIS system that meets the organization's
budget.
The following are the typical STAGES OF THE SYSTEMS DEVELOPMENT LIFE CYCLE :
1. Planning: In this stage, the project team defines the problem statement, project scope, objectives, and
deliverables. The team conducts a feasibility study to assess the project's viability and identifies the
stakeholders, risks, and constraints. The project team develops a project plan that outlines the project's
schedule, budget, and resources required.
2. Analysis: In this stage, the project team analyzes the requirements of the software system. The team
identifies the user requirements, functional requirements, and non-functional requirements such as
performance, security, and scalability. The project team documents the requirements in a requirements
specification document.
3. Design: In this stage, the project team develops the software system's architecture, data model, and
user interface design. The team selects the appropriate development platform, programming language,
and tools. The project team documents the design in a design specification document.
4. Implementation: In this stage, the project team develops the software system using the selected
programming language, tools, and platform. The team codes the software system according to the
design specifications. The team also conducts unit testing to verify that the code meets the
requirements.
5. Maintenance: In this stage, the project team maintains the software system by fixing any bugs or issues
that arise, making updates to the software system, and providing support to end-users. The team may
also conduct periodic reviews of the software system to identify areas for improvement.
Corrective Maintenance—There will be times that despite the best efforts of designers and
implementers, something in the system doesn’t work properly and must be
Adaptive Maintenance—The human resources environment is always changing and evolving. For
example, new government regulations affecting HR practices, such as legislation addressing
racial and gender discrimination, can prompt new requirements or alter the old requirements of
the system.
Perfective Maintenance—The goal of perfective maintenance is to tweak or improve on the
existing system. For example, a more efficient routine that speeds up processing times could be
developed in the maintenance phase.
Preventative Maintenance—Preventative maintenance focuses on the ongoing requirements of
maintaining the hardware and software than runs the HRIS. Such a maintenance action will
prevent future system crashes due to inadequate hardware.