How to use this sheet
Take one sheet per team. You are marking only your own course's dimension of the shared file — the row against your course code below. The five criteria are the same in every course and every block, so a 14 means the same thing across the university. The team mark of 15, with the viva of 5 you hold in the Presentations & Viva week and your own quizzes and assignments 10, makes the sessional 30 of the hundred. Where your course falls outside a team's eight, you mark that student's lens note on this same sheet instead.
Four standing rules
The window. The file goes in between Sat 12 and Wed 16 December, and the whole window is on time; nothing is accepted after Wednesday 16 December. Individual adjustment. You may move one member up to two marks above or below the team mark on the evidence of the viva and the team charter, with a one-line reason in the comment box. Moderation. The convener samples three files per block and will ask you to re-mark, with them present, if your marks sit three or more (out of 15) away from the other courses on the same file. One or two enrolled members. Where your course marks a Folio for one or two enrolled members of the team, mark their named sections; integration (2) asks whether the section belongs to the Folio, not whether the Folio holds together; no ±2 on a one-member marking.
The 15 marks
| Criterion | Max | What you are looking for | Awarded |
|---|
| Substance in this course's dimension | 6 | Does the part this course marks actually work? Is it right, complete and at the level expected of this year? | |
| Evidence and method | 3 | Is the claim supported? Was the method appropriate, followed, and reported honestly? | |
| Integration with the team's file | 2 | Does this part fit the rest of the work, or does it sit beside it? Is the file one document or five stapled together? | |
| Presentation and professionalism | 2 | Is it legible, cited, complete and handed in on time, in the form asked for? | |
| Revision and response to feedback | 2 | Did the draft change after the session-10 review, and can the team say why? | |
| Total | 15 | | |
Course marking this sheet Bands
| Band | Description |
|---|
| 13–15 | Professional. Could be handed to the client, the customer or the community as it stands. Reasoning is explicit and the evidence supports every claim. |
| 10–12 | Sound. Complete, correct and defensible, with gaps that are visible but not damaging. |
| 8–9 | Adequate. The work exists and meets the brief, but is thin in evidence, craft or integration. |
| 5–7 | Weak. Incomplete, or complete but not supported. Would need substantial rework to be usable. |
| 0–4 | Not submitted, or so far short of the brief that it cannot be assessed. |
The dimensions in this block
Each course marks only its own row. The wording below is the same as the one printed in that course's outline, so a student reading their outline and a teacher reading this sheet are looking at the same sentence.
| Code | Course | Dimension marked — 15 marks | Teacher |
|---|
| GCAA444 | Analysis of Algorithm | This course marks the cost account: the asymptotic analysis of the algorithms in the study, the design of the benchmark, the measured results, and the honest reconciliation of predicted with observed running time on the team's chosen workload. 15 marks, team. | Mariha Fahad |
| GCCA445 | Computer Architecture | This course marks the hardware account: the benchmark run on the team's program, the cache and pipeline behaviour measured, the architectural change proposed and simulated, and whether the speed-up claimed survives Amdahl's law. 15 marks, team. | Maaz Ahmed |
| GCCE691 | Natural Language Processing | This course marks the language component of the study: the corpus and how it was prepared, the model built, the evaluation design, the error analysis, and the honesty of the claims made about what the component can and cannot do. 15 marks, team. | Haris Yaseen |
| GCOS443 | Operating Systems | This course marks the operating-system account: the processes and threads the team's program creates, its synchronisation and whether it is free of races, the scheduling and paging behaviour measured under load, and the system-call trace read and explained. 15 marks, team. | Yahya Ali Rashidi |
| Code | Course | Dimension marked — 15 marks | Teacher |
|---|
| GCTA441 | Theory of Automata | This course marks the formal model: the automaton or grammar written for the team's input language, its conversion and minimisation, the proof that the class chosen is the right one, and the recogniser built from the model. 15 marks, team. | Ume Farwa |
| GCCN555 | Computer Networks | This course marks the network: the requirements read out of the brief, the address plan, the device configuration and how it was verified, the packet captures that prove the design works, and the fault log showing what broke and how it was found. 15 marks, team. | Adeel Karim |