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:

Basic Use

Scenarios | Claims Analysis | Design Alternatives

Scenarios

Naomi is a secretary of Computer Science department. At the beginning of the semester, her department hires a graduate student as a graduate teaching assistant, so she inputs his data into the Banner system.

Scenario 1: Naomi logs in to the Banner system

Naomi double clicks on Start Banner icon on the desktop. The Logon dialogue box appears on the screen. It looks like a typical dialogue box of Macintosh operating system. She types the Oracle ID in the Username text field, the Oracle Password in the Password text field, and "banner" in the Database text field. Then, she clicks on the Connect button. The General Menu form window shows up on the screen.

The General Menu form is called GUAMENU which is shown on the title bar of the window. In the window, there is one text field labeled "Enter Selection ==>." which follows the "*no current messages*" button (is this a message sub-window?). There are five menu items labeled from A to E in the center of the window. There are three buttons at the bottom right corner: "Main," "Previous" and "Exit." Bellow the window, there is a message ribbon.

Scenario 2: Naomi opens the Virginia Tech Employee Identification form

Naomi notices that the cursor changes from the arrow to the I-beam. Though the I-beam cursor does not suggest "selection" in menus, she clicks on the "*VT HR DEPT" item. The "VT HR DEPT" System Menu form window appeares on the screen.

After a quick glance of the window, Naomi notices that the window is very similar to the General Menu form window. She clicks on the second item of the menu, "B- PWAEBO Virginia Tech Employee Identification form." Its form window shows up on the screen.

Scenario 3: Naomi inputs a zip code

Naomi sees the Virginia Tech Employee Identification form window which is called PWAEBO form and notices that there are many text fields, buttons and a vertical scroll bar. After typing (I cannot remember detailed things here), she clicks on the "ZIP:" button; then, suddenly a Query Form window relating zip cords appears on the screen.

Claims Analysis

• Shorthanded form names
  • allow users type less words than its full name.
  • are cryptic.
  • may be hard to remember.
  • can cause typing mistakes since they are not common words.
• Labels of menu items (starting from A in alphabetical order)
  • provides users short-cut key of the menu items; it reduces the number of key strokes (GOMS).
  • can cause selection mistakes because there is no logical matching between the labels and the menu items.
• I-beam cursor for selection items
  • allows users to choose an item from the list.
  • may be misleading since in Macintosh OS, the I-beam means an text input (downward consequence of TAG).
• Buttons in Application form windows
  • some of them provide users dialogue boxes to choose an item; the others do not cause any actions.
  • may violate TAG of the Banner system.

Design Alternatives

• Shorthanded form names
  • use the meaningful abbreviations for form names; for example, GENMENU or simply GENERAL for General Menu form.
• Labels of menu items
  • use the meaningful abbreviations of menu; for example, A for ALUMNI, H for HRS, G for General, V or D for VT HR DEPT, and P for PASSWORD. In addition, underline them.
• I-beam cursor for selection items
  • use the arrow cursor when users can choose an item from list items.
• Buttons in Application form windows
  • provide the information on the button, i.e., if it causes a dialogue box, add "..." on the title of the button; for example, "ZIP:" should be "ZIP..."
  • or use pop-up menu items with default input item of the field.