CMPSC 311, Projects, Spring 2013

---

Project 1, posted Jan. 7, due Jan. 16.  Grading info.
Project 2, posted Jan. 18, due Jan. 28.  Grading info.
Project 3, posted Jan. 30, due Feb. 8.   Grading info.
Project 4, posted Feb. 11, due Feb. 22.  Grading info.
Project 5, posted Feb. 25, due Mar. 13.  Grading info.
Project 6, posted Mar. 12, due Mar. 22/25.  To be discussed in class, Mar. 13, 15, 18.  Grading info (see grade sheet attached to project report).
Project 7, posted Mar. 25, due Apr. 9/10.  This is a project for two people.  Grading info (see grade sheet attached to project report).
    The current partners list, if you need to find someone to work with.
Project 8, posted Apr. 11, due Apr. 24.  This is a project for two people.  Grading info.
    The current partners list, if you need to find someone to work with.

Solutions will be posted on ANGEL several days after the due date.

---

Notes for the projects --

• It is important that you write programs that are easily understood by another person.  Correct programs should be obviously correct.  Testing will help confirm correctness, but that's not the whole story.  If a knowledgeable person cannot read your program and immediately see that it is correct, then it isn't well written, and you should try to improve it.  You can expect points to be deducted for "bad program", even if it passes the tests.
  
• It is important that your programs compile without errors.  The testing will be automated as much as possible, and there are too many people in the class for the grader to spend time fixing your program.  Ask for help from the TA or instructor before the project is due.
  
• In general, grades will be split among three parts:
• "the program is readable and well-written"
  
• "the program compiles without errors (even better, without warnings)"
• "the program runs, terminates cleanly, and produces correct output"
• Depending on the assignment, we may require output in a specific format.  If so, there will be examples.

---

Last modified 6 May 2013