Technical Report

Write a technical report about your project. The report should be organized like a computer science conference paper with length ranging from 4-6 pages of main content (not counting optional appendices). It is not necessary to use a specific technical document layout (e.g. the ACM conference format) -- a pdf exported from Google Docs with nice section headers would be reasonable.

Things that should be included:

- A descriptive title that will make sense to AI/Games researchers outside of the class

- An authors list including all team members (submit one report per team)

- An introduction to the project that sketches what value you believe the project has for what stakeholders and outlines the problem setting and approach. The introduction should describe the technical and design contributions of the project. 

- A related work section that explains how your project relates to the closest academic and/or industrial projects (formal citations are not necessary if you'd prefer to simply put hyperlinks in footnotes)

- Some number of content sections that explain the project in more depth, using screenshots or diagrams from your presentation where appropriate. Recycle material from your presentation where possible. The impact and technical achievement of the project should be clear from these sections. 

- One of the content sections should describe the results of playtesting with three different people. I'd suggest playtesting with two people from the class (who already have some idea of what your project is about) and one person from outside the class (to see how people who have no prior idea about your project react to it). It is ok for these playtests for them to have a paper prototyping component (in addition to your implemented component) or for you to serve as the interface to the project. You should also give playtesters an introduction to the project so they have some framing before they start interacting. From the playtests you can learn which aspects of your design people understand, which they find confusing, which aspects of the design you would continue to develop and which you would change. 

- A useful conclusion section, however brief.

- Optional: Appendices containing extra code samples, screenshots, or other material that you are either particularly proud of or think might add some clarity.