COP 1220
Programming in C
Summer 2001

1. Variables, relational expressions and assignments.
2. Assignment operators.
3. Control statements, including branching loops.
4. Character and arithmetic data types.
5. Arrays, strings, and functions using pointers.
6. Recursion.
7. Input/output and related functions."

A=90-100,   B=80-89,   C=70-79,   D=60-69,   F=0-59
(Or you can elect to "audit" the class during the add/drop period.)

• No make up exams will be offered without the prior approval of the instructor. 
• While the exams are non-cumulative, each does build upon knowledge acquired earlier.  Exams are based upon material presented in class and are not taken from the text.
• Regular attendance is imperative for the successful completion of this class.  All phones, pagers, and beepers must be turned off during class time, except with prior permission of the instructor.  No food or drink is permitted in HCC classrooms.  Attendance will be taken within 5 minutes of the start of class; after 6 absences and/or lateness, the student will lose 2 points off the final grade for each occurrence.
• Credit for class participation includes attendance, preparedness, and adding to class discussions by asking questions and participating in discussions.  Playing computer games, surfing the internet, or working on other assignments for this or other classes during class time will lose you credit.
• Additional time outside of class will be required to complete the material.  For typical students an average of between 6 to 12 hours each week outside of class are required for preparation, practice, and projects.

• Students are expected to prepare for each class by completing all reading assignments, reviewing examples and model solutions provided, and practicing programming outside of class.  This is important---you can't learn a skill such as C programming only by attending class and reading books.  You must practice several hours for a few days each week!  If you won't have enough time available, consider auditing the course.
• A project is late if not turned in by the start of class on the day it is due.  Late projects will be accepted up to one week late only if you obtain the instructor's permission at least one week prior to the due date of the project, or for a documented serious medical reason.  All late projects will lose at least one letter grade penalty regardless of the reason for the delay.  Projects later than one week will receive a grade of F (0).

• Working together on individual assignments is considered cheating!  Cheating will result in an automatic F (zero) for the project for all parties.  Note that some projects may be group projects, where each member of a small group works together on a project.  It is also ok to ask a fellow student for class notes (in the event you miss a class) or for help in understanding the text or material given to the class (e.g., example programs on the class website).

• You must follow the academic honesty policy for HCC.  A second cheating offence will result in an "F" for the course, and your name will be turned over to the Dean for further handling.  I take these matters very seriously.  You have been warned!
  

Projects are graded according to their design (25%), how well they compile and run (20%), how well your project meets the requirements specifications (20%), the coding style (15%), the amount (and quality) of your comments (10%), and your creativity in extending the project usefully, or an innovative design that uses the features taught in class well, etc. (10%).  Further details will be provided in class.