User quickly scanned the page and found the "Resume Index" link.

Note: user previously added a resume to the system, so already familiar with the location of the "Resume Index" link.

Scanned the ICS home page for the Resume Index link. Clicked on the link to get to the Resume Index page. Scanned the instructions at the top to find the login link. In an attempt to log in, the user paused to remember what password to use. After seeing the Preferences page, the user indicated the Resume section and claimed that to add a resume, one would have to type in the information, check the "Show Resume" box, and then click on the "Make Changes" button.

Note: since the user is already familiar with the steps to add a resume, the task was modified to repeating the action of how to add a resume.

Repeating the steps of the previous task, the user quickly updated the Preference section with the desired information. After submitting the changes, the user tried clicking the "career zone" link on the left side to return to the Resume Index. Remembering that the link is broken the user commented that he should have remembered it was broken, and then pressed the back button on the browser.

After this task was completed, the user quickly went back to the Preference page to revert back to the original data. When asked why the data needed to be changed quickly, the user replied that since he didn't use the service much, he might forget to change the data at a later date. He didn't want to be known as "bob".

Although the user has previous experience with the service, twice was the "broken" "career zone" link on the Preference page clicked to return to the Resume Index page. The first time was to check that the update was committed, the second when the data was returned to its previous values and the user wanted to ensure the changes were committed.

Both times the data was updated, the user needed to make sure the Resume Index web page reflected those changes.

After reaching the Resume Index page, the user scanned the skill sets that were visible by default on the page. The HTML skill was found in the first skill set. To view the resume, the user clicked on the resume icon.

The first thing the user did was scan the page before trying any finding tools.

After reaching the Resume Index page, the user used the Control-F combination to bring up the browser's find in page tool. First searched for "pascal". When no results showed up, searched for "cobol". When no results showed up again, the user claimed that he gave up, there was no resume with those skills.

The timer was stopped after the user defeat.

When the evaluator erroneously insisted that a resume had to be there, the user then scanned the instructions for the "Search Resumes" link and tried searching with that. After that didn't return any results, the user insisted that there were no resumes fitting that criteria. The user had faith that the searching tool on the web page worked properly.

After reaching the Resume Index page, the user used the Control-F combination to bring up the browser's find in page tool and typed in "Java, sql". When no results showed up, the user then tried "Java" by itself in the find in page tool. After a couple of tries, he realized that this approach wouldn't work, so tried the "Search Resumes" link. In the search he typed in "java,sql", following the example on the page. That returned every resume that contained either "java" OR "sql". Commenting that the search was not good since he expected "java" AND "sql", the user then manually scrolled through the results on the page to find the resume and opening it. He mentioned that the search should allow for both options so it's easier to narrow down searches.

From the Resume Index page, the user automatically clicked on the "Grad Date" column header to sort the column by graduation date. After scrolling a little to verify that the column was sorted, and in what order, the user headed straight to the bottom of the page and manually looked through the skills. Every so often he needed to stop to remember what date he was looking at because expected graduation dates are also posted. The resume viewed belonged to "Steven A. Miyakawa".