Use this guide as a working review for UK Computer Science Coursework Guide. Begin with “Read the brief as a specification”, then move through “Map marks to deliverables” and the remaining stages against your own brief. The aim is to leave a clear trail from the requirement to the technical evidence and final explanation, rather than relying on a generic submission checklist.
Read the brief as a specification
For “Read the brief as a specification”, work directly from the wording of your own assessment. Note the exact action verbs, required files and marking signals that relate to this stage. Then decide what concrete evidence will demonstrate completion before moving on to “Map marks to deliverables”.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
Map marks to deliverables
Treat “Map marks to deliverables” as a decision point rather than a box to tick. Write down what could go wrong, what another student or marker would need to reproduce, and which assumption should be tested. That makes the transition to “Plan code, evidence and report sections” much easier to justify.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
Plan code, evidence and report sections
A practical way to handle “Plan code, evidence and report sections” is to create a small, inspectable output first. Compare it with the rubric, record any dependency or source you relied on, and only then expand the work. This prevents the final report from becoming disconnected from the actual technical process.
Use a reader-first check: could someone who did not build the project understand the requirement, the action you took and the evidence that supports the outcome? If not, add the missing context now rather than trying to reconstruct it at the end of the assignment.
Test before writing conclusions
For “Test before writing conclusions”, work directly from the wording of your own assessment. Note the exact action verbs, required files and marking signals that relate to this stage. Then decide what concrete evidence will demonstrate completion before moving on to “Use feedback as a final audit”.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
Use feedback as a final audit
Treat “Use feedback as a final audit” as a decision point rather than a box to tick. Write down what could go wrong, what another student or marker would need to reproduce, and which assumption should be tested. That makes the transition to “Read the brief as a specification” much easier to justify.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
Final check for UK Computer Science Coursework Guide
Return to the first section, compare the finished work with each rubric row and verify that every important claim is supported by code, a test, a result, a source or a clearly reasoned explanation. Remove evidence that does not help the reader understand or assess the work.