Case Study HR
Case Study: Larson Property Management has depended on a legacy HRIS to manage its applicant and employee databases. The system runs on a client-server computer system. The system was implemented approximately 10 years ago, prior to the company's rapid growth and when it employed fewer than 100 employees. The system's functionality is limited to the storage and retrieval of employee and applicant data. For recruiting purposes, the system requires a clerk to manually enter basic applicant data, the results of the application test, and whether an offer of employment has been made. Prior to this, applicants' files were passed around to those who reviewed the materials and were sometimes misplaced, so trying to locate a particular applicant's file was often a problem. The current HRIS has limited file storage capability for applicant and employee records and currently has reached its storage capacity. Larson Property Management has decided to replace its legacy HRIS. One application module in the new HRIS that the company wants is a sophisticated applicant-tracking system (ATS). The primary objective of the ATS will be to provide a paperless hiring process. The basic functions of the new system will be managing the requisition and approval of job openings, storing resumes and job applications and retrieving through query functions the names of applicants who match job requirements, tracking a candidate's progress through the recruiting and selection process, and providing automated reporting functions. The company's managers also want an eHRM functionality that includes the Internet posting of job openings through the company's website and external job-posting services, application and resume submission through the Web and through kiosks at various office locations, staff ability to access and use the system remotely through a Web browser, and online resume- and application-scanning capabilities. Questions: 1. Who are the important stakeholders to be considered in the design of the ATS? 2. List all the "entities" associated with the ATS in a Data Flow Diagram. You are NOT required to create a Data Flow Diagram (DFD). 3. List at least 3 "processes" associated with the ATS in a Data Flow Diagram. You are NOT required to create a Data Flow Diagram (DFD). 4. Identify at least 2 "data stores" associated with the ATS in a Data Flow Diagram. You are NOT required to create a Data Flow Diagram (DFD) Type your answers to the 4 questions in the box provided below. Please indicate the Question numbers (1, 2, 3 and 4) when typing your answers. For the toolbar, press ALT+F10 (PC) or ALT+FN+F10 (Mac). B I U S Paragraph Arial 10pt X2 X 2 8 8 ST The
