Homework Policy

Homework Policy for CSCI 564

Special Note for hw3

Include concrete proofs in form of graphs, tables, nsl result screen captures, etc. to support your answer, reasoning, claim, etc. to the questions. Lack of proof may give you no credit at all.
Submit all *.mod and readme files if any. You do not need to submit Makefile. Do not submit *.java, *.nlx, *.class and *.tmp files.
In this assignment written part is based on working code. If your code does not work, then document your trial and error with printouts and analytical reasoning associated with them, and try answering the problems.
You must online-submit your code of part c regardless of its working status. If not, you will not get any credit at all.
Please use hw3 (no space; three characters) as the tag when you submit the code.

Submit Policy for the Homework

There will be written part and code for each homework. (Off-line documentation for code is written part.)
On-campus students should submit the written part at the beginning of the class when the homework is due.
Off-campus(DEN) students should submit the written part to DEN according to DEN policy before the class when the homework is due. (Please consult DEN for detail.)
Code must be submitted online to csci 564 account in ISD.

At aludra unix prompt in your account:

aludra>> submit -user csci564 -tag hwx hwx.mod hwx.mod readme ...

Type exactly as it appears for normal fonted word, and substitute italic fonted words with appropriate name and files for each homework.
Only hw0, hw1, hw2, and hw3 are allowed for tag hwx above.

For each homework there may be more specific guideline.

Grading

Each homework section and problem will come with its own points toward the total 10 points per assignment.
You may receive minimal credit (upto the grader) for written part with incomplete, uncompilable, code if you show efforts, and well document your effort.
You may earn upto 60% of credit towards your written part with completed code with smart documentation even if it does not behave correctly.
You may earn 90% of credit towards your written part if code works perfect. You may earn the remaining 10% with minimum documentation.
Written part must be typed to be clearly legible. Your grade will be jeopardized for bad hand-writing or fax quality. No exception.
Take a look at Implementation section below for more detail about documentation.

Implementation

All the implementation or code must be compilable and runnable at your aludra or nunki account.
No exception.
Full off-line documentation must link the theory or concept with the high-level design of code! For example,

Modularize the theory or concept of the assignment to come up with high-level design or implementation
Make code per module.
Explain your modularization and implementation per file, object, and module.
Show that you have given analytical thought to the problem.
It must be easy to read, concise, well formatted, and overall pleasing to the grader.

Minimum documentation must define what the code is about so that when you review your code ten years later, you may understand what you did. It may be online documentation.

Late Policy for the Homework

Maximum potential for an assignment is 10 points for on-time submission.
Being late by x days will reduce it by x.
For example, if you submit late by 2 days, the maximum potential will be 8 points.
DEN time-stamps DEN students' written part. The grader may consider it as the submission time.