Complete Report by Package - Full Details

Tuesday, February 19, 2008, 3:16:40 PM

1. iHRIS Manage - Core Functional
Actors:
A-PT1 HR Manager
A-PT2 HR Staff
A-PT3 Executive Manager
A-PT4 Employee
A-PT5 Supervisor
A-PT6 Manager
A-PT7 Applicant
A-PT8 Training Manager
A-PT9 Any User

1.1. Data Administration
Use Cases:
UC-PT1 Add or update a facility type
UC-PT2 Add or update an office or facility
UC-PT3 Add or update a department
UC-PT4 Add or update an education type
UC-PT5 Add or update a degree
UC-PT6 Add or update a language
UC-PT7 Add or update an identification type
UC-PT8 Add or update a benefit type
UC-PT9 Add or update a marital status
UC-PT10 Add or update a reason for departure
UC-PT11 Add or update a country
UC-PT12 Add or update a region
UC-PT13 Add or update a district
UC-PT14 Add or update a county
UC-PT15 Add or update a currency

1.2. Position Management
Use Cases:
UC-PT16 Add or update a cadre
UC-PT17 Add or update a job classification
UC-PT18 Create a salary grade
UC-PT19 Create a job
UC-PT20 Add or update a salary source
UC-PT21 Add or update a position type
UC-PT22 Create a position
UC-PT23 Update a position
UC-PT24 Discontinue a position
UC-PT25 Create an organizational chart

1.3. Employee Management
Use Cases:
UC-PT26 Enter a new record
UC-PT27 Set a position for an employee
UC-PT28 Add identification information
UC-PT29 Add demographic information
UC-PT30 Add contact information
UC-PT31 Record a special payment
UC-PT32 Terminate an employee
UC-PT33 Record a position change
UC-PT34 Record a salary change
UC-PT35 Add language proficiencies
UC-PT38 Record notes
UC-PT36 Upate a record
UC-PT37 Correct data

1.4. Job Applicant Management
Use Cases:
UC-PT39 Apply for a position
UC-PT40 Log interview details
UC-PT41 Log a hiring decision
UC-PT42 Enter employment history
UC-PT43 Enter educational history
UC-PT44 Review applicants
UC-PT45 Make a job offer

1.5. Search
Use Cases:
UC-PT46 Search for a record
UC-PT47 View a record

1.6. Competency Model
Use Cases:
UC-PT48 Create a competency model
UC-PT49 Assess an employee's competencies
UC-PT50 Search for employee qualifications
UC-PT51 Create an organizational competency inventory

1.7. Training Management
Use Cases:
UC-PT52 Add or update a training funder
UC-PT53 Add or update a training organization
UC-PT54 Add or update a training program category
UC-PT55 Add or update an in-service training program
UC-PT56 Enter the schedule for a training program
UC-PT57 List training programs
UC-PT58 Schedule a training for an employee
UC-PT59 Assess training results and update competencies
UC-PT60 Report on employees trained

1.8. ScholarshipManagement
Use Cases:
UC-PT61 Add or update a scholarship
UC-PT62 Award a scholarship to an employee
UC-PT63 Track employee fulfillment of scholarship requirements

1.9. Dual Data Entry
Use Cases:
UC-PT64 Check data entry errors
UC-PT65 Check data quality
UC-PT66 Process an unverified record
UC-PT67 Spot-check records

1.10. Requirements
Requirements:
REQ-PT1 Integration with Active Directory
REQ-PT2 Pension plan management
REQ-PT3 Employee scheduling
REQ-PT4 Performance review module
REQ-PT5 Workplace safety data
REQ-PT6 Payroll management
REQ-PT7 New employee orientation
REQ-PT8 Document management module
REQ-PT9 Resource planning and approval module
REQ-PT10 Localization
REQ-PT11 Job applicant questions
REQ-PT12 Privacy
REQ-PT13 Track leave
REQ-PT14 Benefits tracking
REQ-PT15 Geographical locations
REQ-PT16 Customization

2. iHRIS Common
Actors:
A-ICE1 System Administrator
A-ICE2 Any User
A-ICE3 Data Analyst

2.1. System-wide
Use Cases:
UC-ICE4 Configure modules
UC-ICE9 Save a record

2.2. User Administration
Use Cases:
UC-ICE1 Add a user account
UC-ICE2 Update a user account

2.3. User Access
Use Cases:
UC-ICE6 Log in
UC-ICE8 Retrieve a password or username
UC-ICE3 Change password
UC-ICE5 Give feedback
UC-ICE7 Log out

2.4. Reporting
Use Cases:
UC-ICE12 Run a preconfigured report
UC-ICE11 Customize a report
UC-ICE13 Save a report
UC-ICE10 Access a saved report

2.5. Offline Tool
Use Cases:
UC-ICE14 Install the offline tool
UC-ICE15 Import data
UC-ICE16 Export data

2.6. Requirements
Requirements:
REQ-ICE1 Cadres
REQ-ICE2 Technology requirements
REQ-ICE3 Multilingual support
REQ-ICE4 Log usage
REQ-ICE5 Leveragability
REQ-ICE6 Integratability
REQ-ICE7 Idle logout
REQ-ICE8 GIS mapping
REQ-ICE9 Extensibility
REQ-ICE10 Data reliability
REQ-ICE11 Compatibility
REQ-ICE12 Caching of report data
REQ-ICE13 Authorization
REQ-ICE14 Auditing
REQ-ICE15 Archival
REQ-ICE16 Authentication
REQ-ICE17 Data import

1. iHRIS Manage - Core Functional

iHRIS Manage - Core Functional

 File: PowerTrack.ucd
Description
iHRIS Manage is a human resources management tool that enables an organization to design and manage a comprehensive human resources strategy.
Related Documents and URLs
https://launchpad.net/ihris-manage
http://www.capacityproject.org/hris/suite/ihris_manage.php
Notes Date Added
This documentation refers to the core version of the HR Management database (working title: PowerTrack). 9/13/2006
The specifications were based on the requirements gathered for the Rwanda release Version 1.0. It also includes some specifications gathered for release to IntraHealth HR department. 9/13/2006
An earlier version of the system was released in Rwanda as RW-MOH 0.9a 9/13/2006
Core Version 2.0 released April 16, 2007, and included all core functionality in these use cases. 5/7/2007

iHRIS Manage - Core Functional actors:

A-PT1

HR Manager

Parent: iHRIS Manage - Core Functional
Description
This person is a manager of HR personnel and is responsible for ensuring that data in the system are complete, correct and up to date. This person will also run reports and analyze data in order to make organizational or individual HR decisions. This person has permission to view any record in the system.
Goals
Create standard lists of data for selection in the system.
Add offices and facilities to the organizational structure.
Create a job structure for the organization.
Check for and correct data errors.
Report on data quality.
Notes Date Added
Can perform any use case that HR Staff, Training Manager or Executive Manager can perform. 9/19/2006
Logs in with their own account (not tied to employee record). 1/12/2007


A-PT2

HR Staff

Parent: iHRIS Manage - Core Functional
Description
This person is responsible for entering and updating data in the system. This person can update and view any record in the system.
Goals
Create and update positions.
Enter application information for a job applicant.
Review applicants and make a job offer to an applicant.
Add a new record.
Enter information into or update information in an employee's record.
Record position and salary changes in an employee's record.
Generate position lists, organizational charts, staff lists and staff directories.
Notes Date Added
Can perform any use case that a Training Manager, Applicant, Employee or Supervisor can perform. 9/19/2006
Logs in with their own account, not tied to an employee record. 1/12/2007


A-PT3

Executive Manager

Parent: iHRIS Manage - Core Functional
Description
This person will run reports and analyze data in order to make organizational HR decisions.
Goals
Search for and view employee records.
Generate reports to analyze data entered in the system.
Assess organizational competencies held by all employees and search for employee qualifications.
Review applicants for a position.
Notes Date Added
Logs in with their own account (not tied to employee record). 1/12/2007
This person has permission to view any record in the system but cannot update or change data in an employee record. 10/31/2007


A-PT4

Employee

Parent: iHRIS Manage - Core Functional
Description
A person who works for an organization. This person performs actions related to his/her own record in the system.
Goals
Apply for an open position.
Update or add to personal, contact, identification, educational and employment information in his/her own record.
Request a training program.
Notes Date Added
Logs in as guest, then authenticates against password stored with their employee record (proposed). 1/12/2007
This role can only view and interact with his/her own record. This role can update demographic and contact information, and view the rest of the record. 5/7/2007
This role has not yet been implemented; new use cases may need to be written for this role. 10/2/2007
This role can complete any use case that an Applicant can. 11/5/2007
The Employee can only add to the employment or educational history and add news skills and languages as part of filling out a job application; otherwise, these areas are for viewing only. 2/7/2008
Identification numbers should be obscured to the Employee. 2/7/2008
Employee access is also referred to as "self service." 2/7/2008
The Employee is considered to have left employment when a position change is recorded but no new position is set; the Employee then becomes an Old Employee and can only access the system as an Applicant. 2/7/2008


A-PT5

Supervisor

Parent: iHRIS Manage - Core Functional
Description
An employee of the organization who supervises other employees. This person can view and update records for any employees under his/her supervision.
Goals
Search for and view records for supervised employees.
View reports of data related to supervised employees.
Request a training program for an employee.
Review applicants for supervised positions.
Notes Date Added
Logs in with the guest account and then authenticates against the password stored with their employee record. 1/12/2007
Role is determined by whether the person's position is a supervisor of other employees. 1/12/2007
This role can only view or interact with records of employees that are in a reporting line underneath the Supervisor. 5/7/2007
The Supervisor cannot update or change any data in an Employee's record. 2/7/2008
Identification numbers should be obscured or hidden from the Supervisor. 2/7/2008
Access to types of reports may be limited. Viewing reports is a lower priority for development. 2/7/2008
This role has not yet been implemented; new use cases may need to be written for this role. 10/2/2007
This role will be important for any performance management module to be development and may play a role in assessing employee competencies. 2/7/2008


A-PT6

Manager

Parent: iHRIS Manage - Core Functional
Description
This person will run reports and analyze data in order to make HR decisions regarding a particular department, facility, office or other specific location within the organization. This person can only view records associated with the organizational division that s/he manages.
Goals
Search for and view records for employees of the department, office or facility.
View reports of data related to employees of the department, office or facility.
Review applicants for open positions in the department, office or facility.
Notes Date Added
Logs in with a guest account and then authenticates against the password stored with their employee record. 1/12/2007
Role is determined by whether the position the manager of a facility or department. 1/12/2007
This role can only view records of employees at the same facility or department. This role cannot change or update employee data. 5/7/2007
The Manager may also be a Supervisor. 2/7/2008
This role is a scaled-down version of the Executive Manager role. 2/7/2008
This role has not yet been implemented; new use cases may need to be written for this role. 10/2/2007
Development of the Manager role is lower priority and has been tabled. 2/7/2008


A-PT7

Applicant

Parent: iHRIS Manage - Core Functional
Description
This is a job applicant who has not yet been hired by the organization. This person does not have permission to view any records in the system.
Goals
Apply for an open position.
Notes Date Added
Logs in with a guest account using a generic username and password, then sets up their own account. Also referred to as "Guest." 1/12/2007
This role can only complete or update the job application once logged in. This includes answering the application questions, adding educational history, employment history, languages and skills, and entering basic personal and contact information. 5/7/2007
Former employees are treated as Applicants when they log in. 5/7/2007
Applicants are converted to Employees when they are assigned a position. 2/7/2008
This role has not been implemented. 11/5/2007


A-PT8

Training Manager

Parent: iHRIS Manage - Core Functional
Description
This person is responsible for managing training programs taken by employees and updating employee competencies.
Goals
Create a competency model for the organization.
Assess an employee's competencies.
Search for employees who hold particular competencies.
Add training information and manage the list of available training programs.
Schedule trainings for employees.
Assess an employee's training results and update the employee's training history.
Report on employees who have received trainings.
Notes Date Added
This is a new actor who is focused on the training module functions. HR Staff may complete any use case that the HR Training Manager can. 11/15/2007


A-PT9

Any User

Parent: iHRIS Manage - Core Functional
Description
A generic user (applies to all users of the system).
Goals
Search for and view a record.

1.1. Data Administration

Data Administration

Description
Create and update standard lists of data for selection in system menus.
Notes Date Added
Access is limited to HR Managers and System Administrators. 5/7/2007
Locate these functions via the Configure System --> Administer Database link on the main menu. 9/28/2007

Data Administration use cases:

UC-PT1

Add or update a facility type

 P1
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager adds a new facility type for selection in the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The facility type is added to the system and is available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage the list of facility types.
  2. The system displays all facility types entered in the system.
  3. The user adds a new facility type.
  4. The user enters a description or name for the facility type.
  5. The user saves teh record (UC-ICE9).
  6. The system makes the facility type available for selection when adding facilities.

Extensions:

3.a The user selects an existing facility type.
  1. The system opens the facility type for editing.
5.a The system determines that the facility type already exists in the database.
  1. The system displays an error and will not continue.
Notes Date Added
This use case is identical for iHRIS Manage and Qualify. 10/31/2007


UC-PT2

Add or update an office or facility

 P2
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager adds a new office or facility for selection within the system and ties it to an institution type.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The office/facility is saved to the system and is available for selection within various use cases and for reporting.
Level: User Complexity: Low
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage the list of offices/facilities.
  2. The system displays all offices/facilities entered in the system.
  3. The user adds a new office/facility.
  4. The user enters the name (description) of the office/facility.
  5. The user selects the facility type for the office/facility.
  6. The user adds the facility's contact information (UC-PT30).
  7. The user selects the country where the office/facility is located.
  8. The system displays all districts in that country.
  9. The user selects the district where the office/facility is located.
  10. The system displays all counties in that district.
  11. The user selects the county where the office/facility is located (optional).
  12. The user saves the record (UC-ICE9).
  13. The system displays the office or facility's record.
  14. The system provides the option to update the office or facility information.
  15. The system makes the office or facility available for selection and reporting.

Extensions:

3.a The user selects an existing office or facility.
  1. The system opens the item for editing.
5.a The user adds a new facility type (UC-PT1).
  1. The user returns to Step 1 to add the office/facility.
7.a The user adds a new country (UC-PT11).
  1. The user returns to Step 1 to add the office/facility.
8.a The user adds a new district (UC-PT13).
  1. The user returns to Step 1 to add the office/facility.
10.a The user adds a new county (UC-PT14).
  1. The user returns to Step 1 to add the office/facility.
12.a The system determines that the office/facility name already exists in the database.
  1. The system displays an error and will not continue.
Open Issues AssignedTo ResolveBy
Should the Manager of the office/facility be set in this use case? 151719 n/a


UC-PT3

Add or update a department

 P2
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager adds a new department to the list of departments available for selection in the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The department is saved and is available for selection within various use cases and for reporting.
Level: User Complexity: Low
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to update the list of departments.
  2. The system displays all departments previously entered into the system.
  3. The user adds a new department.
  4. The user enters the name of the department.
  5. The user saves the record (UC-ICE9).
  6. The system makes the department available for selection when adding positions.

Extensions:

3.a The user selects an existing department.
  1. The system opens the department for editing.
5.a The system determines that the department already exists in the databse.
  1. The system displays an error and will not continue.
Open Issues AssignedTo ResolveBy
Should the Manager of the department be set in this use case? 151719 n/a


UC-PT4

Add or update an education type

 P2
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager updates a list of education types that are available for selection within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new education type is saved and available for selection when adding a degree.
Level: User Complexity: Low
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage the list of education types.
  2. The system displays all education types entered in the system..
  3. The user adds a new education type.
  4. The user enters the description or name of the education type.
  5. The user saves the record. (UC-ICE9)
  6. The system makes the education type available for selection when adding educational information.

Extensions:

3.a The user selects an existing education type.
  1. The system opens the education type for editing.
5.a The system determines that the education type already exists in the database.
  1. The system displays an error and will not continue.


UC-PT5

Add or update a degree

 P2
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager adds a type of educational institution to the system and associates it with degrees that it issues.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
A new degree is associated with its education type and made available for selection from various use cases.
Level: User Complexity: Low
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage the list of degrees.
  2. The system displays all education types entered in the system.
  3. The user selects an education type.
  4. The system displays a list of matching degrees for that education type.
  5. The user adds a new degree.
  6. The user enters the name (description) of the degree.
  7. The user selects the education type for the degree.
  8. The user saves the record (UC-ICE9).
  9. The system makes the degree available for selection when adding educational information.

Extensions:

3.a The user does not select an education type.
  1. The system provides the option to add a new degree only.
  2. Skip to Step 6.
5.a The user selects an existing degree.
  1. The system opens the degree for editing.
7.a The user adds a new educational type.
  1. The user returns to Step 1 to add the degree.
7.b The user already selected the education type.
  1. The system fills in the selected education type when the degree is added.
8.a The system determines that the degree already exists in the database for the selected education type.
  1. The system displays an error message and will not continue.


UC-PT6

Add or update a language

 P1
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager updates a list of languages that are available for selection within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new language is saved and available for selection.
Level: User Complexity: Low
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage languages.
  2. The system displays all languages entered in the system.
  3. The user adds a new language.
  4. The user enters the description or name of the item.
  5. The user saves the record (UC-ICE9).
  6. The system makes the language available for selection when adding language proficiency.

Extensions:

3.a The user selects an existing language.
  1. The system opens the language for editing.
5.a The system determines that the language already exists in the database.
  1. The system displays an error and will not continue.


UC-PT7

Add or update an identification type

 P1
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager updates a list of identification types that are available for selection within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new identification type is saved and available for selection when adding an identification.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage the list of identification types.
  2. The system displays all identification types entered in the system.
  3. The user adds a new identification type.
  4. The user enters the description or name of the item.
  5. The user saves the record (UC-ICE9).
  6. The system makes the identification type available for selection when adding identifications.

Extensions:

3.a The user selects an existing identification type.
  1. The system opens the identification type for editing.
5.a The system determines that the identification type already exists in the database.
  1. The system displays an error and will not continue.
Notes Date Added
This use case is identical for both iHRIS Manage and Qualify. 10/31/2007


UC-PT8

Add or update a benefit type

 P1
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager updates a list of benefit types that are available for selection within the system.
Preconditions:
The user must be logged in to the system		 Success Guarantee:
The new benefit type is saved and available for selection when adding a benefit.
Level: User Complexity: Low
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage benefit types.
  2. The system displays all benefit types entered in the system.
  3. The user adds a new benefit type.
  4. The user enters the description or name of the item.
  5. The user saves the record (UC-ICE9).
  6. The system makes the benefit type available for selection when adding benefits.

Extensions:

3.a The user selects an existing benefit type.
  1. The system opens the benefit type for editing.
5.a The system determines that the benefit type already exists in the database.
  1. The system displays an error and will not continue.


UC-PT9

Add or update a marital status

 P1
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager adds a new marital status to the system that is available in selection lists.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The marital status is added to the system and is available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage the list of marital statuses.
  2. The system displays all marital statuses entered in the system.
  3. The user adds a new marital status.
  4. The user enters a description for the marital status.
  5. The user saves the record (UC-ICE9).
  6. The system makes the marital status available for selection when adding demographic information.

Extensions:

3.a The user selects an existing marital status.
  1. The system opens the marital status for editing.
5.a The system determines that the marital status already exists in the database.
  1. The system displays an error and will not continue.
Notes Date Added
This use case is the same for both iHRIS Manage and Qualify. 10/31/2007


UC-PT10

Add or update a reason for departure

 P2
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager updates a list of reasons for departure that are available for selection within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new reason for departure is saved and available for selection.
Level: User Complexity: Low
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage the list reasons for departure.
  2. The system displays all reasons entered in the system.
  3. The user adds a new reason for departure.
  4. The user enters the description or name of the item.
  5. The user saves the record (UC-ICE9).
  6. The system makes the reason available for selection when recording position changes.

Extensions:

3.a The user selects an existing reason for departure.
  1. The system opens the item for editing.
5.a The system determines that the reason for departure already exists in the database.
  1. The system displays an error and will not continue.


UC-PT11

Add or update a country

 P1
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager updates the list of countries available for selection in the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new or changed country is defined within the system and available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage lists of countries.
  2. The system displays all countries entered in the system.
  3. The user adds a new country.
  4. The user enters the two-letter country code.
  5. The user enters the ISO numeric code for the country (optional).
  6. The user selects whether the country is the primary country for the system.
  7. The user saves the record (UC-ICE9).
  8. The system makes the country available for selection whenever adding geographical locations or nationalities/citizenships.

Extensions:

3.a The user selects an existing country.
  1. The system opens the country for editing.
6.a The user selects the country as the primary country.
  1. The system displays the country first in all country selection menus.
6.b The system determines that more than one country was selected as the primary country.
  1. The system displays all primary countries at the top of selection menus in alphabetical order.
7.a The system determines that the name and country code are the same as a country previously entered.
  1. The system displays an error message and will not continue.
Notes Date Added
This use case is the same for iHRIS Manage and iHRIS Qualify. 10/31/2007
Geographical locations are tied together from largest to smallest: country --> region --> district, state or province --> county or sector. 10/31/2007
The country list also displays nationalities for selection. 10/31/2007


UC-PT12

Add or update a region

 P9
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager updates the list of regions available for selection in the system and establishes the region's parent country.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new or changed region is defined within the system and available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage lists of regions.
  2. The system displays all countries entered in the system.
  3. The user selects the country where the region is located.
  4. The system displays all regions entered for that country.
  5. The user adds a new region.
  6. The user selects the name of the country inside which the new region is located.
  7. The user enters the name of the region.
  8. The user enters the code for the region (optional).
  9. The user saves the record (UC-ICE9).
  10. The system makes the region available for reporting.

Extensions:

2.a The user does not select a country.
  1. The system provides only the option to add a new region.
  2. Skip to Step 5.
5.a The user selects an existing region.
  1. The system opens the region for editing.
6.a The user adds a new country.
  1. The user returns to Step 1 to add the region.
6.b The system determines that the country was previously selected.
  1. The system fills in the selected country.
9.a The system determines that the name and parent country are the same as a location previously entered.
  1. The system displays an error message and will not continue.
Referenced Requirements Type ID
Geographical locations Business Rule REQ-PT15
Open Issues AssignedTo ResolveBy
Redesign needed: If a new parent location is added from a link on the new location's page, the Return button should go back to the original location being added. Not implemented. 153037 n/a
Notes Date Added
This use case is identical for iHRIS Manage and iHRIS Qualify. 10/31/2007


UC-PT13

Add or update a district

 P9
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager updates the list of districts available for selection in the system and establishes the district's parent region.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new or changed district is defined within the system and available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage lists of districts.
  2. The system displays all countries entered in the system.
  3. The user selects the country where the district is located.
  4. The system displays all regions entered for that country.
  5. The user selects the region where the district is located.
  6. The system displays all districts entered for that region.
  7. The user adds a new district.
  8. The user selects the name of the country and region inside which the new district is located.
  9. The user enters the name of the district.
  10. The user enters the code for the district.
  11. The user saves the record (UC-ICE9).
  12. The system makes the district available for selection when adding geographical locations.

Extensions:

3.a The user does not select a country.
  1. The system provides the option to add a new district only.
  2. Skip to Step 7.
7.a The user selects an existing district.
  1. The system opens the district for editing.
8.a The system determines that the user previously selected the country and region.
  1. The system fills in the selections for the district.
11.a The system determines that the name and parent region and country are the same as a location previously entered.
  1. The system displays an error message and will not continue.
Referenced Requirements Type ID
Geographical locations Business Rule REQ-PT15
Open Issues AssignedTo ResolveBy
Redesign needed: If a new parent location is added from a link on the new location's page, the Return button should go back to the original location being added. Not implemented. 153037 n/a
Notes Date Added
This use case is identical for iHRIS Manage and iHRIS Qualify. 10/31/2007


UC-PT14

Add or update a county

 P1
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager updates the list of counties available for selection in the system and establishes the county's parent district.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new or changed county is defined within the system and available for selection within various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to manage lists of counties.
  2. The system displays all countries entered in the system.
  3. The user selects the country where the county is located.
  4. The system displays a list of regions for that country.
  5. The user selects the region inside which the county is located.
  6. The system displays all districts entered for that region.
  7. The user selects the district where the county is located.
  8. The system displays all districts entered for that county.
  9. The user adds a new county.
  10. The user selects the country, region and district where the county is located.
  11. The user enters the name of the county.
  12. The user saves the record (UC-ICE9).
  13. The system makes the county available for selection whenever geographical locations are added.

Extensions:

2.a The user does not select a country.
  1. The system provides the option to add a new county only.
  2. Skip to Step 9.
9.a The user selects an existing county.
  1. The system opens the county for editing.
10.a The system determines that the country, region and district were previously selected.
  1. The system fills in the previous selections for the county.
12.a The system determines that the name and parent district are the same as a location previously entered.
  1. The system displays an error message and will not continue.
Notes Date Added
The use case is the same for iHRIS Manage and iHRIS Qualify. 10/31/2007


UC-PT15

Add or update a currency

 P2
Parent: Data Administration
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager adds a currency for selection when setting salaries and other monetary amounts.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
The new currency is added to the system and can be selected whenever specifying monetary amounts.
Level: User Complexity: Low
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 2.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to update the list of currencies.
  2. The system displays all currencies entered in the system.
  3. The user adds a new currency.
  4. The user enters the currency code.
  5. The user enters the name of the currency.
  6. The user selects the country for the currency (optional).
  7. The user enters the symbol for the currency (optional).
  8. The user saves the record (UC-ICE9).
  9. The system makes the currency available for selection by symbol and code.

Extensions:

3.a The user selects an existing currency.
  1. The system opens the currency for editing.
6.a The user adds a new country.
  1. The user returns to Step 1 to add the currency.
8.a The system determines that the currency already exists in the database.
  1. The system displays an error and will not continue.
Notes Date Added
This is a new use case requested during testing to support internationalization. Implemented in version 2.0. 2/2/2007

1.2. Position Management

Position Management

Description
Design and manage a job structure for the organization, add new positions that may be filled by employees or applicants, and manage existing positions.
Notes Date Added
Access these functions via the Administer Positions link on the main menu. 9/28/2007
Access is limited to HR Staff, HR Manager and System Administrator. 10/2/2007

Position Management use cases:

UC-PT16

Add or update a cadre

 P9
Parent: Position Management
Primary Actors: HR Manager Supporting Actors:
Brief Description/Goal
The HR Manager enters or edits a cadre for selection within the system.
Preconditions:
The user must be logged in to the system.		 Success Guarantee:
Each cadre, as applied by the health professionals, is defined within the system and available for selection in various use cases.
Level: User Complexity:
Use Case Status: Released Implementation Status: Complete
Assigned To: Release: 1.0
Flow of Events

Main Success Scenario:

  1. The user selects the option to update the list of cadres.
  2. The system displays all cadres entered in the system.
  3. The user adds a new cadre.
  4. The user enters the name of the cadre.
  5. The user saves the record (UC-ICE9).
  6. The system displays the new or edited cadre in selection lists of cadres.

Extensions:

3.a The user selects an existing cadre.
  1. The system opens the cadre for editing.
5.a The system determines that the cadre already exists in the database.
  1. The system displays an error and will not proceed.
Open Issues AssignedTo ResolveBy
The minimum qualification and ISCO classification code have not been implemented in iHRIS Manage; these should be added to increase compatibility with iHRIS Qualify. 151735 n/a
Redesign needed to match similar functions such as under Administer Database. 193043 3.0 release
Notes Date Added
This use case may be optional if new cadres are not allowed to be defined or if cadres are not used by the organization. 10/30/2007


UC-PT17

Add or update a job classification

 P1
Parent: Position Management
Primary Actors: HR Manager Supporting Actors:
Brief Descript