Create your planning document as a google document.

• Name of google doc:

       cs1S14 username username Planning for title

  where usernames are the usenames for all team members, and title is a brief title for your project

• Share the google doc with both rab@stolaf.edu and rab.stolaf@gmail.com

Sections of the planning document (see example):

• Internal title of document and list of team members

• Brief description of project idea

• Features list, indicating more specifically what your program could eventually do. Group these into two categories:

  • Baseline features, a simple starting point for the program -- a minimal version that you can complete by Wednesday or Thursday 5/7 or 8.

  • Extra features, other features you would like to add to the baseline as time permits

• Some essential classes that your project will use. You don't need to give a formal spec, but indicate what each class represents, and list some important state variables and some methods for each class.
  Note: For WMR-based projects that do not use classes, instead describe some key map-reduce cycles you will need. You don't need to give complete IN/OUT specs, but indicate what these cycles need to accomplish, with informa indication of input for mapper and output for reducer.

• General timeline for completing the work.

  Note:

  • Plan to finish your baseline by Wednesday or Thursday 5/7 or 8.

  • Plan to present a brief demo of your project as a team on Monday 5/12

Add indications of who will take primary responsibility for which baseline features and which classes