CIS 700 Programming & Problem Solving - Fall 2013

Project Presentation

Your project presentation is considered part of your project report and is not only a chance for you to communicate your ideas and impress your classmates, but also to work out anything that needs to be resolved before writing your paper.

Each group will have 10 minutes to do their presentation. Please make sure you practice and that you can finish in 10 minutes! It's a lot less time than you might think. Try to keep it to 7-8 slides.

Keep in mind that this is a presentation, not a "demo", so there should be some structure to it. I recommend organizing it as follows:

1. Initial Insights and Observations
When you first started working on this project, what were the first things you thought about? What were your insights, observations, and intuitions?

After you started implementing and analyzing your solution, what did you realize needed to be changed?


2. Strategies & Concepts
Now describe the main idea behind the solution you submitted. Do not explain the implementation details (you'll do that in the next section) of how you wrote your code, but start with a high-level overview of what you were trying to accomplish and why you thought it was a good idea.

Imagine you are explaining your solution to your parents: just give a general idea of what you were trying to do, and why you thought it would make sense to do that.

This would be a good place to include screen-shots showing your solution at work, especially if there is some step-by-step process that is difficult to explain in words. And it's always good to use specific examples. The more specific, the better.


3. Implementation
Next, explain how you actually implemented the solutions described in the previous section. Make it clear what parts you solved in your heads (and thus hard-coded into the solution) and what parts you allowed the software to figure out for itself.

The most important information in this section regards the different algorithms that you used. It must be very clear how they work and how you implemented them. You can include pseudo-code if you'd like, or the actual Java code from your implementation (we won't look at your code unless it's in this document, but please don't just dump all of it into this report).

Also describe any formulas you used to determine the behavior of your code. If your implementation included any hard-coded constants or parameters, explain the effects that those had on your solution.


4. Analysis & Results
Discuss the results of your submissions to the end-of-project tournament. There are two things to focus on here: are your results "good"? are your results "better" than other groups'? Those are not necessarily related!

In describing whether your results are "good", refer back to the Approach section and relate your initial thoughts and intutitions to the actual experimental outcome. That is, did you set out what you hoped to accomplish? If so, how do you know? If not, what went wrong?

In describing whether your results are "better" than other groups', feel free to put a positive spin on things. For instance, was there a particular configuration or aspect of the problem that you were significantly better at? Be careful about meaningless self-congratulating platitudes, though: "we were consistently in the top five" doesn't really sound good if there are only five groups!

If you performed additional experiments outside what we agreed upon for the tournament, and those experiments reflect positively on your implementation, include those results, too.


5. Contributions
Conclude by describing the contributions that your group made to the class as a whole. Were there any specific insights that you had that helped other groups? Did you identify any algorithms or solutions that no one else thought of? What was different/unique (in a good way) about what you did for this project?

Updated: Sept 19 2013, 11:21am