10nov15

Reasons for the above requirements
----------------------------------

Here are the principles from which the above requirements follow, and on
which basis the requirements can be ammended and or relaxed on request.

- 1. Several people need to see your project presentation.  
   If something goes wrong with your software, we will go to the next
   presenter and you may have to give a private demo later. 

- 2. I need to have some recompilable version of your source code. 
     If it's in Unix, then this must compile on the grafixLab macs or pcs. 
     If your code compiles only in Windows, then I need a copy of the 
     code and instructions for recompiling it. 
     If it is in Javascript, then the  .html has to run on Firefox from  
     every platform (windows, mac, linux).

- 3. An (even minimally) documented collection of your work could be of 
     immense value to some future MA198/CS1988 student (and to me). 
     So please, no false modesty here. Remember "content trumps format".

- 4. A LaTeX document always looks good, and makes fine printouts. But 
     if you're running short of time, and your .html files already have 
     all the information, then may just print out the .html files and 
     submit them as hard copy here. But you should still follow the 
     instructions in the two "Sampledoc" links.
     If you've learned to use the Pudding, then you could
     edit your .tex code into the .html file and your formulas will look 
     really professional.

- 5. The hand annotated printout of your project is invaluable if I or
     some future student needs to understand your code. Please don't
     waste time to prettify your code. The hand annotation is much more 
     valuable. And MA198/CS199 is not a CS course. You will never be criticized
     for writing ugly code, just if you write ugly math.

- 5b. The hand annotation transcribes mathematical formulas into the 
     customary mathematical format. Do not "mix-and-match". In math we
     use the * for purposes other that multiplication, and variables have
     single letters, in various fonts, and possibly with subscript. You are
     de-constructing the original tranlation of math into whatever computer
     language before you. 

- 5c. If a section of code produces a picture or animation, sketch the figure
     with your pencil and possibly annotate the this picture properly to 
     correspond to the formulas. The idea is simply to shorten the time and 
     effort of unravelling what you're trying to encode.

- 6. See the three cover sheets. If you want feedback on your project 
     documentation, with an opportunity to make corrections, then you write
     "Draft" at the top of the cover sheet. But the cover sheet must be 
     attached, and the document must be submitted by F14, no exceptions.  

- 7. Finally, a word about grades. You have contracted for a product,
    namely your project with all of its parts. Satisfactory completion 
    of the project with all of its parts  merits the contracted A. 
    If some or all of your project is really superior, you'll get an A+, 
    which shows up on your transcript but doesn't count more than an A in 
    your GPA. If you fall short in one or another aspect of the project, 
     but it is materially finished, then you'll get an A-. 
     In all other cases, you have an "incomplete". In that case, see (8).

- 8. In "real-life", delays in project completions, and extensions are very 
     common. The University does not believe in this fact of life. 
     So, my policy is to give a grade commensurate with what you have 
     accomplished in this course, usually some kind of B. This grade, whenever 
    you have finished your project and submitted it in the form contracted,
    can be updgraded to an A- or A.