Your final grade will be weighted as follows.

Letter grades are figured according to the standard scale: 90% or more of the total points in the class will earn you an A- or better, 80% a B- or better, 70% a C- or better, and so on. The actual grade you receive, however, may be curved based upon the performance of your peers.

Homework is due on the dates below. You will not be reminded to turn it in, you are expected to keep track of your deadlines. Late homework will not be accepted.

Your coding style will play a huge part in determining your score on the assignments. I will not hesitate to assign D's and F's to working programs which are poorly structured, haphazardly indented, under-commented, have poor identifier names and abbreviations, contain inappropriate hard-coded values, or are not "easily maintainable". Appearance of the grading policy in this syllabus constitutes "fair warning" of the consequences of poorly written code.

Code that fails to compile or fails to validate when run through a conformance test (e.g. validating parser) will be given an F without further review.

All submitted work, when turned in must be typed and proofed. The ability to communicate your ideas clearly and effectively is a critical aspect of your work now and later in industry. As such, assignments with misspellings and bad grammar will be returned ungraded. You are encouraged to make use of your peers and it is my assumption that any writing assignment you turn in has been proofed by at least one other person. The campus LRC in the library is an invaluable resource in this regard. An exception to printed/typeset material requirement is granted for hand-annotation of printed screen shots, complicated diagrams or other material that would be impractical to typeset. However, illegible work will be returned ungraded.

Work may be turned in either in-class or via email, however email submissions of writing assignments will be accepted in PDF format only. Word is not an acceptable format for electronic publication.