Table of Contents

Home

Overview

Scenario-based Claims Analysis

Suggested Improvements

References

CS5724 -- HCI
Dr. Carroll

Scenario-based Claims Analysis

Scenarios and associated claims analyses:

Adding Records

Scenario | Claims Analysis | Design Alternatives

Scenario of entering data for a new employee using the Banner System

Scenario:

John has just been hired by the College of Human Resources and Education to fill a position as Associate Professor in the Instructional Technology Department. He has filled out his new employee form and turned it in to the department secretary.

The secretary starts entering the new employee data into the Banner system. The first page contains general information on the employee and the secretary fills in each box with data taken from the paper form. In some of the boxes she must type in the data, in some she clicks to see a menu of possible choices for that box. Once the first screen is completed, she must exit the form, and save it, then go into the next form to continue adding data. To enter the data in the different boxes, the secretary clicks on the appropriate box with the mouse for some selections, and uses the arrow key to move to others. After all of the data has been entered, the secretary saves the form and exits the Banner system.

Claims Analysis

All of the data boxes look the same. In some you type in data, in others you click and select from a pull down menu.

• - Having similar material in a selection box makes it less likely the user will make an error entering the data.
• but, the boxes are similar and it is hard to tell which ones require typing and which have selection choices.
• but, the user may not remember that some require a mouse selection and some require typed entry.
• but, the user must move their hand from the keyboard to the mouse when entering data via a mouse selection, adding to the time it takes to complete a form.

When you exit the form, it is not automatically saved.

• - The form is stored in 'pending' until saved by the user allowing modifications before the final form is submitted.
• - If the user needs to leave the computer, the form is held without loosing data already entered.
• but, the user may forget to save the form, holding up processing for the employee.
• but, the user may loose data due to a system crash and have to re-enter all of the data for employees.

To select the different data entry boxes you click in the box with the mouse, or use the arrow key to select a box.

• - The user can use the arrow key to jump to different entry points on the form allowing for quicker access.
• but, the user may arrow over a box that uses a mouse entry and enter incorrect data in a different box.
• but, the user must move their hand from the keyboard to the mouse when entering data via a mouse selection, adding to the time it takes to complete a form.
• but, there is no indication to the user which box uses text data and which uses mouse selected data causing confusion to the user.

Design Alternatives

• The data entry boxes should all look the same and work the same. If a box has pre-determined data, it should be a different shape so the user can see visually that this entry point is different.
• Saving of data should be automatic on every change of field allowing for minimal loss of data. This should be a built in feature, not something the user must execute.
• Use of keyboard should be available for all data entry points, and use of mouse should be available for all entry points. This allows the user to make the choice based on skill level.