Final Project Presentations

The final project presentations will all be held in the 212 WVH lab. All students who normally attend the lab or lecture scheduled for the presentation time should attend. Attending the presentation will allow you to see different programming styles, hear the comments of the instructors about the project design and implementation, will give you an opportunity to comment on your peer's projects, and will show you the breadth of ways how projects of this kind can be designed.

Please, read carefully the instructions for what materials to prepare for the presentation, how to set up before the presentation, and how your presentation should be organized.

The documentation for your project should consist of the following three parts:

• User's Guide: This should be a short (one page or so) description of what your project does and how to 'play the game' or 'run the application'. You should include one snapshot of the game in progress, or a transcript of the console, if the program uses only console for user interactions.
• Design Overview: This document is for a programmer who may be asked to modify your program three months from now. It should include a class diagram (hand sketch neatly done is OK) and a brief description of the classes in the project and their role. To check if you document if effective you may show it to another student who does not know about your project and see if they can understand your design from reading it.
• Javadocs The entire project should be documented using the Javadoc style. You should then run the Javadoc program, generate the documentation pages, and show them during the presentation.

Bring four copies of the User's Guide and Design Overview to the presentation. You will give one to each instructor and each presenter should have a paper copy to look at when there are questions.

The presentations are scheduled to last 15 minutes each with no break between the presentations. That means, when you time comes, you should be fully prepared to start, with all projects configured, web pages loaded, the application ready to run. At home make a list of all that you will need to do, package the files you need, save them in at least two different locations (e.g. you and your partner's myFiles) and know how to get all started using either one of the lab machines, or your own laptop. If you plan to use your laptop, make sure you have the power supply, have a backup plan, in case that fails, know how to use your laptop with the projection.

In the lab we will have several projectors, so that while one group is presenting another one or two groups can be preparing for the presentation. That way you will have time to set up your computer, open the Eclipse, the web browser, add the settings for Eclipse projects (libraries), and briefly test drive your presentation.

The presentation itself will consist of the following segments:

• Demo a 2-3 minute live demo of your project.
• Programmer's Overview 2-3 minutes where you show the class diagram, the Javadocs, and explain the program structure. Make sure both partners take turn in presenting this.
• Eclipse Project a 2-3 minute highlights of the classes that comprise your project. Make sure both partners take turn in presenting this. You are not required to use Eclipse IDE, but should be able to navigate to any file within the project with ease.
• Question Time where we will ask questions about parts of the program. We may direct any of the questions to any of the partners. Audience is allowed to ask questions as well, but the instructor will moderate the question session.

We will evaluate both the code submitted to the server and the different aspects of the actual presentation. For some parts of the evaluation both partners earn the same points, for some parts of the presentation each partner's contribution will be assessed separately - with points earned awarded to each partner individually.

The presentation will be assessed as follows:

• Written User's Guide 3 points (joint)
• Written Design Overview 3 points (joint)
• Demo 3 points (joint)
• Programmer's Overview and Javadocs 3 points - each partner can earn up to 3 points
• Eclipse Project: code overview 3 points - each partner can earn up to 3 points
• Question Time 5 points - each partner can earn up to 5 points

The code will be graded on the design clarity, test coverage, documentation, and aesthetics, earning additional 20 points.

Posted: April 2, 2009 12:50 pm