Assignments

CSCI 135 Online
Fundamentals of Computer Science I
Spring 2016

Computer Science & Software Engineering

Schedule | Assignments | Resources | Course syllabus

This page lists the programming assignments for the course and the due dates.

#	Due	Assignment
0	Mon 1/25	Hello World
1	Thu 2/4	Loops and Conditionals
2	Mon 2/15	Input and Arrays
3	Thu 2/25	Mars Lander
4	Mon 3/7	Audio Effects
5	Thu 3/17	Recursive Graphics
6	Mon 3/28	Staying Alive
7	Thu 4/7	Guitar Hero
8	Mon 4/18	Bombs Away
9	Thu 4/28	Gem Matching
10	Mon 5/9	Atomic Nature of Matter

Due

Assignment

Mon 1/25

Hello World

Thu 2/4

Loops and Conditionals

Mon 2/15

Thu 2/25

Mon 3/7

Thu 3/17

Mon 3/28

Thu 4/7

Mon 4/18

Thu 4/28

Mon 5/9

Atomic Nature of Matter

Submission. All assignments need to be submitted via email to the course instructor. You should attach all the source files that you were required to create or modify by the assignment (just the *.java files not the *.class files). You do NOT need to attach any source files that you did not need to change (this includes any of the Std*.java files). The top of every source file should include your name, email address, 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 (late = 12:00 AM the next day or later).
Allow plenty of time (tens of minutes) to be sure the email arrives at the TA's inbox before the deadline.
There is a penalty of 6 points per day (or partial day) late. Assignments (except for the final project) are each 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.

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.

Page last updated: January 13, 2016