0% found this document useful (0 votes)
90 views

Computer Science Test Rubric - JAVA

The document provides a rubric for grading a Java program assignment. It outlines criteria such as program functionality, errors, output correctness, formatting, modularity, and documentation. Points are awarded based on how well the program meets the criteria, with 100 points being a perfect score. Deductions are listed for various issues like incorrect output, lack of modularity, missing documentation, and other errors or problems.

Uploaded by

Siti Zuhra
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
90 views

Computer Science Test Rubric - JAVA

The document provides a rubric for grading a Java program assignment. It outlines criteria such as program functionality, errors, output correctness, formatting, modularity, and documentation. Points are awarded based on how well the program meets the criteria, with 100 points being a perfect score. Deductions are listed for various issues like incorrect output, lack of modularity, missing documentation, and other errors or problems.

Uploaded by

Siti Zuhra
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Computer Science Program Rubric - JAVA Name__________________________________

Test/Quiz/Activity #___ Date___________________________________

_____ 45/100 Program is incoherent, illogical, and indicates a lack of knowledge of proper syntax
and correct modular programming style. Errors are numerous ( 10 or more ) and
require a significant amount of time to correct.

_____55/100 Program shows signs of becoming workable, and uses some aspects of correct JAVA
syntax and formatting. Errors are minimal ( 3 <= X < 10 ).

_____60/100 Program does not function as expected and does not compile or run. The program
contains 1 or 2 errors that are relatively simple to correct. Coding and JAVA syntax
seem appropriate for the most part.

_____65/100 Program compiles and runs without errors. Output is INCORRECT or


PARTIALLY correct (~25%), but contains some calculation or formatting errors.

_____70/100 Program compiles and runs without errors. Output is PARTIALLY correct (~50%),
but contains some calculation or formatting errors. A few measures were taken to
format the output with respect to alignment, elegance, and readability.

_____75/100 Program compiles and runs without errors. Output is MOSTLY correct (~75%), but
contains some calculation or formatting errors. Notable measures were taken to
format the output with respect to alignment, elegance, and readability.

_____80/100 Program compiles and runs without errors. Output calculations are COMPLETELY
correct (100%). Notable measures were taken to format the output in respect to
alignment, elegance, and readability.

_____ / 2 Descriptive Identifiers / Use of Correct Java Naming Conventions

_____ / 3 Appropriate Commenting/Documentation ( Pre & Post Conditions )

_____ / 3 Proper Spacing, Indentation, and Alignment of Key Code Blocks

_____ / 7 Code is Completely Modular and Uses Proper Object Oriented Style

_____ / 5 Elegance and Readability of Program Output

_____( - ) Miscellaneous Deductions (if any) ___________________________________________

_____( + ) Bonus Points (if any) ______________________________________________________


------------- -------------------------------------------------------------------------------------------------------------

______/ 100 YOUR GRADE


Comments (if any):
______________________________________________________________________________________________________
______________________________________________________________________________________________________
______________________________________________________________________________________________________
Point Deduction Key Codes
 TB Title Box Needed

 NC Naming Convention Violation

 OL Code Written Pass The Right Margin Line

S Inconsistent Spacing Throughout the Code

 INF Inefficient Code – Simpler Design In Order

 OE Data Output Not Elegant or Organized

I Identifiers Not Initialized

 FN Final Variables Needed in Program

 OP Output Precision is Incorrect (Round-Off Errors)

 IO Incorrect Output/Values in Some or All of The Code

A Incorrect Alignment of Code Blocks

 IND Code Indentation Needed

M Modularity Needed in Code

D Appropriate Documentation Needed/Missing

 VD Documentation is Vague and/or Undescriptive

 VI Vague Introduction

 RT Return Type Needed (in Method) or Used Incorrectly

 NI Program Needs/Missing Introduction

 UC Unneeded Code Left in The Program

 DNW Program Does Not Work

You might also like