CSCE 330 Fall 2017: Grading

The grading policy is subject to revision.

  • Quizzes: 5%
  • Programming Assignments and Other Homework: 45%
  • Midterm: 15%
  • Final Exam: 30%
  • Presentation: 5%
  • The numeric scores are translated to letter grades as follows: [90-100] = A, [87-90[ = B+, [80-87[ = B, [77-80[ = C+, [70-77[ = C, [67-70[ = D+, [60-67[ = D, [0-60[ = F. However, in order to obtain a grade of C or better in this course, it is necessary to obtain at least a grade of D (60%), cumulatively, on the tests. The instructor has the final say in setting the algorithm for computing the cumulative test grade.

    Some quizzes will be based on the assigned readings. Quizzes (which are often in class exercise) are designed to emphasize a salient issue in the lecture of the day or in a previous lecture. Another purpose of quizzes is to take attendance. Students who take all quizzes and who, in the judgement of the instructor, make an honest attempt to answer the quiz will receive full credit for them. Missed quizzes may be replaced by correctly answered quizzes, up to a number (usually three), which is determined by the instructor, and depends on how many quizzes are given.

    Homework must be turned in typed; exceptions will be made for assignments requiring figures or unusual formatting. Homework will normally be due before the beginning of class. Homework will normally be submitted through the departmental dropbox. Homework turned in late is subject to a 10% per day penalty, subject to the provision that no credit is given to homework turned in after the beginning of the following class.

    Each student is expected to attend all classes for this course and is responsible for all material covered in class or assigned. In particular, absence from more than four scheduled classes, whether excused or unexcused, is excessive and may result in a grade penalty, consistently with the University Attendance Policy, which is provided in the University Bulletin. Student who expects to miss class for any reason must contact the instructor by email as soon as possible.

    Programs in Prolog, Haskell, and possibly other programming languages, will be assigned during the course. Programming assignments should be developed to run in the Linux, UNIX, or MS-Windows environment, as indicated. Please comment your code, when appropriate. Programs will be submitted using the departmental dropbox.

    Each student must follow the University Honor Code and turn in his or her work. It is very good to study in groups. In fact, there is evidence that group studying is a predictor of success, at least in early college mathematics courses. Some of you may enjoy studying in groups! You are therefore encouraged to discuss the material you study, but you must do your homework individually, unless an assignment is explicitly designated as a team assignment. The minimum grade penalty for a violation will be a zero on the work involved. In addition, an honor code violation will be subject to the sanctions described in the USC Community Handbook and Policy Guide. The following paragraph, written by Professor Duncan Buell, clarifies the distinction between "learning from a discussion" and "turning in someone else's work": If, after having participated in a group activity, you can walk away, put the books down, have lunch, and then come back afterwards to re-create from your own head the material and techniques you discussed as a group, then you can legitimately say that you have learned from the group but the work you turn in is your own.