Computer Science 314 - Summer 2014
Assignment Guidelines

 

Assignment
Number
Release Date Due Date Topic
1 Wednesday, May 28 Thursday, June 12, 11pm Code camp, warm up assignment. (Individual Assignment)
2 Wednesday, June 11 Thursday, June 19, 11pm Creating a stand alone class - Mathematical Matrices (Individual Assignment)
3 Wednesday, June 18 Thursday, June 26, 11pm Implementing a program with multiple classes, using ArrayLists - The Name Surfer (Individual Assignment)
THERE IS NO ASSIGNMENT NUMBER 4 - SKIPPED TO MAINTAIN CONSISTENCY OF ASSIGNMENT NUMBERING
5 Wednesday, June 25 Thursday, July 3, 11pm Using Data Structures - Evil Hangman (Individual Assignment)
6 Wednesday, July 2 Monday, July 14, 11pm Linked lists (Individual Assignment)
7 Wednesday, July 9 Thursday, July 17, 11pm Recursion (Pair Assignment)
8 Wednesday, July 16 Thursday, July 24, 11pm More recursion, Anagram Solver (Individual Assignment)
9 Wednesday, July 23 Thursday, July 31, 11pm Using lists, creating data structures - Implementing a Set class (Pair Assignment)
10 Wednesday, July 30 Thursday, August 7, 11pm Binary Search Trees (Individual Assignment)
11 Wednesday, August 6 Thursday, August 14, 11pm Huffman Coding (Pair Assignment)  No slip days may be used on assignment 11.
12 - Extra Credit Monday, August 10 Sunday, August 17, 11 pm Graph Algorithms (Individual Assignment) No slip days may be used on assignment 12.

General assignment requirements.

Programming Assignments: Individual assignments are to be completed on your own. You may not share solution code or experiment 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 third 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. You may NOT start working on on your own and then start working with another person. 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.

If you are retaking CS314 you must start from scratch on assignments unless you worked alone on the assignment in previous semesters and are working alone this semester. You may not reuse code from a partner from previous semesters and you may not use code you created in a previous semester with a partner this semester.

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

Note, you code must compile using Java 6. On the Eclipse IDE set your compiler level to 6.0. You may not use features of Java 7.0 (notably type inference with the diamond operator) or 8.0,. Doing so may result in a grade of 0 due to compiler errors.

Assignments are due by 11pm on the due date.,

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

Unless prohibited by the assignment handout, you may use any component of the language or standard library up to Java level 6.0. (The Java API).

Assignments must compile and run with Eclipse in the GDC Microlab set to compiler level 6.0.

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 if I ask for that. 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 fail to follow instructions it causes you to become a special case. With many students and a very short 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. 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 are 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 6 days. A grade can only be disputed within the following 5 days. (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. After the 5 day time limit scores will not be altered.

All grade disputes must be made in writing by email to the grader with supporting evidence or arguments within 5 days of grades being posted. A regrade will result in the entire assignment being re-graded and the score could be lower than the original score.

.I welcome feedback and comments about the course and assignments, and we will correct legitimate grading errors that are identified in a timely fashion, but whining is counter-productive and will only irritate myself and the TAs.


Testing:

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, Program Hygiene, 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. Some tests will be based on the length of time it takes your solution to complete and you may fail a test if your solution takes too long.

To the CS 314 home page