Computer Science 314 - Summer 2012
Assignment Guidelines


Release Date Due Date Topic
1 Wednesday, June 27 Friday, July 13 Code camp, warm up assignment. (Individual Assignment)
2 Tuesday, July 10 Tuesday, July 17 Creating a stand alone class - Mathematical Matrices (Individual Assignment)
3 Friday, July 13 Friday, July 20 Implementing a program with multiple classes, using ArrayLists - The Name Surfer (Individual Assignment)
4 Tuesday, July 17 Tuesday, July 24 Using Data Structures - Evil Hangman (Pair Assignment)
5 Friday, July 20 Friday, July 27 Linked lists (Individual Assignment)
6 Tuesday, July 24 Tuesday, July 31 Recursion (Pair Assignment)
7 Friday, July 27 Friday, August 3 Using lists, creating data structures - Implementing a Set class (Pair Assignment)
8 Tuesday, July 31 Tuesday, August 7 Binary Search Trees (Individual Assignment)
9 Friday, August 3 Friday, August 10 Huffman Coding (Pair Assignment) No slip days may be used on assignment 9.
EC Tuesday, August 7 Tuesday, August 14 Graph Algorithms (Individual Assignment)  Extra Credit Assignment due by 1 pm. No slip days may be used on the extra credit assignment.

General assignment requirements.

Programming Assignments: Individual assignments are to be completed by you alone. You may not share code with other students or other programmers. Review the class policy on improper collaboration from the class syllabus and how this applies to individual assignments.

About one quarter of the assignments may be done in pairs using a technique called pair programming (Read the paper on pair programming to understand how the technique works.). Turn in one solution  for the pair. (Submit the assignment to one partners turnin account.) Once you start working with a partner on an assignment you may not switch partners. If you do not wish to work with a partner after starting on an assignment you must both complete it individually. You must inform your TA(s) via email if you start working on an assignment with another person and decide to finish as individuals. You may not re-pair after starting the assignment with someone else. When working on pair programming assignments you are expected to spend at least 80% of your time on the assignment working with your partner, together at one computer, taking terms typing, and navigating.

Programs will be written in Java, using the Java 2 Platform Standard Edition 7.0. See the software page for information on downloading and installing Java at home.

Assignments are due by 11pm on the due date except the extra credit assignment which is due by 1 pm.

You have 6 free late (slip) days in 1 day units (1 second  to 24 hours = 1 day) for the semester.

Unless prohibited, you may use any component of the language or standard library (The Java API).

Assignments must compile and run with Eclipse in the Painter Microlab.

Assignments will either be submitted as a single Java file or  in the form of a single JAR (Java Archive) file. Each assignment will specify exactly what to turn in. Assignments that are not in the correct format or not named correctly will be penalized as described below.

Assignments must be turned in via the Microlab turnin program. If you are registered for more than one computer science class you must ensure that your turn your assignment in to the correct, CS314 directory. You must turn in a file with the correct name and in the proper format. (The source code if I ask for the .java file or the source code files packaged as a jar file. The format will be specified on the assignment page.)

If you do not follow the instructions and specifications for assignments (name, where to turn in, jar file format) you cause extra work for the graders and myself. As a student and potential software developer you must follow instructions and specifications. When you are penalized for failure to follow instructions it causes you to become a special case. With over 50 students and a very shoirt amount of time available to us, the TAs and undergrad proctors use scripts to streamline some aspects of grading. Failure to follow the assignment instructions and specifications causes these scripts to fail and the graders must spend more time on your submission. The following penalties are in place because there must be consequences for failure to follow instructions. Otherwise there is no deterrent. Please read this account of a student who has seen the issue from both sides.

Penalties for failure to follow instructions and specifications on assignments:

Assignments grades are not scaled to effort or time spent working on them. (You may spend a large amount of time working on an assignment and still lose many points because your program is not correct.) The programs are not graded on a strictly linear scale. Points will be deducted for failed test cases, poor style, poor efficiency, lack of necessary comments, convoluted algorithms, lack of student provided test cases, lack of answers to questions regarding the assignment, and other reasons deemed appropriate by the instructor.

Each assignment will specify whether it must be done individually or as a pair.

Assignments will be checked for plagiarism and copying using Moss. You may discuss high level design issues with your fellow students, but sharing algorithms or code or obtaining solutions from another source constitutes academic dishonesty and will result in an F for the course. Review the class policy on cheating.

The teaching staff will grade, comment, return, and post the grade for an assignment within 2 days. A grade can only be disputed within the following week. (This isn't a weekend bazaar. If there is an error in your grade you have one week to contact your grader. We won't go back at the end of the term to look at an assignment from early in the term.) You are responsible for contacting your TA or proctor if you assignment is not graded in a timely and accurate fashion.

All grade disputes must be made in writing by email to the TA with supporting evidence or arguments, and will result in the entire assignment being re-graded. Remember, no whining.


Assignments will be checked for correctness with more tests generated by the instructional  staff. Your assignment may pass all the provided tests and still be incorrect. Grading test cases will not be published. If you would like to see the test specific test cases your code failed on you must meet with your TA during their office hours to see the test cases.

Design, Style, and Documentation

Efficiency: Worry about this last, but your program should run as fast as possible and use as little memory as possible within the constraints of the assignment.

To the CS 314 home page