Ch 3 - Lec slides J, Flashcards
What are the considerations when planing a new HRIS system (project life cycle)?
Stakeholders Levels of information Architecture Roles in implementation Key activities in implementation Potential pitfalls
Who are potential users/stakeholders
Leaders & Managers Analysts and technicians Clerical employees Organizational employees Job seekers Eternal partner organizations
what types of interactions will managers have with the system?
support for timely and accurate decision making.
Performance management, hiring, promoting, salary, training & development.
what types of interactions will Analysts and Technicians have with the system?
Maintenance and updates
Pull detailed reports to evaluate potential strategic opportunities
what types of interactions will Clerical employees have with the system?
Data entry, reporting, managing transactions, and error checking
what types of interactions will organizational employees have with the system?
Self service applications ie. payroll, benefits, training
Pulling reports
System portal for other uses
what types of interactions will job seekers have with the system?
Online recruitment
Job applications
(consider ease of use of system for this user group who have no training on the system)
what types of interactions will external partner organizations have with the system?
They will rely on information coming from the system.
Eg of partners are banks, benefit provider, external recruitment, government agencies.
What are the categories of information to be inputted to the system?
Personal - details and KSAs
Organizational - Job descriptions, structure, compensation
Combination - individual job histories, performance reviews,
What are some details that need consideration for how the information will be stored?
Data security Data duplication Number of users accessing simultaneously Require off-site access Can the system be hosted on-site
What are the types of architecture that can be used for the system?
Two-tier Three-tier N-tier Cloud computing Best of breed
Two-tier architecture (def)
Connection between PC and Database Management Server where data is stored on the server and the PC runs day-to-day logic and applications.
The desktop didn’t do any of the work. Good security features, but large volume of processing.
Three-tier architecture (def)
Addition of an application server (middleware) to the two-tier system.
Allows for multiple simulations data transactions.
Can place high demands on network communications (bandwidth).
Application software still needed on every PC client.
N-tier architecture (def)
Client servers connect to a web server that is connected to application servers, and then the DBMS.
Able to add ERP to HRIS.
Allows for many types of user clients incl. thin clients.
Can add servers for specific functions ie. Web, print, encryption.
Can be geographically dispersed for load balancing and world wide access.
Reduces bandwidth demand.
Less privacy, and increased security risk.
Cloud Computing
X
