Because CS and HU students have class on different days, the CS sub-team and the HU sub-team will have separate cognitive walkthrough during their respective classes. The presentations will be video recorded so that you can share them with your sub-teams and the scientist.
The walkthrough presentations of the two sub-teams can share common material, but the CS sub-team should focus on the interaction design of the app’s functionality, and the HU sub-team should focus on the interaction design of the instructional and other content in the app.
All students are required to attend all presentations in their respective classes and to provide feedback to each team.
Your team will prepare initial design documents and slides for your cognitive walkthrough for the two walkthroughs. The cognitive walkthrough will provide the graduate students the material they need to perform their heuristic evaluations. Although you will have 20 minutes for your cognitive walkthrough, your walkthrough should last less than 10 minutes.
For the cognitive walk you will need a paper prototype and supporting design documents:
Your team should sketch all major views. The sketches can be neatly hand drawn or you may use drawing software, Flash or other software. The sketches can use sticky post-it notes to represent interacting components of the UI. All sketches and major views should be scanned so that they can be used in the slides for the cognitive walk through.
A good reference for paper prototyping is at Board of Innovation, Resources & Tools for Paper Prototyping.
The paper prototype should be the same for both sub-team cognitive walkthrough presentations.
Use scenarios are stories for the walkthrough and are verbal descriptions demonstrating the use of your app. They are descriptions of a single instance using the app. The use scenario also motivates the use by initially giving the context of the use. Using the personas that your team has created, you should prepare at least two use scenarios, one for nominal task performance and the other illustrating error handling. The use scenarios should demonstrate the depth of your system meaning it should not be a trivial example of using the system. Try to demonstrate as much functionality as possible.
Barnum (Usability Testing Essentials: Ready, Set…Test! Morgan Kaufman, 2010) defines scenarios as stories about “the user in pursuit of a goal” (99). Although they will include tasks that users engage in with technology in pursuit of goals, their focus is on why users are using a product to complete certain tasks, not how they are doing so. Scenarios help designers to understand user motivation and possible sources of frustration and also why, and whether, they are likely to carry out the tasks that the designers envision.
The HU and CS sub-teams can have different use scenarios so that they can emphasize ether the app functionality or the instructional and other content.
Usability Goals and Concerns Lists
You should have two usability lists: usability goals and usability concerns. Usability goals are usability principles that you used to help guide your design. Usability concerns are potential usability problems that you hope you have designed for or uncertain if you have designed for it. If you use a bullet list, you should clearly describe each listed item in a few sentences succeeding the list.
The HU and CS sub-teams can have different usability goals and concerns that are associated with ether the app functionality or the instructional and other content.
Instructional and Other Content Design Plan
HU4268 members should create a document outlining the design for the instructional and other content for the app. If the help is integrated in the app, begin considering how it will be integrated and demonstrate the integration in the paper prototype. Post the Instructional and other Content Design documents on your website, clearly indicating the authors of the design document.
HU4628 & CS4760 Collaboration
Before the cognitive walk through, your group should meet frequently to collaborate on the app design and prepare for the cognitive walkthrough. The design and implementation of the paper prototype should be team effort. Although the use scenarios and their presentation during the cognitive walkthrough can be different in the two presentations, all team members can participate in their design.
Meeting with Graduate Students
During the week prior to the cognitive walkthrough your team should meet with graduate students performing the heuristic evaluation for your app. You should provide the graduate student with any additional documents they may need. This can include:
- The slides for your walkthrough
- More paper prototypes
The graduate will need a link to your walkthrough presentation slides so that they can use them for the heuristic evaluation. The graduate students will give you a link to their heuristic evaluation. Your website should include these links.
Prepare slides for your cognitive walk through and post them on your team website. You should prepare walkthroughs for two use scenarios (described above), but you may have time only to present one use case. The nominal task performance scenario should be presented first. Only if you have sufficient time will you present the use case demonstrating error handling. (The first use scenario should demonstrate nominal usage of the app and the second use scenario should demonstrate how your app handles errors.)
Your team should prepare slides for the cognitive walkthrough. Post the slides on the website, but bring your own laptop with the slides already downloaded for presenting. Do not waste time downloading slides during your presentation.
Outline for Walkthrough Slides
- Title slide with app name, team name and date (single slide)
- Title slide for cognitive walkthrough/Use Scenario Name (single slide giving the name of the usage)
- Description of users and environment (single slide)
- Use scenario description (single slide)
- Paper prototype views (sequential slides illustrating the use)
- Usability Goals and Concerns (single slide)
Format for Walkthrough
All members of the team should be present during the walkthrough.
One or two members of your team will conduct the walkthrough by demonstrating the interaction, action by action. This should take only 7 minutes.
After finishing the walkthrough, the conductors should pause to give evaluators time to respond by pointing out usability problems or giving design ideas. The evaluators are the rest of the class. This should take another 7 minutes.
Two member of your team will record the usability problems or design ideas. These notes should be posted on your website the evening of the walkthrough.