Due: 4/3
Project teams are finalized and topics chosen.
Due: 4/8
A brief document introducing the project team members and providing a schedule for activities to be performed during the quarter.
Due: Week 3
You will schedule a time with the instructor to show what progress has been made to date with your system. This is intended to be a demonstration of the software system, not just a discussion of how things are going.
Due: 4/22
An extended document that details all functional requirements of the delivered prototype. A section of this document also indicates nonfunctional requirements that will be used to test the system for acceptability and a storyboard will be used (and potentially presented to the class) to demonstrate how the system will look and be used.
Due: Week 6
You will schedule a time with the instructor to show what progress has been made to date with your system. Since this is the second demo, there needs to be clear progress shown since the last demonstration.
Due: 5/6
A detailed description of how the system will be built, including, for example any object-oriented analysis and design to show the system structure.
Due: Week 9
A running prototype of the system that is to be demonstrated to the instructor and intended to meet all aspects of the revised requirements document.
Due: Last 4 classes
Presentation to discuss your progress over the quarter in front of the whole class.
Due: 5/29
A final collection of all of the above information in a well-organized Web page. Any revisions of documents must be clearly displayed and all documents and source code must be accessible.