CIS 226 Introduction to Java Programming

Assignments

YOU MUST FOLLOW THE CODING CONVENTIONS TO RECEIVE FULL CREDIT FOR THE ASSIGNMENTS! Please make sure you read and follow them before submitting your assignments.

Homework Standard

Source code formatting standard

You should use the standard Code Conventions for the Java(TM) Programming Language as your guidelines for formatting your code. If a specific data type or name was required from the homework specification, I would expect to see it. Otherwise, please use meaningful names for your variables and methods as suggested in the naming scheme guideline. All assignment source code files must start with the following JavaDoc comment lines:

/**
 * Program or Class Name
 *
 * Description of this program or class
 * ... more description ...
 *
 * @author (Your Name - Your student ID)
 * @version 1 (required only for homeworks with multiple versions)
 */

...Your code starts here...  

Java Naming Conventions

Effective Comments

Assignment 1
Assignment 2
Assignment 3
Assignment 4 and 5
Assignment 6
Assignment 7 and 8
Assignment 9

Check your grades here! (You must fill out the survey first)

Grading Criteria:

(For 100% of the maximum points for an assignment) Your homework will be graded on a sliding scale by a combination of computerized and human grading. I will look for Convention, check to see if it Compiled, then verify Correctness, then do Crash-proof testing, then read the print out for Code Layout and Style, Clarity and finally award the extra point to Elegant solutions. 

• (-100%) points - Using others' classmate works will result in negative points in the gradebook and possible F for the course. It's OK to discuss with others, to research for similar code snippets from the net, but not to copy the works of others and get all the credits for it.
• +40% points - Good effort but not correct results.
• +50% points - Compiled: The java complier will compile your code, if there are no syntax errors, you will get 50% points to start.
• +60% points - Compliance: Another computer program will scan through your code for defined standard file name(s), @author tag and the required JavaDoc header comments, and all requirements per specification. If you pass this point, the computer will give you 60% points.
• +70% points - Correctness: The computer will run your program through a batch of expected inputs or interfaces. If your program produces the expected outputs, you will get 70% of the total points.
• +80% points - Crash-proof: The computer will run your program through another batch of reasonable unexpected inputs or interfaces designed to flush out any logic errors you may have had. If your program survives intact, you will get another 10%.  A comprehensive test suite will be used against your code to find error-prone code segment and produce a report for you.
• +90% points - Code Layout and Style: A human evaluator now will start reading your printout after all the automated testing above and look for good indentation for all blocks; empty lines between section of codes, comments before every public methods and if everything looks nice and neat, you will get another 10%.
• +100% points - Clarity: To get the last 10% point, the evaluator should be able to read and understand your code intent easily. This is where effective comments and good naming scheme come in to play. A good program should be easily read and understood right from the first glance.
• +110% points - Elegance: In some rare case, people may submit unusual and extraordinary solutions for the problem. Make sure that you comment your code clearly to catch the evaluator's attention and describe your unique approach.

What this means is, if you use the most elegant algorithm but didn't submit the files in the right place, you would not even get past 50% points mark.

Remember, no late assignments will be accepted. Good Luck!

Home | Syllabus | Lectures | Assignments | Coding Conventions | Links