1 SPML V2 / HRXML Integration Use Cases

1

2 3 4 5 SPML V2 & HRXML Integration Use Cases 6 Draft Use Cases 0.1 7 11 January 2005 8 9 10 11 12Editor: 13 Darran Rolls, Sun Microsystems ([email protected]) 14 15Contributors: 16 Paul Kiel, HRXML 17 Romuald Restout, Lotus Interworks 18 Matt Tobiasen, Sterling Testing Systems 19 20Abstract: 21 This document describes the application and system level use case that will be modeled 22 using SPML V2 23 24Status: 25 Draft 26 27Copyright (C) OASIS Open 2004. All Rights Reserved. 28Copyright 2004 HR-XML Consortium

2 1 3 SPML V2 / HRXML Integration Use Cases

29 30 31SPML V2 & HRXML Integration Use Cases

32Revision History

33 Version Draft 01 – v01 (Working Group Review) Date 7th March 2005 Editor Darran Rolls, Sun Microsystems Contributors Matt Tobiasen, Sterling Testing Systems Paul Kiel, HRXML Romuald Restout, Lotus Interworks Comments Initial Draft

34

4 2 5 SPML V2 / HRXML Integration Use Cases

35 36 Revision History...... 1 37Introduction to the Use Cases...... 3 38HRXML Actors...... 3 39Use Case 1: New Applicant Screening Life-cycle...... 3 40 Description...... 3 41 Actors...... 3 42 Pre-Conditions...... 4 43 Steps...... 4 44 Post-Conditions...... 4 45Use Case 2: ATS Update Applicant Data...... 4 46 Description...... 4 47 Actors...... 4 48 Pre-Conditions...... 4 49 Steps...... 4 50 Post-Conditions...... 4 51Use Case 3: TA Update Applicant Data...... 4 52 Description...... 4 53 Actors...... 5 54 Pre-Conditions...... 5 55 Steps...... 5 56 Post-Conditions...... 5 57Use Case 4: ATS Deletes Applicant Data...... 5 58 Description...... 5 59 Actors...... 5 60 Pre-Conditions...... 5 61 Steps...... 5 62 Post-Conditions...... 5 63

6 3 7 SPML V2 / HRXML Integration Use Cases

64Introduction to the Use Cases 65 66The following use cases have been compiled by the joined HRXML & PSTC teams to 67represent an outline of the service level requirements for the integration of SPML V2 68with a sub section of the HR-XML schema. 69 70These integration use case, are taken from a sub-set of the HR-XML domain that 71covers user and systems provisioning between an Applicant Tracking Systems 72(ATS) and Screening Systems (SS) 73 74 75HRXML Actors 76 77For the purposes of these use cases, the following generic HRXML actors are defined 78and subsequently used throughout the use cases. 79 80Hiring Organization (HO) – A company or system that uses an Applicant 81Tracking System (ATS) to manage the process of finding, tracking and managing 82applications for a HR “new hire” 83 84Tracked Applicant (TA) – The person who applies to the hiring organization 85and is subsequently tracked as a record or activity within the Applicant Tracking 86Systems. 87 88Application Tracking System (ATS) – The manual/automated system and 89human services that forms a system for the tracking and processing of applicants for 90the HO and direct interaction with the TA. 91 92Screening Systems (SS) - The manual/automated system and human 93services that forms a system for screening the TA and reporting its findings to the 94Screening System 95 96 97 98Use Case 1: New Applicant Screening Life-cycle

99Description 100In this use case the ATS requests the creation of a new TA within a given SS. The 101SS then processes the request and responds back to the ATS with the results. 102 103NOTE: this looks like a basic application level protocol exchange between the system 104entities. This might now be what is required. Should this be just the TA record 105creation and the “application level” exchange is out of scope?

106Actors 107This use case uses the flowing actors: 108  HO 109  TA 110  ATS 111  SS

8 4 9 SPML V2 / HRXML Integration Use Cases

112Pre-Conditions 113  HO has created a TA record within the ATS (through unspecified integration 114 means) 115  ATS has pre existing trust relationship with SS

116Steps 117 1. 118 2. ATS sends an asynchronous createRequest to SS for creation of a new TA 119 record and provides required attributes for that service interface 120 3. SS sends back an acknowledgement of receiving the request and a 121 “requestID” for future queries 122 4. ATS sends a statusCheck request for ID to SS to see if screening process is 123 complete 124 5. SS sends back a statusResponse saying “in progress” 125 6. SS sends ATS a asyncResponse with notification of completion of screening 126 process

127Post-Conditions 128  TA record created within SS and screening process is completed. 129 130 131Use Case 2: ATS Update Applicant Data

132Description 133Here the ATS request update for a TA record that has previously been created using 134the proposed exchange.

135Actors 136This use case uses the flowing actors: 137  ATS 138  SS 139

140Pre-Conditions 141  Exist

142Steps 143 1. Happens 144 7.

145Post-Conditions 146  Happened 147 148 149

10 5 11 SPML V2 / HRXML Integration Use Cases

150Use Case 3: TA Update Applicant Data

151Description 152Here the TA request update for their own record, created by the ATS exchange with 153the SS.

154Actors 155This use case uses the flowing actors: 156  TA 157  SS 158

159Pre-Conditions 160  Exist

161Steps 162 1. Happens 163 8.

164Post-Conditions 165  Happened 166 167 168Use Case 4: ATS Deletes Applicant Data

169Description 170Here the ATS request deletion of a TA record that has previously been created using 171the proposed exchange.

172Actors 173This use case uses the flowing actors: 174  ATS 175  SS 176

177Pre-Conditions 178  Exist

179Steps 180 2. Happens 181 9.

182Post-Conditions 183  Happened 184

12 6