Code Project Outline
If you write code, you need to provide a report on what you did.
- an introduction to the project
- provide a high-level description of what the project is about (introduce the reader to the project)
- Is it affiliated with some particular game? ... some particular (or general) activity/potential?
- Is it a completely new addition [to something]?
- Is it a adaptation of someone else's code? (cite)
- an introduction to the problem being solved
- you should begin with a description of the problem and the desired (AI) properties of the solution
- you should have a least a few references - it does not have to be comprehensive
- a technical description of the solution
- sample code if appropriate
- discuss algorithmic details as necessary
- a description of your contribution to the project
- if you wrote something which has a GUI or something that can be demoed, provide in your writeup a "walk-through". This would mean taking screen shots of your code running and discussing them (as you would if you were giving a demo in person).
- if you did an individual project, state that you did everything; if not, be clear on what portion of the solution you did.
- you should include a brief survey of what games/genres might find the technique useful
- discuss what you learned by doing this project
Bibliography
- At least 5 references (not counting the two text books). You can reference the texts, but they do not count as your research effort).
- At least 3 references that are from refereed sources (i.e., not the web)
- See dept site for example information for references
If possible, I would like a demo of your project for the class. Given hardware inadequacies, this might not be
possible. Hence the "walk-through" of screen shots is very important.