CS1005 - A Term, 1994
Introduction to Programming in C
Lectures: AK-116, MTTF 10:00 - 11:00
Labs: FL-B11, Wednesday at various times
Instructor: Prof. Matthew Ward, FL-134, 831-5671, matt@cs
Office Hours: Monday and Thursday: 11AM, Tuesday and Friday: 1:30PM, Others by appointment

Teaching Assistants:
Pete Bastien, FL-145, 831-5118, ptbast@cs, Office hours M9, T11, W6, Th7, F12:30
Chris Bentley, FL-140, 831-5004, chrisb@cs, Office hours M12:30, T12:30, W7, Th12:30, F9
Ming He, FL-239, 831-5005, mhe@cs, Office hours M1:30, M7, T2:30, Th1:30, F2:30
Course Objectives:

Upon completion of this course, the student should possess a good understanding of structured computer programming in general, and should be moderately fluent in the syntax and semantics of a significant portion of the C programming language. Students desiring an exposure to more advanced topics in C programming are encouraged to take CS2005 after this course.

Course Description:

Programming Assignments: Four programming assignments will be given. Assignments are due by noon on the dates specified; late assignments will incur a 10%loss of points per day (not including Sunday) unless prior permission has been granted. Permission for late assignments must be obtained at least one day prior to the due date, with a very good excuse! Students are strongly encouraged to get an early start on programming assignments to help avoid last-minute crunches and problems. Programs should be well documented, with comments at the beginning stating your name, the function of the program, and how it should be executed. Major variables, computations, and routines must also be commented. Significant points will be lost for poorly documented programs. Source code and sample input/output should be submitted electronically via the turnin utility (instructions will be provided in lab).

Exams: There will be 3 exams given. All exams are closed book, closed notes. If you cannot be present for one of the exams, please see me (with a very good reason) at least 2 days prior to the exam. Oversleeping on the day of an exam is NOT an acceptable excuse. I do not give make-up exams.

Laboratories: Laboratories will be held each Wednesday (except for the last week) in FL B11. Attendance at these sessions is required, as part of your grade will be based on performance in the laboratory programming problems. There are no make-up laboratories. Please attend the same laboratory session throughout the term, as different assignments may be used in each distinct session. If you wish to permanently change the session to which you are assigned, please discuss it with your TA prior to the change.

Grading Policy: Course grade will be based on a total of 200 points; the four programming assignments will account for a maximum of 15, 25, 35, and 25 points, respectively, the three exams will contribute a maximum of 20, 20, and 35 points respectively, and each of five laboratory exercises will be worth at most 5 points. In order to pass the course you must have a passing average for the programming assignments AND a passing average for the combined exams and laboratories.

Textbook: The primary textbook is Problem Solving and Programming Design in C - Hanly, Koffman, and Friedman. Please do the reading assignments. Studies have shown that your understanding of the material will be greatly enhanced if you both attend classes and read the associated text.

I have also placed several other books on C Programming on reserve in the library to assist students who are still fuzzy on a particular topic after attending class and reading their text book.

Facilities:

DecStations are available FL-B11, CCC, and other labs across the campus. Hours of availability differ. Programs may be developed on PCs; however, the assignments must be turned in and fully functional on the workstations. If you are doing the coursework on a PC and you need help from me or the TAs with your program, please transfer the program to the workstation environment (and try compiling it there) before coming to us, as this makes it easier for us to examine your code and insures that the problem is not with your PC.

Getting Help:

If you are having difficulty understanding a concept, designing your program, or finding a bug, do not hesitate in contacting either me or the TAs (this is why we have office hours!). If the problem occurs at an odd hour or you cannot get to one of our office hours, the next best solution is to send electronic mail to us. This can be done individually at the addresses above. We each check our e-mail several times a day, so chances are you would get a response fairly quickly. For help using electronic mail, check the CCC Handbook or see one of us. You should try to read your e-mail every day, as we will broadcast useful information on a regular basis to the class.

Cheating:

Academic Dishonesty, as stated in the student handbook, is a ``willful act that interferes with the process of evaluation by misrepresentation of the relation between the work being evaluated (or the resulting evaluation) and the student's actual state of knowledge.'' Thus, copying someone else's code (or exam), sneaking notes into an exam, or getting someone else to write all or a significant part of your code each constitute cheating. This does not mean that you cannot ask a fellow student a question regarding such things as understanding the assignment, a particular C language construct, or an error message you are receiving. Just make sure that what you hand in is your work alone. Any student found guilty of academic dishonesty will receive a 0 grade for the particular assignment or exam and the CS department head will be notified. A second incident will result in a failing grade for the course and other actions (which may lead to expulsion) as specified in the student handbook. Bottom line? Don't cheat - if you are having troubles, come see me or one of the TAs.

• About this document ...