We met with Adam with the intention of showing him our storyboard. Unfortunately, a bomb scare at the CIT prevented us from getting our storyboard when we needed it (you can't make this stuff up!), so we ended up just describing it to him and bouncing ideas off him. Both our group and Adam had also wanted us to meet with some of the students, but as it turned out, none of them were around when we got there. In any case, we still managed to have a productive meeting.

Adam clarified for us the uses to which our software will be put: in some cases, entire classes will take the tour, led by Adam or another instructor. Initially, it will also be available as a sort of pseudo-on-line help. Issues we hadn't previously discussed that he wants us to include are questions about the difference between ethernet and a dial-up connection (to be addressed in the ISP module), the ways in which search engines work (to be addressed in the web module), and issues of network security (to be addressed, perhaps, in the first section). We discussed the idea of having clips of relevant news stories (The Net in The News, or some such) spliced into the explanations of Internet technology. For example, our discussion of packets could include a clipping of the recent BDH article on packet sniffing. Finally, Adam suggested that each time a new term is introduced, there should be a link from that term to its place in the glossary. We like the idea, and will experiment with implementing it.

We asked Adam how long students would have at any given time to go through the tour; the answer was approximately 40 minutes. Presumably, this may not be enough time to finish the entire tour, which brought up the question of how to track when students had completed the tour in order to give them the congratulations page. Adam suggested that in order to solve that problem while also reinforcing the concepts introduced, we can have a quiz at the end of the final module which addresses issues from each module; satisfactory performance will lead to the congratulations page. We also discussed having the same quiz at the beginning, as a sort of before and after comparison, but Adam didn't want the tour to feel too academic, so we may only have the final quiz.

Adam asked us about tools. While we had originally thought that HyperStudio only has a plug-in for the Mac, Adam told us there is also one for the PC, and he already has both. As a result, and because HyperStudio might meet our needs better than Authorware, we decided to do the project in HTML and Hyperstudio.

Finally, we asked Adam to put us in touch with a group of one to three students of varying levels. We want to form a focus group of sorts whom we can contact regularly over the course of the semester to discuss design issues and test our ideas and implementations. Adam agreed to ask for volunteers; we're really excited about involving the students as much as possible.

Adam agreed to find interested students of varying levels of experience with these concepts, and to think about graphic ideas before our next meeting; we promised to send him a list of terms and topics by the end of the coming week.