Project Grading

This course requires that you complete programming projects of a variety of types. In some cases, you are required to write, debug, and test a C program. In some cases, you must solve assembly language programming "puzzles".

Because of the different types of projects, no single grading methodology is possible for all projects. Therefore, the grading criteria for each project will be provided with each project specification.

C Programming Projects

In general, C programs will be graded for correctness and to a lesser extent for style
C coding standards from a previous course are provided for your reference.

Assembly Language Puzzles

In general, assembly language projects take the form of multi-part puzzles to be solved. Points are awarded for solving each piece of the puzzle. Points may be deducted for failed attempts to solve the puzzles.

Project Grade Changes

Visit your TA during regular office hours (or make an appointment) to request a project grade change when you think the grader has made a mistake. Come prepared to show evidence of a specific grading mistake. Project grades will not be changed just because you think the TA has graded your project too harshly.

Remember that if you have a question regarding your project grade, you have exactly one week from the receipt of your grade to speak to your TA in person.

Project Regrades

In some unusual circumstances you may recieve a low project score because of a single, simple error that results in many incorrect outputs or results in a compiler/linker error. The definition of "simple error" is determined by your TA. In such cases, your TA may (at his discretion) allow you to fix the simple mistake and have your project regraded.

A deduction of 10% of the project value is assessed when your project is regraded.