Assignments

CSCI 135
Fundamentals of Computer Science I
Fall 2016

This page lists the programming assignments for the course. When an assignment is released, the assignment column will link to a detailed description of the assignment.

#	Due	Assignment	Collaboration
0	Thurs. 9/1	Hello New World	Individual
1	Thurs. 9/8	Conditionals	Individual
2	Thurs. 9/15	Basic I/O	Individual
3	Sat. 9/24	Iteration - Mars Lander	Individual
4	Thurs. 10/13	Arrays	Individual
5	Thurs. 10/20	Methods - Audio Effects	Individual
6	Thurs 10/27	Classes - Staying Alive	Pair
7	Thurs 11/10	Object Oriented Design - Wumpus World: Part 1	Pair
8	Wed. 11/30	Wumpus World: Part 2	Pair

Due

Assignment

Collaboration

Thurs. 9/1

Hello New World

Individual

Thurs. 9/8

Conditionals

Individual

Thurs. 9/15

Basic I/O

Individual

Sat. 9/24

Iteration - Mars Lander

Individual

Thurs. 10/13

Arrays

Individual

Thurs. 10/20

Methods - Audio Effects

Individual

Thurs 10/27

Classes - Staying Alive

Pair

Thurs 11/10

Object Oriented Design - Wumpus World: Part 1

Pair

Wed. 11/30

Wumpus World: Part 2

Pair

Submission. All assignments need to be submitted via Moodle. In the event of a Moodle failure, email your submission to me before the deadline. You should upload all the source files required by the assignment. You should also include any other source files which your programs depend on (things not in the standard Java library or Princeton's Std*.class files). The top of every source file should include your name, username, and a description of what the class does.

Deadline and late policy:

All assignments are due at 11:59PM on the stated date. Assignments arriving after 11:59PM are late (12:00 AM the next day or later).
Allow plenty of time to upload files, sometimes Moodle is slow.
There is a penalty of 6 points per day (or partial day) late. Assignments are worth 30 points, so that is a 20% penalty per day.
- For example, if an assignment is due on Tuesday at 11:59PM, you must turn it in by Wednesday at 11:59PM to only accumulate 6 late points.
Your first 24 late points are automatically waived. No additional late points will be waived without a valid, documented, official university excuse.
Assignments submitted more than 4 days late will not be graded. You will receive a zero but no late points will be used.
On designated pair assignments, both partners are assessed late points according to the number of days the assignment was submitted late.
- For example, if an assignment is due on Tuesday at 11:59PM and the pair turns it in by Wednesday at 11:59PM, each partner would accumulate 6 late points.

Grading. Your code will be graded on correctness, programming style (including comments), and efficiency. Partial credit is possible so if you run out of time, submit what you have. If you want to do well, start well in advance of the deadline. This allows time to seek help if you run into trouble. Software bugs can be difficult to find and are often easily found after a good night's sleep.

Collaboration policy. Programming is a creative process and no two programmers will solve the same problem in the same way. You are encouraged to discuss how to design a solution to a given problem with your classmates. But when it comes time to convert your design into code, you must write the code yourself. Be sure not to leave copies of your code where others might be able to access it (such as in the recycling bin of a lab computer). You may adapt code from the CSCI 135 course materials provided you cite what code you used in your program's comments.

Under no circumstances should you copy another person's code. Copying code from another student can result in an F in the course. Novices often mistakenly believe simple transformations can disguise a copied program. In actuality, copied programs often reveal themselves quite easily during grading. We can also use sophisticated software such as MOSS to detect plagiarized code.

Pair programming. For designated assignments, you are encouraged (but not required) to pair program with another student in the class. In pair programming, both people work side-by-side at the computer on the same program. One person is the driver who actively types at the computer or records a design. The other person is the navigator who watches the work of the driver, identifies problems, asks clarifying questions, and makes suggestions. About every half-an-hour, the pair should switch roles. Before starting pair programming, you should watch this video. A pair should submit one solution with both partner's names and usernames in the header of the submitted files.

Page last updated: November 10, 2016