On Storyboards in CS92/ED89

The storyboard presentations are your group's chance to show the rest of the class how you envision your project taking form in the next few months. The guidelines here are to help you, but there are no strict rules as to how your presentations should be. Be prepared, though, for questions, suggestions, and criticism from the audience. This exercise can provde a useful chance to get feedback from the class, so the more clearly you explain your project, the more relevant the comments are likely to be.

Guidelines:

• Briefly review the information on your detailed project description, including goal, audience, and 'metaphor', if you've chosen one. It would also help to introduce yourselves to the class one more time and explain your each person's role in the development of the project.

• Discuss your choice of a programming tool. If you have not yet decided, this is a good time to ask ta's and classmates who might have experience with authoring tools already. Example of tool justification at http://www.cs.brown.edu/courses/cs092/blessed/main.html, follow II.D.i Introduction to the Storyboard link.

  The rest of the class should be able to understand the basic idea of the project, the look and feel, and the overall organization of the program. Flowcharts can be helpful here and if the program is divided into distinct sections, make those clear to the class. An example is the flowchart at http://www.cs.brown.edu/courses/cs092/RIMA/story.html.

• Explain how you would like a user to go through a typical session with your program. You can use key frames, with or without graphics, to explain this flow. Example of key screens at http://www.cs.brown.edu/courses/cs092/blessed/main.html, follow II.D.ii Puzzle Types link

• Try to justify as much as possible the choices made thus far for the metaphor, the interactivity of the user, the pedagogical strategy of the program, and the sequence of program events. You might explain your justifications based on issues raised in class or in the readings we've done. Examples of such justified descriptions might look like: http://www.cs.brown.edu/courses/cs092/Matter/Wheeler.mission.html#Picture and http://www.cs.brown.edu/courses/cs092/Matter/Wheeler.mission.html#Experience

There is no need to include specific content if it is not yet available.

There is also no need for graphics that will not be part of the final project. Unless, of course, the graphical component is crucial to understanding the program.

To present your storyboard, you may use web pages, transparencies, powerpoint slides, any of the authoring tools available, paper, or the white board. Please do not, however, spend time building something that will never be part of your final program or part of your final project page.

Last but not least, if you need help in putting together your storyboards or giving them a test-run, don't hesitate to contact the TAs.