******************* Project Guidelines ******************* About handin procedure: Email your submission form (see below) to b649@cs.indiana.edu, do not email to my personal address. If all your files (only those you changed or added) are in one directory, say proj2/src, do "cd proj2/src" and run "md5sum *.java (or *.cc)"; otherwise, zip all your files and subdirectoies into one file, say proj2.zip (or gzip), and run "md5sum proj2.zip". Do not make any changes to your project directory before domo. If you need to reuse the code there, make a copy and work on your copied directory. You should save all your projects on burrow and set read/execute permission for b649 - you need to first make your home directory world-wide readable, and run setfacl on your b649 directory (see P536 Project Guideline for instructions on how to use facfile). A brief readme is required for each project. In some cases, test scripts are required if you want to show some special features of your program. Your readme should at least include: how to run the program, user interface conventions etc; which of the required functions are implemented; functions you have coded but not working; any extra features you added; test scripts you wrote and explanations on them; any design/implementation issues you'd like to discuss. ------------------------------------------------------------ Project submission form: Team members: Spokesperson for demo of this project: Lateness (if you handin after due time): Pathname and md5sum for your files: Contributions of team members: INSERT CONTENTS OF README FILE HERE IN UNENCODED ASCII FORMAT. Do not attach README as a mime attachment! ------------------------------------------------------------ About demo: For project 2-4, all demos will be done on Tuesdays. For B649 students, it will be the Tue. after due date. For C490 students, it will be one week after B649 demos. All demos will be done in LH125, unless otherwise indicated. Please CHECK YOUR SCHEDULE in the following list. If your spokenman's name doesn't appear on it, or you have conflictions with your assigned time, please let me know asap. If you need to reschedule a demo for a special case, let me know in advance. NO MAKE-UPS FOR MISSED DEMOS WITHOUT NOTIFICATION. To save time, please arrive a bit earlier than your scheduled time to set up your demo as follows: 1) login, 2) cd to your code directory, 3) run md5sum, 4) unzip and compile (only if you zipped your files), 5) pick up the feedback for your last project, 6) acquaint yourself with your test procedure, GRADES WILL BE DISCOUNTED FOR MAL-OPERATION. ------------------------------------------------------------ About grading: Readme/testcases/coding count for 30%. Required functions count for 70%. Robustness (error checking, exception handling etc), efficiency, scalabilty etc will be counted in addition to functionality. (- 1~3% each error, 15% max) Extra points will be credited for non-trivial features implemented. (+ 1~5% each feature, 20% max) Late submissions will be counted 10% off each day. If submitted files are modified before demo, the submission will be dated as the demo day. No submission will be accepted after demo day. Above are general rules, subject to change for individule projects. ************************************************************* Demo schedule for B649/C490 Project 2-4 B649 Proj2 demo: Mar. 20 C490 Proj2 demo: Mar. 27 C490 Proj3 demo: Apr. 17 B649 Proj3 demo: Apr. 24 Time | Tue. (B649) | Tue. (C490) | 1:00p | lifang | XXXXXXXX | 1:15p | feliu | XXXXXXXX | 1:30p | pchivuku | XXXXXXXX | 1:45p | raindurk | XXXXXXXX | 2:00p | yinjin | XXXXXXXX | 2:15p | djaishan | XXXXXXXX | 2:30p | gkandasw | XXXXXXXX | 2:45p | arossi | XXXXXXXX | 3:00p | wsibo | XXXXXXXX | 3:15p | jieli | XXXXXXXX | 3:30p | dsarkar | XXXXXXXX | 3:45p | holiu | roabaker | 4:00p | robo | pkasper | 4:15p | dwang | mshuter | 4:30p | yyuan | nkidd | 4:45p | roypivn | alllee | 5:00p | oleykin | toezer | 5:15p | ysimmhan | jeboyles | 5:30p | adhua | dtrusty | 5:45p | ranantha | jcwelch |