Use Case:CM-3: Difference between revisions

From IHRIS Wiki
No edit summary
 
(One intermediate revision by the same user not shown)
Line 3: Line 3:
  |description=The user adds to or updates the list of competencies obtained by an employee.
  |description=The user adds to or updates the list of competencies obtained by an employee.
  |actor=Training Manager? HR Staff?
  |actor=Training Manager? HR Staff?
  |preconditions=TThe person has a record in the system. The user must be logged in to the system. The competency and competency evaluation must be added to the system.
  |preconditions=The person has a record in the system. The user must be logged in to the system. The competency and competency evaluation must be added to the system.
  |success=The employee's competencies are saved and displayed with their record, the evaluation history for each competency is updated, and the competencies are available for searching.
  |success=The employee's competencies are saved and displayed with their record, the evaluation history for each competency is updated, and the competencies are available for searching.
  |mss=#The user selects the option to add competencies to a person's record.
  |mss=#The user selects the option to add competencies to a person's record.
Line 21: Line 21:
:5.a  The user does not select an evaluation date.
:5.a  The user does not select an evaluation date.
:#  The system enters today's date by  default.
:#  The system enters today's date by  default.
|resources=[http://www.google.com google]
}}
}}

Latest revision as of 12:06, 4 May 2011

Use Case: CM-3 Assess an employee's competencies


The user adds to or updates the list of competencies obtained by an employee.

Primary Actor Training Manager? HR Staff?
Pre-Conditions The person has a record in the system. The user must be logged in to the system. The competency and competency evaluation must be added to the system.
Success Guarantee The employee's competencies are saved and displayed with their record, the evaluation history for each competency is updated, and the competencies are available for searching.
Main Success Scenario
  1. The user selects the option to add competencies to a person's record.
  2. The system displays the competency model.
  3. The user selects the competency to add.
  4. The user selects the competency evaluation (optional).
  5. The user selects the date of the evaluation.
  6. The user enters a date when the assessment expires or should be re-evaluated (optional).
  7. The system sets a flag to appear on the person's record when the date has passed that reminds the user that the person needs reassessment.
  8. The user saves the record
  9. The system saves the competency information and displays it in the record.
  10. The system provides the option to update the competency or view the evaluation history for any competency.
Extensions
3.a The system detects that the competency is a parent category.
  1. The user checks the category to add all subcategories and competencies within that category to the record.
  2. The user expands the category to select subcategories or competencies within the category for addition to the record.
5.a The user does not select an evaluation date.
  1. The system enters today's date by default.