Copywrite C 1999 PMi www.pmihrm.com Chapter 5 Designing and Developing a New HRMS.

Slides:



Advertisements
Similar presentations
Copywrite C 1999 PMi RETURN ON INVESTMENT Chapter 3.
Advertisements

System Development Life Cycle (SDLC)
NATIONAL TREASURY TECHNICAL ASSISTANCE UNIT (TAU) Enabling Change for Development Programme and Project Management (PPM) Update Project Management Interest.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Acquiring Information Systems and Applications
CHAPTER 10 & 13 IS within the Organization & Acquiring IS and Applications.
Planning a measurement program What is a metrics plan? A metrics plan must describe the who, what, where, when, how, and why of metrics. It begins with.
Copywrite C 1999 PMi HUMAN RESOURCES MANAGEMENT SYSTEMS Benefits and Pension Programs Chapter 12.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 3: System design. System design Creating system components Three primary components – designing data structure and content – create software –
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Fundamentals of Information Systems, Second Edition
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 18-1 Accounting Information Systems 9 th Edition Marshall.
© Pearson Education Limited, Chapter 6 Fact-finding Transparencies.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
Lecture Nine Database Planning, Design, and Administration
Copywrite C 1999 PMi HUMAN RESOURCES MANAGEMENT SYSTEMS Compensation and Payroll Chapter 10.
Copywrite C 1999 PMi HUMAN RESOURCES MANAGEMENT SYSTEMS Staffing Chapter 9.
Chapter 24 - Quality Management
Acquiring Information Systems and Applications
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Internal Auditing and Outsourcing
Hartley, Project Management: Integrating Strategy, Operations and Change, 3e Tilde Publishing Chapter 11 Procurement Management Embedding value into the.
1.Database plan 2.Information systems plan 3.Technology plan 4.Business strategy plan 5.Enterprise analysis Which of the following serves as a road map.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Managing the development and purchase of information systems (Part 1)
Verification: Quality Assurance in Assessment Verification is the main quality assurance process associated with assessment systems and practice - whether.
Chapter 14 Information System Development
Software Engineering Lecture # 17
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Acquiring Information Systems and Applications
1 The Software Development Process  Systems analysis  Systems design  Implementation  Testing  Documentation  Evaluation  Maintenance.
1 Unit 1 Information for management. 2 Introduction Decision-making is the primary role of the management function. The manager’s decision will depend.
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
Acquiring Information Systems and Applications
CHAPTER 13 Acquiring Information Systems and Applications.
Programme Objectives Analyze the main components of a competency-based qualification system (e.g., Singapore Workforce Skills) Analyze the process and.
Screening and Selecting Software. HRIS Project Phases NeedsAnalysis Design & Development Implementation & Maintenance.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Introduction Procurement of Consultant Services (based on PPA 2004 and Best Practices) Presented by: NM Lema Macrh, 2013.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
The Software Development Process
Systems Development Life Cycle
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Chapter 11: Alternative Approach - Purchasing Systems.
Learning More About Oregon’s ESEA Waiver Plan January 23, 2013.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
P5: Advanced Performance Management. Section A: Strategic Planning and Control A1. Introduction to strategic management accounting A2. Performance management.
Software Engineering — Software Life Cycle Processes — Maintenance
Stages of Research and Development
Appendix 2 Automated Tools for Systems Development
Software Quality Control and Quality Assurance: Introduction
Modern Systems Analysis and Design Third Edition
BANKING INFORMATION SYSTEMS
System Design Ashima Wadhwa.
Modern Systems Analysis and Design Third Edition
Business System Development
IS442 Information Systems Engineering
Chapter 4 Automated Tools for Systems Development
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
The ultimate in data organization
AICT5 – eProject Project Planning for ICT
Software Testing Lifecycle Practice
Modern Systems Analysis and Design Third Edition
Presentation transcript:

Copywrite C 1999 PMi Chapter 5 Designing and Developing a New HRMS

Copywrite C 1999 PMi Human Resources Management Systems: A Practical Approach n By Glenn M. Rampton, Ian J. Turnbull, J. Allen Doran ISBN X Carswell

Copywrite C 1999 PMi Introduction n The design of any HRMS software system requires both functional and technical decisions n These decisions should be predicated on the uses to which the system will be put

Copywrite C 1999 PMi Security n System security addresses concerns re: system control and privacy n System control addressed through audit trails n In provincial and federal jurisdictions privacy is a legislated right of persons whose personal data resides on an HRMS

Copywrite C 1999 PMi Analysis of Business Process n To often systems are developed based on existing requirements n Automation of inefficient or unnecessary work flows may simply produce the wrong result more quickly

Copywrite C 1999 PMi Business Process Reengineering Reengineering the Corporation, Hammer and Champy (1993) in their book Reengineering the Corporation, have argued that American corporations had to radically change the way they did business, or go out of business.

Copywrite C 1999 PMi Phases in Process Reengineering n Analysis Phase – identify what tasks are being done – determine why those tasks are being done – analyze how they are being done – identify who is doing them n Problem-Solving Phase – determine what should be done and why it should – determine how tasks should be done – determine who should do the tasks, along with where and when they should be done

Copywrite C 1999 PMi Conducting Reengineering n develop a strategy, scope, and for the re-engineering plan; n ensure that management at all levels are convinced of the value of project, and are committed to supporting it; n chart process flows, and analyse current high or low level tasks; n consider what supporting application software you will require; n conduct Value for Money Audits to ensure that you can justify your project in dollars and cents terms (see Chapter 3);

Copywrite C 1999 PMi Conducting Reengineering (cont’d) n develop benchmarks for the projects to be used as standards to be met (or exceeded) by the project; n develop new effective and efficient tasks and processes; n prepare an implementation plan (see Chapter 6); n implement the plan; and, n develop a plan for maintaining the system.

Copywrite C 1999 PMi Once one has decided that the human resources processes in the organization are the “right ones to automate” one can then turn one’s attention to designing the HRMS to automate the processes in the “right way”.

Copywrite C 1999 PMi Steps in Designing a New HRMS n design a database with the capacity to handle the relevant populations. n label each field and each data element to create a complete data dictionary. n create tables of values which can be drawn on by data fields as appropriate. n establish data relationships, including all algorithms and routines, to optimize editing and validation of fields. n create menus and screens to assist users in navigating through the HRMS.

Copywrite C 1999 PMi Steps in Designing a New HRMS (Con’t) n create operator messages that specify action options. n build in error-checking routines. n build in data security, including audit trails. n define standard reports. n include a tutorial module to assist new users.

Copywrite C 1999 PMi Benchmarking

Copywrite C 1999 PMi Measurement

Copywrite C 1999 PMi Performance Measurement Principles The productivity and effectiveness of any function can be measured by some combination of cost, time, quantity, or quality indices: n A measurement system promotes productivity by focusing attention on the important issues, tasks, and objectives. n Professional and knowledge workers are best measured as a group. n Managers can be measured by the efficiency and effectiveness of the units they manage. n The ultimate measurement is not efficiency, but effectiveness.

Copywrite C 1999 PMi Build or Buy? Not a simple question, but: Organizations must understand that the strategic advantage of good information systems comes, not from building some unique tool, but by ensuring that the tool has all the capabilities that the organization requires, and by using these capabilities well.

Copywrite C 1999 PMi Screening and Selecting Software The traditional approach to software includes: n definition of user requirements. n development of a request for information (RFI) or request for proposal (RFP), which is then sent to appropriate software suppliers. n assessment of supplier responses, screening out systems or suppliers which do not match sufficient criteria. n demonstrations of short-listed products to see the "look and feel" and to confirm that stated capability does exist. n assessment of vendor and software reliability.

Copywrite C 1999 PMi Definition of Requirements Requirements are generally defined in three ways: functional, system operations, and technical.

Copywrite C 1999 PMi Attributes of User-Friendly Systems n easy to establish contact with software (sign-on process; security) n uses icons, menus, or both to guide user choices (no need to use code or learn mnemonics) n software easy to learn and use (windows, scrolling, and other features) n users are guided through various processes; help to correct mistakes is easily available; n all error messages are fully explanatory n the data dictionary is available on ‑ line n software has edit checks to verify syntax, semantics, and overall data integrity (e.g., n down loads/uploads to/from PC products such as word processors, spreadsheets n effective use of graphics.

Copywrite C 1999 PMi Screening and Selecting Software (cont’d) n Development of an RFI/RFP n Assessment of Vendor Responses n Demonstrations n Supplier and Product Reliability

Copywrite C 1999 PMi Development of an RFI/RFP

Copywrite C 1999 PMi RFI/RFP (cont’d) Developing an RFI/RFP is a complex task. The RFI/RFP should be designed in a way which will facilitate comparative analysis of several software supplier's responses. Open ended questions invite open-ended answers which are very hard to compare. As much as possible, questions should be specific. One method of achieving this is to offer multiple choice responses followed by a "comments" section for the software supplier to elaborate as required, thus providing both comparative data and allowing for the explanation of variances

Copywrite C 1999 PMi Assessment of Vendor Responses With a well designed RFI/RFP, the analysis of results should be easy, although often detailed and time- consuming. The purpose of the analysis is to weed out systems or suppliers which are unsuitable, leaving only the best options for further review.

Copywrite C 1999 PMi Demonstrations Potential suppliers should be asked to provide demonstrations of their products. Demonstrations of a software product can be as short as one hour, or as long as a week or more. Many software selection processes include at least two phases; a short (one to three hours), general initial demonstration, followed by a more detailed and focused demonstration.

Copywrite C 1999 PMi Supplier and Product Reliability Buying a software package, particularly an HRMS, should mean that you are buying not just the current software version, but future versions as well. This investment in a product and its supplier can be a marriage of five, ten, or even more years. It should only be made if the buyer is sure that the supplier and the product are reliable, i.e., that both are a good investment.

Copywrite C 1999 PMi Question 1 Suppose you were given the responsibility for designing and developing a new HRMS in a financial institution with 15,000. employees headquartered in Winnipeg, Manitoba, but with branches across Canada. What are some of the global (high level) design issues which you feel should be considered? Are there some issues which you believe should take precedence over others? Discuss.

Copywrite C 1999 PMi Question 2 List three methods by which an organization can verify vendor claims about an HRMS product. Which are most important, and why?

Copywrite C 1999 PMi Question 3 Why is it important to examine what human resources business processes one in automating when one sets out to design and develop a new HRMS? Given that the “powers that be” agree to conduct a business process re-engineering (or engineering, if prefers) study of the organization’s Human Resources Function, who do you think should be involved in such a study. Who should lead it? Should it contain representatives from outside of Human Resources. What should be the role of Management Information Specialists?