Whereas earlier assignments focused primarily on specific techniques and coding, the project offers an opportunity to think more broadly about building AI agents or systems, to collaborate and communicate with someone about the issues, and to be more creative in the design of the experiment, application or agent.

Milestone B consists both of a progress report and a piece of working code that reflects the progress of your implementation. This is due on May 29. For this milestone, turn in both your Python file(s) and a 1-paragraph document that answers the questions: (a) what are the main techniques you are featuring in your project? (b) How far along is your implementation (what works, what does not yet work?).

Milestone C involves (a) final code and (b) final report. The code must be working and ready to demo in class on Wednesday, June 5. When it is turned in Tuesday night, it also needs to be commented and presentable, if it isn't already.

Each project should address the following criteria.

1. Originality. The project must not be an edited version of something developed elsewhere.
2. Demonstration of an appropriate artificial intelligence technique. (In this project this is not likely to be an issue, since each option is oriented around some specific AI techniques.)
3. Transparency. The implementation should take specific steps or incorporate explicit features to help the user understand how the program works, typically showing in some form, key intermediate results, status of longer computations, and relationships among key data structures, rules, states, or constraints.
4. Interactivity. The program should allow the user to control the computation through interaction. There can be default parameter settings, but it must be possible for the user to easily override many of the defaults.

Project presentations are currently scheduled to take place during class on Wednesday, June 5. During the demonstration period, each student should complete two peer evaluations. Printed copies of the forms will be available in class. Each team should bring a laptop to class that day in order to demo your project to small groups. The time will be spent with multiple presentations to small groups happening simultaneously.

Turn in the following files (zipped up or tarred) by the Milestone C deadline. (Late days are not allowed in the project.) Report.pdf; code files; data files if doing Option 4.

The report should be an electronic document in the form of a PDF file. The key elements of your report include:

1. title of project;
2. names and roles of each teammate;
3. what the program is supposed to do;
4. technique used and brief description (half a page) of how that technique works. If you use multiple AI techniques then describe each one but with somewhat less detail for each one;
5. either a screen shot or a transcript of an interesting sample session;
6. brief demo instructions;
7. code excerpt showing some interesting part(s) of your Python code and some explanation of it;
8. brief description of what each team member learned in this project;
9. what you would like to add to your program if you had more time;
10. citations for any references you used in the project. This should include the names and URLs of any websites that you used and whose ideas or other resources were incorporated into your project. In each case, describe in a sentence what role that website played in your project and what you incorporated from it.
11. For 5 points of extra credit, include a section with a heading "Partners' Reflections" with two subsections, one for each partner. Each subsection should give the partner's name, main role(s) in the project, a description of the challenges and benefits of the partnership from that partner's perspective.