Computer Science 333:
Thanks for all the hard work that went into demos, which were really nicely done. For the last part, here is some information on project submission for Dean's Date. Read this for details on what to submit and how.
Lecture notes: 2/1 2/3 2/8 2/10 2/17 2/22 2/24 3/1-3 3/8 3/10 3/22-24 3/29 3/31 4/5 4/7 4/21 4/28
Assignments:   1 2 3 4 5
Project: Preliminary project info Project info 2/15 previous projects comments from reports design document format MySQL hints TA-project group assignments info on weekly meetings CVS help more CVS help 4/22 demo information last-minute demo suggestions
Reading: language tutorials general bibliography Ousterhout on scripting languages
Old stuff: playlist survey ed to grep assignment Java crash course language popularity assignment 3 ratios LDAP authentication using PHP Newsgroup
Dates: All dates are subject to minor changes.
S M Tu W Th F S Feb 1 2 3 4 5 first class 6 7 8 9 10 11 12 assignment 1 due; preliminary project info 13 14 15 16 17 18 19 assignment 2 due 20 21 22 23 24 25 26 assignment 3 due 27 28 Mar 1 2 3 4 5 assignment 4 due; project meetings 6 7 8 9 10 11 12 assignment 5 due; project proposal due 13 14 15 16 17 18 19 spring break 20 21 22 23 24 25 26 detailed project plan due; first TA meeting 27 28 29 30 31 Apr 1 2 small-group design reviews 3 4 5 6 7 8 9 project prototype 10 11 12 13 14 15 16 17 18 19 20 21 22 23 alpha test 24 25 26 27 28 29 30 last class; beta test May 1 2 3 4 5 6 7 project demos 8 9 10 11 12 13 14 Dean's date; project due 15 16 17 18 19 20 21
This is a course about the practice of programming, an attempt to expose students to the development of real programs. Programming is more than just writing code. Programmers must also assess tradeoffs, choose among design alternatives, debug and test, improve performance, and maintain software written by themselves and others. At the same time, they must be concerned with compatibility, robustness, and reliability, while meeting specifications. Students will have the opportunity to develop these skills by working on their own code and in group projects.
COS 333 is about programming, not about a specific language. The course will assume that you are familiar with C, and will include excursions into C++, Java, and Visual Basic, and scripting languages like shells, Awk, Perl, and Tcl. There will be significant emphasis on tools, both how to use them and how they are designed and built. The course will use Unix and Linux more than Windows, but not exclusively. Students must be comfortable with C programming and Unix, and able to write modest-sized programs that work. COS 217 is a prerequisite.
This is meant to be more than a laundry list, however. Each section will also discuss issues of design, implementation, testing, performance, portability, and other software engineering concerns, and these will also be part of the programming assignments. With luck there will be a few guest lecturers as well.
There will be two lectures each week. During the first half of the semester, there will be a modest-sized programming assignment each week, which should take perhaps 5 hours to complete. During the second half of the semester, students will work in groups of 3 or 4 on a project that will involve a significant amount of design and implementation.
There is one required text: The Practice of Programming, by Kernighan and Pike; you should also know basic Unix tools and usage as described in, for example, The Unix Programming Environment. Other readings will be handed out in class or found on the Web. The books listed in this bibliography are also worth looking at; they cover a wide variety of material related to programming.
Tuesday and Thursday 11:00-12:20, Friend 004.
Brian Kernighan, 311 CS Building, 609-258-2089, bwk at cs.princeton.edu. I will set up regular office hours once things get rolling; alternatively, make an appointment, or just drop in if my door is open, which it usually is.
Chris DeCoro, 103B CS 258-0944, cdecoro, Tue&Thu 2:00-3:00
Aquinas Hobor, 214 CS, 258-1793, aahobor, Mon&Wed 2:00-3:00
Five programming assigments will be assigned during the first half of the term; each is intended to take about five hours, but is sure to take longer unless you are careful.
Assignments are together worth about 30 percent of the course grade. Assignments are due by midnight on Thursdays unless there are extraordinary circumstances. For the record, extracurricular activities and heavy workloads in other classes don't count as "extraordinary", no matter how unexpected or important or time-consuming. You must complete all assignments and project requirements to pass the course.
The project will have frequent checkpoints along the way for which you will have to present status reports, preliminary designs, and the like. There will be a public presentation and demo at the end, a written writeup, and submission of a system for testing and evaluation. All of these are graded.
The project will be worth about 60 percent of the course grade; it will be shared equally among group members, with the possibility of negative adjustments for members who fail to contribute their fair share.
Regular class attendance is expected and class participation helps; frequent absences are grounds for a failing grade regardless of other performance. This means you.
Do not, under any circumstances, copy another person's program for an assignment. Writing code for use by another or using another's code in any form violates the University's academic regulations.
Examples of unacceptable behavior for assignments include:
The program you turn in must be your work. You may get help from the instructor or TA after you have started writing code, but not from other students. Computer science assignments are not like physics or math problem sets: there is no single right answer. Each student is expected to come up with his or her own individual solution.
If you plan to do something that you are not absolutely sure is legal, ask first. Ignorance of this policy will not be accepted as an excuse for your actions.
You are responsible for ensuring that your files are not readable by your classmates. We recommend doing your COS 333 work on your own machine or in a private subdirectory, i.e.:
% mkdir cos333 % chmod 700 cos333
Project groups are encouraged to share insights and information about how things work, how to get things done, and other aspects of programming knowledge.