Deadlines, August 12^th and August 22^nd

This is important new information. Your first major project submission, with documentation and working code on the CCS Unix systems is due by midnight, Monday, August 12th. Credit for this first project submission is 5% of your total course grade, half a letter grade.

The final version of the project is due by midnight, Thursday, August 22nd, the last day of classes for this Summer Quarter. Credit for the final version will be 5% of your total course grade. That and the 5% for the first major report will total 10%, which is the portion of the total course credit apportioned for your project final report(s) -- one full letter grade.

Be warned that we will be very exacting in our grading of your final Project Reports, unlike our grading of your weekly handins. Your weekly handins are typically much too short to serve as final Project Reports. Many of you hand in half a page at your weekly meetings. Your final reports should be closer to 1,000 words in length, plus diagrams and code. They should be carefully written and edited (and spell-checked!).

We will do our best to get some feedback to you rapidly after the August 12th due date, in case you need to do some final tweaks. If you are able to get a preliminary version to us before the 12th, all the better, because we can get feedback to you sooner. And of course bring any material and questions to your weekly project meetings.

What to do and hand in

• Place your source and compiled code on the College's Unix system and tell us path to your files. Mail the location to Ms. Zhang xin@ccs.neu.edu including your project title and both partner's names, if for some reason you haven't done so already. Check that your code is accessible by having one project partner try to access the code in the other partner's directory location.
• Have a brief plain text Readme file in your code directory that explains four things:
  • What we should run.
  • How to interact with your code, if that's the way it is set up.
  • What we should expect to see as the output/display/results of running your code.
  • What Object-Oriented Design principles and techniques are demonstrated by your system. (The remainder of your explanation, and a discussion of your design and implementation will be in the Project Report described below.)
• Turn in a reasonably complete first draft of your Project Report. You may post this report on your site, but you must turn in a hardcopy no later than the beginning of class, Wednesday, August 14th. Sentence on Breadth added 8/4/02: This should include a first draft of your Breadth Requirement, but the emphasis should be on your OO Design and implementation, with the full final breadth component handed in along with your final project report on the 22nd. Since this is just your first draft, it would be far better for you and for us if you could hand in this draft at the beginning of class on Monday the 12th. The report should contain the following, at a minimum:
  • What OO Design principles and techniques are being used and/or demonstrated by your project.
  • How the principles and techniques were implemented in your code.
  • What parts were difficult or not so difficult and which were rewarding or not. Please be specific.
  • What you feel you accomplished and what you would have still liked to do.
  • Sample input/output pairs that demonstrate the principles and/or show your system's output. Diagrams are a required part of your report, typically some types of UML diagrams. You should try to go beyond simple class diagrams and include interaction and sequence diagrams, as appropriate. You can also include CRC-like diagrams too. Your diagrams can be hand-drawn, on separate pages if you like, to make your report easier to prepare. Just be neat and include some text with your diagrams that explain what they're about.
  • A list of web pages, books (which sections in particular) or articles you used to help you build your system. Do this in the standard way (there are many sources of information about how to do this, e.g., this one).
• The electronic version of your Project Report can be in any format you like, but you are still required to hand in a hardcopy that we can read and mark up. For example, your Report could be created as a web page or set of web pages at some URL we can access.

Go to COM1204 home page

Return to Prof. Futrelle's home page