Group 1
CS 4970/ 5973
March 6, 2003

Project 2 – Milestones and Fallback Plan


       This document lists the milestones set for this project, as well fallback plans for each milestone should problems occur.  
       Inter-group checkups on approaching milestones will be made throughout the lifetime of this project in class meetings.  Email will also be used should class be missed.  If a member with an upcoming milestone should go incommunicado, it will be assumed that his milestone will not me met, and the backup will begin work on that piece of work.

Hardware Development 
March 14, 2003
	The hardware should be to a point where preliminary testing and integration is reasonable.
Fallback
	Manohar will assume hardware development should problems arise.
	
Software Development 
March 14, 2003
	The preliminary code should be written and ready to download into the robot’s Handyboard
Fallback 
	Should both software developers have problems with this milestone, Romain and Adam will take it up.

March 23, 2003
	Code should be to a point where all simple errors (e.g. motor control, problems with basic functions) are eliminated, leaving larger concepts (e.g. completing the goal) to the testing phase.
Fallback
	If this milestone is missed, it rolls back into the testing phase.  Unfortunately, half 	our team is gone for the duration of this milestone.

Testing
March 24-26, 2003
	After this time the robot should be fully functional, fully tested, and ready for a complete demonstration.
Fallback
	None.