As already stated, the grading system can be different even between different modules. As an example, the mark-to-grade mapping table for the 2nd year CS modules last semester is here:
http://www.owenrudge.net/various/grades.html
whereas last year in a third year module, the mapping as more like:
29.5% --> 5
39.5% --> 7.5
46.0% --> 10.5
58.0% --> 13.5
68.0% --> 16.5
85.0% --> 20
Grade descriptors for comp sci (they were in the general handbook, foo - although, admittedly, these are for coursework more than exams, I guess):
• Grade 0: nothing submitted
• Grade 1‐2 (severe fail): almost no evidence of any attempt to complete the piece of work.
• Grade 3‐4 (fail): no evidence of any serious attempt to complete work. No substantial relevant code or other deliverable. No report showing any grasp of the issues.
• Grade 5‐7 (bare pass): Evidence of a serious attempt at the work, which ran into major problems. Typically might include code representing a significant part of a solution, but which does not compile or does not run, together with a report describing the problems and the attempts made at a solution. Might also include working code for part of the problem, but no report, or similar.
• Grade 8‐10 (pass): Evidence of a reasonable attempt addressing some requirements. For coding assignments, code achieves some of the required functionality and is adequately documented/reported or a model captures some elements of what is to be modelled. Might also include better code and a weaker report or vice versa. Code style starts to become important at the top end of this range.
• Grade 11‐13 (pass): Evidence of a competent attempt addressing most requirements. For coding assignments, code achieves most of the required functionality and is of acceptable standard. Report describes what was done clearly and in proper style or model captures main features of what is to be modelled. Might cover code, which is fully functional but poor in terms of style, readability and robustness, when the report adds little or no value to the code.
• Grade 14‐16 (merit): Evidence of a good attempt completing nearly all requirements successfully. For coding assignments, code or model should achieve almost all required functionality and be clear and well‐structured. Report should be clear and show a proper level of understanding.
• Grade 17‐18 (first rank): Evidence of an excellent attempt with no significant defects. For coding assignments, code or model achieves full functionality required, including any extension elements, and is well‐designed and clear in good style. Report shows real insight into the subject matter, and is clear, well written and well presented.
• Grade 19‐20 (exceptional): Evidence of exceptional achievement. For coding assignments, code or model achieves all specified functionality, and may contribute some appropriate extra features. Design and implementation show unusual clarity and planning, producing robust and effective software or an exceptionally expressive model. Report is very well written and presented, showing evidence of background reading, a full knowledge of the subject and insight into the problem.
So that's a rough guideline, but it does vary between subjects, modules and years.
[hr]
http://www.owenrudge.net/
http://standrews.facebook.com/profile.php?id=37103734