Duke CS Logo CompSci 100e: Program Design & Analysis II
(Spring 2011)
Home (Forbes)
Home (Rodger)
Course Information
Calendar
Resources
Assignments
Prestidigitation
Markovian Text Generation
Written: Analysis
Percolation
Written: Lists & Trees
Boggle
Huffman Coding
EC: Contest Problems
EC: Tic-Tac-Toe
APT problems
Lab
Discussion Forum
Help Sessions
Java Help
Blackboard

Programming Assignment Schedule

Assignment Due Date
Introductory Compci 100e Survey January 21
Natural Prestidigitation February 8
Markov Text Generation February 17
Test on February 23
Written: Analysis March 3
Percolation March 25
Written: Linked Lists and Binary Trees March 31
Boggle April 7
Test on April 15
Huffman Coding April 21
Extra Credit Tic-Tac-Toe April 27
Extra Credit Contest Problems April 27

Starter Code

Most assignments will include code to get you started. This may consist of completed classes that you will utilize but not modify or classes in which some methods have been completed and others are left for you to fill in. In either case, comments will clearly indicate which sections of the code you may edit and which must not be modified (you can go to these sections directly by using the Tasks view within Eclipse). All starter code may be obtained with the Ambient download tool by following the directions here. The download site for the course is

http://www.cs.duke.edu/courses/cps100e/spring11/snarf/

Assignment Submission

All assignments must be turned in on the due date given. If your assignment is received the next day, it is considered late. You are responsible for ensuring that all files are turned in on time, if a program is turned in late there is a penalty detailed on the course information page.

When you are done with your project and are confident it is satisfactory, you should submit it electronically using the directions available here. You may submit an assignment as many times as necessary, but only the files included in the last submission will be graded. Thus, you should always submit all your project's files -- even if they have not changed since a previous submission. Note, the official time of submission for your project will be the time of your last submission. An assignment will be considered late if any submission is late, even if your first submission is on time. You may lose points on your assignment if your final submission is incomplete or late.

README Guidelines

Every assignment submission must include a plain text file, named README.txt (please use all capital letters in naming the file), that includes the following information:

  • Your name and NetID
  • Hours Spent: Give the date you started the assignment, the date you completed the assignment, and an estimate of the number of hours you worked on it
  • Consulted with: A list of the students, TAs, and professors with whom you consulted on the assignment. Since assignments are to be your own work, you should keep track of anyone with whom you have had a significant conversation about a program. You are welcome to talk with the course staff about the assignment, and to other students about broad ideas and concepts. If you did not consult with anyone, you must explicitly state that fact.
  • Resources used: Note any books, papers, or online resources that you used in developing your solution. If you did not use any outside resources, you must explicitly state that.
  • Answers to questions: There may also be specific questions given in the assignment whose answers you will be asked include in this file
  • Impressions: You may include your impressions of the assignment to help the course staff improve it in the future.

Failure to provide this file with this information will result in rejection of the assignment as complete. You may be able to resubmit. .

Within Eclipse, you can create plain text file by choosing File → New → Untitled Text File.

Code Style

Finally, note that a significant portion of your assignment grade is based on the readability of your program. This readability grade includes style, comments, and the naming of variables and methods.

You must include a comment at the top of each source file you modify that includes your name, course and purpose of the class specified. For example:

// Name: Susie Student (ss1)
// Course: CompSci 100e
// Purpose: This class has the following uses
//          ...
Last updated Wed Apr 13 14:46:05 EDT 2011