Submission Deadlines
Electronic Submission
Grading
Cross Platform Development
Teams and Team IDs
Some graders will require submission of your program on paper. Your grader will explain in section whether this is required. The hard copy submission must be the same program you submit electronically, including all formatting. You may use programs such as enscript or prettyprint to clean up your results, but your electronic file must be equally readable (see Grading, below). This hard copy should be submitted to the instructor grading your team's programs. Only one team member need submit a hard copy, where applicable.
All members of a team will receive the same grade on a programming project and, consequently, on the programming portion (35%) of your final grade. Sometimes, members of a team feel that the work load is not being shared equally. If you feel that this is the case, you should first try to work it out diplomatically with your partner. If that fails, you should contact your TA before the problem becomes a big issue.
Finally, as with the homeworks, the programming projects are also subject to the course policy on cheating and collaboration, so please review them if neccesary. Remember, you can always talk to your instructor if extenuating circumstances are placing your team under time pressure.
Do not do your program development in that directory. Files that are not .java or for submission are subject to random and untimely deletion. (This isn't just so we can be mean; if everybody works in the submission tree, we'll run out of space).
To submit your project, create a subdirectory in your team's directory named progX, where X is the number of the current programming project. Leave the .java files that you are submitting in those directories (do not submit .class files; they will be ignored and/or deleted). At the submission deadline (9 a.m. on the appropriate Wednesday), files in your progX directory will be copied and sent to your grader. Your directory will be renamed progX-submitted, and you will lose write priviledges. There is no early submission, and any problems (i.e., your submission directory does not exist at collection time) are the responsibility of the team.
For late submissions, you may create a new progX directory, which will be collected in the same manner 24 or 48 hours later (be sure to read Submission Deadlines, above). In those cases, the directory will be renamed progX-submitted-85, progX-submitted-50, or progX-submitted-0.
Style, that elusive aesthetic quality of your program, is defined (insofar as this class is concerned) in 15-212 Java Coding Style. Note that this document is a work in progress, and will not be enforced for the first assignment. For further information on coding style, you may look at the links under, you may Java Coding Standards on the course textbook page.
If you have any questions about these guidelines, see your section instructor.
Team Number | Members (e-mail, section) |