next up previous
Next: About this document ...

CpSc 428/628
Programming Language: Design & Implementation

Policies and Information
Department of Computer Science, Clemson University
Brian Malloy, PhD
August 23, 2006



Office: 313 McAdams Hall Phone: 656-0808
Office Hours: TBA e-mail: malloy@cs.clemson.edu
No office hours on Thu or Fri TA: me



  1. There is no official textbook for this iteration of this course. I will be taking material from various sources including textbooks, and material from web resources.

  2. Tentative Grading Policy ($\pm$ 10%):

    Exams 50% Date: Sept 13th, Oct 18th
    Final Exam 20% Date: Dec 13th, Wed, 6:30-9:30 PM
    Assignments 20%  
    Final Project 10% Dec 6th
    Fall Break   Nov 6-7, Mon & Tue
    Thanksgiving Holiday   Nov 22-24, Wed, Thu & Fri
    Final Exam Week   Dec 9-16, Sat - Sat

  3. Course objective: To build an multi-lingual application that demonstrates mastery of a variety of programming language paradigms.

  4. Attendence: Attendence at classes is expected. Many studies have found that the single factor that contributes the most to success in a course is class attendance. Failure to attend not only hurts you, but places an extra burden on the instructor and detracts from the overall quality of the course. If you have exceeded 3 unexcused absenses before the drop date you may be dropped from the course. If you are not or cannot be dropped, or if the last day to drop has already passed, you will receive an F for the course. You are responsible for keeping track of your situation in the course. If you know that you have exceeded the maximum number of absences before the last day to drop you should go ahead and drop the course yourself to avoid an F.

  5. Policy and Syllabus: This policy & the syllabus can be found on my web page.
    www.brianmalloy.com
    

  6. Venue: The course meets in McAdams 119 on Monday and Wednesday from 4:00 until 5:15. If the instructor has not arrived by 7:30, you may assume that something bad has happened and you may depart.

  7. Assignments: There will be 4 to 7 assignments that will be done by you, alone. You may talk about what you did and how you did it with me or with fellow students; I would like to encourage communication among students. Obviously, you may not give/mail your code to another student. Your assignments will demonstrate your mastery of the various languages and tools that we use to build our multi-lingual application.

  8. Grades: The grading scale is: 90 or better is an A, 80 or better is a B.

  9. Behavior: Please do not engage in side conversations during class. Try to direct your comments to all of us. I believe that we're all interested in learning more about game construction.




next up previous
Next: About this document ...
Brian Malloy 2006-08-23