Each team will give a 30 minute presentation of their final project. Since the projects themselves are not due until the last day of class, some teams will probably be presenting work in progress, rather than a finished product. Those of you who are presenting work in progress may want to use part of the presentation as a chance to ask students in the class for suggestions and feedback on those aspects of the project that you presented.

Some general guidelines for your presentations:

• Use the overhead projector. Those of you who built stacks can use it to present your stacks and explain the scripts in your stack. Those who wrote papers can use it to present relevant web sites, or an outline of your paper, or quotations, or pictures.

• Try to include the audience in parts of your presentation-- audience participation is always good. Allow some time for questions (people in the audience should be thinking about questions to ask). Those of you who wrote stacks can put your stack on the server and let people copy the stack and try it out during class. Those of you who wrote papers might spend some time leading a class discussion on some of the key issues you researched.

• Try to convey to us what you find interesting about your topic, and why you chose the topic you did.

• Be creative!

For those of you writing papers, here are some possible topics to include and questions to answer in your presentation:

• What are the questions which you set out to answer? What kinds of answers did you find? What questions do you still have?

• What did you find most interesting in the material you researched?

• How does your paper relate to material we covered in class, lab, or discussion?

• Is the topic of your paper relevent to current events or current developments in computer technology? What implications does your topic have for the future of computing?

• What kinds of sources did you use? Did you find useful sources on the internet?

• If you had more time, what kinds of issues would you research further? How would you turn the paper into a 40 page thesis?

For those of you writing HyperCard stacks, here are some possible topics to include and questions to answer in your presentation:

• What is the purpose of your stack. What does it do? Why is/isn't a Hypercard stack a nice way to achieve this purpose? Would your stack be something that the early pioneers in the development of computers would have ever envisioned using a computer for? Are there commercial applications which are similar to your stack? Would your stack be marketable (with a little improvement, maybe)?

• What kinds of decisions did you face in the design of the stack? What kinds of issues did these decisions address? How did you approach the design? Did you start by planning everything out on paper? Or did you start right away in Hypercard and plan as you go?

• What kinds of scripts does your stack use? How do these scripts work? Do your scripts use any features of HyperTalk which we didn't use in class and lab?

• Comment on the user-interface of your stack. Is it user friendly? How could the user-interface be improved? What kinds of issues were faced in the design of the interface?

• What were the most difficult problems your team faced? What solutions to these problems did you arrive at?

• What was fun about your project? What was not fun?

• What did you learn from working on your project? What did it teach you about scripting? About Hypertalk?

• What would you change about your project if you knew more programming or had more time? How could your project be improved?