Assignments that do not meet the program specifications EXACTLY will not be graded!
Any assignments that are returned to students because they do not meet the assignment specifications will be penalized with late points.

Assignment results will be assessed visually. I am not looking for any specific file output.

1 point per day (max of 5 points) will be deducted from late assignments.

The deadline for turning in all assignments is December 13. I cannot guarantee that anything turned in after this date will be graded.

You will be given a grade of 0 if an assignment is not turned in by this date.

The programming assignments should be submitted on the class Bb Learn page before 11:59 PM on the due date.

• Assignment 1 (Draw clipped lines) - Due October 13
  
• Assignment 2 (Sutherland-Hodgman polygon clipping) - Due October 27
  
• Assignment 3 (Draw clipped, filled polygons) - Due November 10
  
• Assignment 4 (Draw 3D lines) - Due November 26
  
• Assignment 5 (Z-buffer rendering) - Due December 8
  
• Extra Credit Assignment (Bezier curve drawing) - Due December 8
  

You must be the sole original author of all assignments and examination solutions in their entirety, unless the instructor explicitly instructs you otherwise in written directions on an assignment or exam.
Collaborative work is a violation of academic honesty in this course.
You are not to examine or use code belonging to someone else, nor may you let anyone else examine or copy your code.
You may not use generative tools to produce your programs.

Students found in violation of the Academic Honesty policy will receive an 'F' in the class.
In the case of plagiarism, all parties involved will be equally penalized.

The description of the department's Academic Integrity Policy can be found here. If a student violates this policy, an Alleged Academic Misconduct Report will be filed with the college.

It is your responsibility to avoid violating the university's policy. If you are unclear as to what the policy means in a particular situation, ask the instructor for clarification before you hand anything in.

See the examples below for clarification of this policy.

Examples

• Using code provided in lecture: include comments that cite the source.
• Using code provided in the class textbook: include comments that cite the source.
• Code developed jointly with instructor or teaching assistants assigned to this course.
• Discussing algorithms or possible approaches to writing your program, WITHOUT discussing particulars of the code.
• Discussing how to resolve errors, WITHOUT discussing particulars of the code.

• You borrow a printed or electronic copy of a friend's assignment, and use it for "inspiration".
• You give a printed or electronic copy of your assignment to somebody else.
• You "find" a copy of somebody's program in the trash, on a lab machine, on their hard drive, on the web, etc., and use it for "inspiration".
• You pay a "tutor" who writes the assignment for you.
• You download code from the Web, and turn in some or all of it as your own assignment.
• You use generative tools to create portions of your assignments.
• You and a friend together write one assignment, then create separate modifications to be handed in.
• You and a friend write certain portions of the assignment individually, but collaborate on other portions of the assignment.
• You work in a group that works out the detailed structure of the assignment and you turn it into a specific program.

Your source code for all programming assignments will be run through a plagiarism detection system. This program uses compiler techniques, which are invariant of syntax and style. If you are sharing/borrowing code with other classmates (from this or previous years), you will get caught.