600.120 Assignment Index

Here are some general guidelines that apply to all assignments unless otherwise noted:

• Readings: Make sure you do the reading for each week, preferably before lectures and attempting homework.
• Compilation for C programs must be done with these options: gcc -ansi -std=c99 -pedantic -Wall -Wextra -O
• Style: All files with main must be named according to the assignment number they solve, such as pg1.c or pg5.cpp. Other files should be named descriptively. Use a consistent layout style for your programs, as well as recommended naming practices for variables and functions. For C programs, we suggest following Kernighan & Ritchie's style.
• Submission: Upload all source files (no object/executable files) for a particular assignment part to that webCT assignment page. Make sure that you hit SUBMIT after uploading. You can retrieve and resubmit as many times as you want before the deadline. If you retrieve, it's as if you never submitted, so make sure you have time to resubmit! If you need to explain anything in general, include a README plain text file with your submission. Anything not on webCT by the deadline gets a 0 = no credit. Also bring a printout of your source code to class on the due date. Make sure that your name and JHED are in a comment at the start of each file. Also staple and/or clip together all the pages for each file and submission.
• Ethics: Assignments will be individual unless otherwise noted. Remember that you may use or adapt code from your texts and lectures, but you MUST include a comment to cite the original source. You may not use code from other sources.
• Help: check the TA info course webpage for hours when help will be available in the CS lab. This may be updated throughout the semester to note any weekly changes.

Here are your actual assignments. Forbidden links mean the files are not yet ready for public consumption. Due dates are subject to change until the actual assignment is posted.

• Assignment 1 -- due Tuesday, 2/9 -- sample run with an extra feature added -- solution
• Assignment 2 -- due Thursday, 2/18
• Assignment 3 -- due Thursday, 2/25 -- sample input
• Assignment 4 -- due Wednesday, 3/3 & Tuesday 3/9 -- partner evalution

MIDTERM on THURSDAY, 3/11

SPRING BREAK

• Assignment 5 -- due Thursday, 4/1
• Assignment 6 -- due Tuesday, 4/13
• Assignment 7 -- due Thursday, 4/22 -- driver program -- partner evalution
• Final Project -- due Thursdays 4/29 & 5/6
• Team Evaluation -- due Friday 5/7

NOTE: Your final has been rescheduled for 9am on Tuesday, 5/11, in Shaffer 301. The review session will be Sunday, 5/9, 7pm in Shaffer 303 (not our regular classroom).