(Submit by email)
This is a "works cited" page that cites every every source you read, with a couple of lines of description about each source. You should include a brief description of the topic(s) covered by the paper, as well as comments about its relevance and usefulness for your project and paper. The best way to do this is to write an annotation for everything you read, as soon as you read it. When it comes time to put together your paper, it will be easier for you to track where you learned the information that you need. It also serves to document the research that you did that, for one reason or another, didn't make it into your project and/or paper.
Your poster should serve as an advertisement for your project. It should include your abstract and some visual material to make it interesting. The poster should be eye-catching and easily readible from 3-5 feet away. Don't forget to also include the title of the project, your name, and the time of the presentation on your poster.
Very nice posters can be made using the large-format printer in the media center. To do this, you need to create a powerpoint presentation (one slide) whose size is 48x42 inches. Depending on the amount of type you need, sizes from 36 points to 40 points might be appropriate. Here are two examples that you can use as templates (replace the images and text with your own):
Once you are satisfied with the poster, you can print it at the media center. You can charge one printing to the Computer Science Department, so be sure you are ready when you go to print. (See Valerian Anderson for help or instructions).Posters will be posted in the hall of Colton during the week of the presentations. Due by the beginning of Week 12.
Your paper should be a research paper in the scientific style, using as many pages as you need to fully explain your research project. It is very unlikely that this will be less than 10-15 pages, and it could be considerably more. Your paper should include the following sections. Section titles are provided as guidelines, rather than a required template. It is possible that some papers will add more sections or combine some of the sections below.
What problem are you trying to solve? Why is it interesting? What technique do you plan to use, and why? (Why might also be answered in the next section). This section can often be taken directly from the proposal.
What approaches to this topic have already been tried? Describe the major research that
has influenced (either positively or negatively) your implementation choices. A good
relevant work section tells a "story" leading up to your choices of implementation techniques.
It should not just be a sequence of paragraphs of the form, "in their work,
Describe your implementation in detail. Include the design and implementation process as
well as the final implementation. Use diagrams and screenshots where appropriate.
Explain as clearly as possible how your system works. (This is often best done by going
through a simple example run in complete detail).
Show the results of your project.
Try to avoid tuning your system for just one example. If you used a very simple example
to explain your system, show the results of more complex examples here. If appropriate, also include summary statistics or other analysis.
Discuss and evaluate your project, according to the criteria you set in the proposal. Where the
results differ from expectations, explain why. What would you do if you had more time? What
would you do differently if you were to start over? What did you learn by doing this project?
(You might choose to separate evaluation,
future work, and conclusion into three sections. If you do this, the conclusion should succinctly
sum up what you learned from this project.)
Your code should be substantially original. If you use code from any other source (including the textbook), it should be clearly marked as not your own, along with a citation of where it came from. If you have found code that you would like to use as part of your project, the safest course is to discuss it with me before you rely on the code. (Some code can be considered "infrastructure" rather than "project").
Please submit one CD ROM that contains all of your materials: Proposal, Poster, Annotated Bibliography, Implementation (source code with documentation), Presentation, and Paper.
As we have done in the past, we will set up conference-style sessions for presentations. Each presenter will have 20 minutes to present their work, followed by up to 10 minutes for questions. If you plan a demonstration as part of your presentation (this is recommended), it must fit within the 20 minutes. Your presentation should give the highlights of your work. While it should be targeted to an audience consisting of your classmates, at least part of the presentation should be accessible and interesting to a more general audience, such as CPSC 171 students.
Your presentation should have an introduction that captures the audience's attention and provides an excellent overview of the project. You should present material at an understandable, but not trivial technical level. You should cite your sources and resources. You should explain why you chose the project, what made it exciting to you, how you did the project, what difficulties you encountered, what you would do differently if starting over, and what enhancements you would add (if you had more time). You should end with a conclusion that summarizes the main parts of the project and what you learned. Everyone present will be asked to evaluate each presentation with this evaluation form.