Team MHC

Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Group Members

Howto understand our milestone documentation

Don't wait to the last minute or day to do anything. Start early and code in groups, because it makes it much easier to understand what other people are doing and gives a block time that you are going to work on the project
The milestones are simply rough descriptions of the project. Ask questions early so the TAs have time to respond.
Watch out for changes to the milestone specs both on the swiki, in the questions on milestone on the swiki, and on the newsgroups. There may be last minute changes, so make sure that your code meets all the milestone requirements before turnin.
Squeak isn't documented very well, so you have to read the code for the methods to figure out what they do in the System Browser. This takes some time but is well worth it, as Squeak already has some useful methods coded. So make liberal use of the method finder and system browser.
Zip up your changesets before sending them over email. Sometimes they get corrupted if you send it out as plain text and you'll have trouble filing them in.
Zip up your entire project and include a readme when turning in your milestones.
Try to demo your project milestones to the TA. It makes it a lot easier to grade and you get immediate feedback.
Don't lose points over not doing class comments. The way to do this is in the System Browser; click on a class and then click the question mark inbetween the instance and class buttons to enter comments.