Mr Ashim

CSCI 180 Project Grading   Your project is graded based on four categories: correctness, assignment requirements, documentation, and style. Below are the point breakdowns for each of these areas, detailing the range of points you will receive for achievement levels within each of these categories.   Functionality Note that you cannot receive the minimum functionality points for a level unless your code fulfills the requirements for that level. So, for example, if you do not fulfill the C-level requirements completely (with minor errors), the highest grade you can receive is a 39 no matter what other features you have put into your code.   60-70

      50-59

        40-49

        30-39

        0-30

 

  Code compiles and runs without crashing. Fulfills the A-level requirements. Variant points based on quality of minor flaws in correctness.   Code compiles and runs without crashing. Fulfills the B-level requirements. Variant points based on discussion of issues arising in reaching the next stage of the project and in how easy it is to determine the correctness of the code by running it.   Code compiles and runs without crashing. Fulfills the C-level requirements. Variant points based on discussion of issues arising in reaching the next stage of the project and in how easy it is to determine the correctness of the code by running it.   Code compiles and runs without crashing. Fulfills D-level requirements. Variant points based on discussion of issues arising in reaching the next stage of the project and in how easy it is to determine the correctness of the code by running it.   Code does not compile or code crashes when run. Variant points awarded based on quality of analysis of the problem with the code.

  Assignment Requirements   5 Handed in on time, code has some documentation, and you included a journal (as described

in assignment). The journal includes comments about tasks and issues you encountered and describes how you tested the project.

3 Assignment is on time, code has some documentation, the journal is completed, but a bit

sparse but seems like you wrote it as you went. 2 Assignment is on time. The journal may be a bit sparse or it may be obvious that you wrote

it after the fact. 1 The code might be undocumented, or you may not have turned in a journal. 0 There was an assignment? Oh yeah, here it is. Oh, a journal -- can I still do that? It is

obvious you need to spend more time reading about deadlines and what is included when you hand in your work.

Documentation of Code   During this course, I will frequently award points for documentation as follows (up to 2 points for each item):  

• documentation at top of file including name of file, your name, and date • description of class (top of file) • documentation on each public method including parameter and return tags. • interior documentation for code that may be hard to understand • documentation gives the big picture relating the code to the task, not micro "this line sets

a value"   Naming   Up to 10 points awarded, as follows (up to 2 points for each item):  

• lowercase starting letter on methods and variables • uppercase starting letter on classes • names suggest use of variable • names suggest action of void method • names suggest result of value- returning methods

  You could lose all 10 points for not using names of methods, classes, and files specified in the project assignment.   Code Structure / Style   Please note that efficiency is of little concern to me initially, but gains importance as you learn more programming. Each of the items is awarded 1 point in the rubric:  

• line lengths reasonable (80 or less) • methods are not too long • if possible, blocks of code are not repeated • whitespace/indenting used to increase readability of code • local variables used where appropriate (rather than only fields)