0% found this document useful (0 votes)
163 views1 page

Grading Rubric

The document outlines a grading rubric for evaluating code solutions with categories for Solution (50%), Report (30%), and Code Quality (20%). It provides descriptions of what constitutes an insufficient, sufficient, good, or excellent score for each category. The remarks note that an insufficient solution score cannot be compensated by other categories and that partial solutions can still score well if optimal algorithms and structures are used.

Uploaded by

Serkan Sezin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
163 views1 page

Grading Rubric

The document outlines a grading rubric for evaluating code solutions with categories for Solution (50%), Report (30%), and Code Quality (20%). It provides descriptions of what constitutes an insufficient, sufficient, good, or excellent score for each category. The remarks note that an insufficient solution score cannot be compensated by other categories and that partial solutions can still score well if optimal algorithms and structures are used.

Uploaded by

Serkan Sezin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Category Weight No Score = 0 Insufficient = 3 Sufficient = 6 Good = 8 Excellent = 10

Solution 50% Incomplete solution of (basically) complete and Fully complete and correct Optimal choice of
failing unit tests correct solution for test data solution for any valid test algorithms and data
given data structures (CPU + memory
efficient while maintainable
code)
Report 30% Practically missing or code Too little or lacking Seven code snippets Three most complex code Alternative solutions are
solution is insufficient to explanation of (seven) code provided with acceptable fragements have been being discussed with clear
start with snippets explanation included with clear and and compelling
compelling explanations explanations; clear and
compelling explanations for
chosen solution
Code Quality 20% Report or solution is correct use of nameing effective encapsulation; and Low cyclomatic complexity
insufficient to start with concentions; well readable (re)use of methods with (use of loops, if-else); extra
code; useful inline appripriate parameters unit tests
comments

Remarks:
If the solution itselves scores insufficient, that score cannot be compensated by excellent report or code quality!
Within a category, scales van compensate; i.e. a partially correct solution that just passed unit tests can still score "Good" if optimal algorithm and data structures have been used.

You might also like