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 |
|---|
| GCCO432 | Computer Organization & Assembly Language | This course marks the machine-level account of the team's program: the disassembly read and annotated, the register and stack usage explained, the memory-access pattern measured, and the gap between the predicted cost and the time the machine actually took. 15 marks, team. | Ume Farwa |
| GCDS433 | Discrete Structures | This course marks the proof: the loop invariant and the induction that establishes correctness, the recurrence set up for the chosen algorithm and its solution, the counting argument behind the search space, and whether the bound claimed is the bound proved. 15 marks, team. | Haris Yaseen |
| GCDS435 | Data Structures | This course marks the implementation: the structure chosen and the case made for it, the correctness of the operations under edge cases, the measured time and space against the predicted bound, and the quality of the test set the team wrote. 15 marks, team. | Dr Nasreen |
| GCLA431 | Linear Algebra | This course marks the mathematics: the matrix model set up for the team's problem, the method chosen to solve it, the account of conditioning and numerical error, and whether the results the program produces are the results the model predicts. 15 marks, team. | Zaeem Farooqui |
| Code | Course | Dimension marked — 15 marks | Teacher |
|---|
| GCAG311 | Calculus & Analytic Geometry | This course marks the continuous mathematics: whether the model is set up correctly, whether the limits, derivatives and integrals are right, whether the geometry is represented properly in coordinates, and whether the team can justify every step by hand. 15 marks, team. | Zaeem Farooqui |
| GCDD323 | Digital Logic Design | This course marks the hardware: the truth table and state diagram derived from the model, the minimisation and the case made for it, the Verilog implementation and its testbench, and the timing analysis that shows the circuit meets its clock. 15 marks, team. | Adeel Karim |
| GCMC325 | Multivariable Calculus | This course marks the continuous model: the function set up for the team's problem, the derivatives and integrals computed from it, the optimisation carried out and its constraints, and whether the numbers the model produces are defensible. 15 marks, team. | Asif Rehman |
| GCPF312 | Programming Fundamentals | This course marks the code itself: whether the program the team ships actually runs, whether the logic is correct at the boundaries, whether the structure is readable by someone who did not write it, and whether the student can explain any line of it. 15 marks, team. | Yahya Rashidi |