GRADER

Name of student running submit:
Login of student running submit:

Second team member's name:
Second team member's login:

Third team member's name (if any):
Third team member's login:

IMPORTANT:  Once you've submitted Project 2 once, the same team member should
submit always.  If a different teammate must submit, inform cs61b@cory of all
the details.  Include a complete list of team members, and let us know which
submission you want graded.

If you've submitted your project once, or even written a substantial amount of
code together, you may not change partners without the permission of the
instructor.
===============================================================================
Does your program compile without errors?


Have you tested your program on the machines in 277 Soda?


Did you successfully implement game tree search?  Did you successfully
implement alpha-beta pruning?  Are there any limitations on it?  What is the
default number of search levels set by the one-parameter MachinePlayer
constructor?


Describe your board evaluation function in some detail.


Does your MachinePlayer use any special method of choosing the first few moves?


Is there anything else the graders should know to help them read your project?



Describe the classes, components, and interfaces you designed before and while
you implemented the project.  Your description should include:
  -  A list of the classes your program uses.
  -  A list of each of the "components" used in or by MachinePlayer, similar
     to the list in the "Teamwork" section of the README (but hopefully more
     detailed).  Which class is each component implemented in?
  -  A list of the interfaces by which your components call each other.  Don't
     include every single method in your project--we will penalize you if
     you're not selective.  Include the interfaces that create a clean
     separation between the different components you have enumerated.  For
     each interface, provide here (1) a method prototype and (2) a description
     of the behavior of the method/component (which should also be in the
     comments in your code).
  -  Who implemented each component?
You will probably need to change some of your design decisions as you go; be
sure to modify this file to reflect these changes.  Your design of classes and
interfaces with be worth about 10% of your grade.