TURNING IN YOUR PROJECTS

Please note the importance of the directory
/proj/demsys/com3360-f98
if you have an NU account.

The goal is to save your code for future courses/projects and to put the completed
projects (or at least a summary) on the WWW.

Put into /proj/demsys/com3360-f98/YOUR_LOGIN
the growth phases you went through but don't leave any
*.java or *.class files in the growth phases, except the last
one which should contain compiled Java code ready to run.

Please submit your project to com3360-grader@ccs.neu.edu
=========
the reason why you had to email the hws and keep the hw directories
private was that everybody did the same homework.

But with the projects it is different. They are all individualized
and all you need to do is to open your project directory
and send the path name and README-project file to com3360-grader.

=========

Josh's task is to install your program (if you developed it on
your own machine) and to run your program on the input you provide and on a few
inputs which he prepares and he will give me a report on how
well your program works.

Please make it easy for him to install and to prepare some inputs and to check
whether the output is the intended output.
Give him the relevant information as succinctly as possible.

If you provide HTML files as part of your project (some of you have
very useful ones), please make sure they are location independent
so that they also work in my directories.

I will then study your programs and make an overall evaluation
taking the complexity of your task into account.

If you worked in a team, please send me the peer report (see below).

The final exam is Thursday, Dec. 17 for NU students and for NTU students it is
on Dec. 18 by email (no Federal Express).

For NU students, the project deadline is Dec. 14; for NTU students it is later.

Since not all projects can be graded at the same time, there is some flexiblity
with submitting late but I hope to get a few projects 
early or on time so that the process
can start. With some more complex projects we have already made agreements
for later submission.

Looking forward to studying all your work.

-- Karl L.


o What do you need to hand in at the end of the quarter?

  What you hand in is all electronic. The description is at
  the very end. The goal is that the information you hand in will
  allow other students to build on your projects. You may assume
  that those students are as educated as you are in object-oriented
  systems development using adaptive programming.


WHAT TO TURN IN. 
================================================

FOR GROUP PROJECTS:

To get additional input regarding the grade for your project, 
I would like you to evaluate your peers. Please answer the following
questions in the last week of the quarter, put the 
answers into an envelope into my mailbox or bring it to class.
NTU students please send by email.

===============
Project:

Your name:

Let's assume that the grade for your project is B. Which grade would you give 
to each of the team members (including yourself)? Why?

The evaluation is confidential. It will serve as additional input
for assigning a grade.
=============

FOR ALL PROJECTS

OPEN YOUR FILES FOR READ ACCESS.
Put your project in polished form into:

/proj/demsys/com3360-f98/YOUR_LOGIN

if you have an NU account.

For the purpose of grading your projects, and saving your assignment
code, please use a command such as:

chmod -R go+rx xy &

for the top directory which contains your project.
Make very sure that the top directory itself is world accessible.

---------------------------------------
Include the following information in what you turn in
for your project: Put this information into file 

/proj/demsys/com3360-f98/YOUR_LOGIN/README-project

and mail a copy to com3360-grader.
----------------------------------------

NOTE: FOR SOME PROJECTS  SOME OF THE QUESTIONS BELOW
ARE NOT MEANINGFUL. IGNORE THEM.


Your name:
Your host:
Account Number:
Project: (brief description)

Credits: (from where did you reuse some of the software/ideas in your project?
	  reuse is good as long as you give proper credit. Give directory
	  names and name of person from which you used ideas.)

Class dictionary  which you used. 

Growth plans which you used. 

Parts of your project which you would have developed further if
you had more time. Include a list of known bugs here.
(The more bugs you know, the better you have tested your project!)

Names of files where test inputs can be found.

Names of files where outputs can be found.

Include one interesting input/output pair in this file.
  (well, if your output is graphical, maybe you have some printed
   form for the graphical information.)

Include one interesting input/output pair where the behavior of
your program could be improved.

Any information which you think is useful to properly reuse your software.

Please answer the following questions: 

Did you change the generated Java code?

If you had the priviledge to have one of my graduate students as host or
if you had interactions with the teaching assistant,
an evaluation of their performance would be welcome.
I let them know about your feedback.
----------------------------------------