Our usability protocols are divided into four forms or sections: scenario formation, CS92 testing, early design and content testing, and late-stage program testing.. Below is a description of each:

Scenario Formation: At several key points during production, we conducted scenario testing, which basically consists of our placing ourselves in the role of the student user and thinking about how we would react to each button, screen, or design decision. Scenario formation is a form of meta-production, asking ourselves what students will do at each point, what they will see, what happens when each button is clicked on. This portion of the testing allowed us to look beyond the immediate and place each part of the program into a greater context.

CS92 Testing: Our storyboard presentation to the class, as well as our class demo midway through production, gave us a fresh perspective on the material we had grown close to. The class asked questions, offered suggestions, and provided valuable feedback which allowed us to further clarify design issues and revise our path.

Early Design and Content Testing: Near the beginning of our project, we spoke with students in the Classical multimedia lab, discussing their computer background, and finding out where their interests lie in terms of Internet technology. Our main goal was to find out which of our proposed topics they knew about, which they cared about, and what else they wanted to learn. We also bounced design ideas off them, getting their feedback on our ideas for organization and presentation.

Late-Stage Testing: Our main goal at this point was to present two complete modules, and identify the usability issues of each. It was important to us to get a clear sense of the users' experiences using our software, so we began by asking them to play with Wires and think aloud. During this phase, we were relatively quiet, allowing the students to be alone with the program. Once this was complete, we asked more specific questions based upon the things they skipped over, paid special attention to, seemed confused about, or seemed to like. Finally, we asked for ideas as to whether there was anything they didn't see but would have liked to. Overall, this protocol seemed to have great results; we got a lot of feedback, and identified a lot of usability issues not previously anticipated which we will prioritize and fix as much as we can in the remaining time.