Chhetri AcademyGCSE & A level Paper Builder

How to get a grade 7 in Edexcel GCSE Computer Science

Download as a PDF

A grade 7 means you are secure across the whole specification, not just the familiar parts. Your answers are precise and applied to the scenario, your working is accurate including two's complement and shifts, and in Paper 2 you write complete, tested programs using functions, lists and files, and make a strong start on the hardest task.

What a grade 7 asks of you

  • Precise technical language applied to the context in every answer: not 'the CPU is faster' but 'a higher clock speed means more instructions can be fetched, decoded and executed each second'.
  • Accurate two's complement, overflow, logical and arithmetic shifts, hexadecimal, and expressions that include every unit conversion.
  • Full-mark trace tables, confident merge sort and binary search steps, and clear comparisons of how efficient algorithms are.
  • Discuss answers in the upper levels: developed, balanced and tied to the scenario throughout.
  • Paper 2 programs that meet every requirement, including validation, functions with parameters and return values, two-dimensional lists, reading and writing files, and output formatted exactly as asked.

Secure these topics

  • The harder data topics: two's complement, what an arithmetic right shift does to a negative number, overflow, and the limits on range and precision set by the number of bits available.
  • Merge sort and binary search, step by step, and comparing algorithms by the number of comparisons and passes.
  • The TCP/IP model: the four layers and which protocols work at each. Network security: finding vulnerabilities and protecting a network.
  • Programming languages and translators: high-level and low-level languages; compilers, interpreters and assemblers, with the benefits of each.
  • Issues and impact: artificial intelligence, machine learning and robotics, intellectual property and licensing, and the protection of personal data.
  • Programming: subprograms, local and global variables, file handling, validation, two-dimensional lists, and string manipulation and formatting.

Question types to master

  • Explain questions answered with a point and a linked development, in the scenario's terms.
  • Construct an expression for image size, sound file size or transmission time, with all the conversions.
  • Identify and correct errors in algorithms and code, naming the type of error.
  • Writing a complete, correct algorithm on paper as a flowchart, pseudocode or program code.
  • The extended Discuss answers, covering each aspect named with developed points on more than one side.
  • Paper 2 amend, extend and write-from-requirements tasks, with input handling that does not crash.

Programming practice for Paper 2

  • Once a week, write a complete program from a short set of requirements against the clock, for example 25 minutes. Good practice programs: a quiz that reads its questions from a file, a stock list kept in a two-dimensional list, a login with limited attempts.
  • Practise debugging on purpose: take a working program, break it in several places, then find and fix each fault. Aim to be fast at logic errors.
  • Structure your code with functions. Pass values in as parameters and return results, rather than relying on global variables.
  • Test every program with normal, boundary and erroneous data, and fix what breaks.
  • Know the PLS string methods, format() placeholders and file methods well enough that you do not need to hunt for them.

A 10-week plan

  • Aim for 4 to 5 hours a week, plus a Daily 5 every day.
  • Weeks 1 and 2: sit a timed mock of each paper to find your gaps, then list your weakest subtopics from Progress.
  • Weeks 3 to 5: work through the weak subtopics first with notes, worksheets and Medium or Hard custom papers; write one timed program each week.
  • Weeks 6 and 7: the harder data topics and algorithms; one Discuss answer a week marked against the levels; the Paper 2 practice set.
  • Weeks 8 and 9: full timed mocks, alternating Paper 1 and Paper 2, and an error log after each one.
  • Week 10: redo every question you dropped marks on, go through flashcards and cheatsheets, and write a short program every day.

Using GCSE Paper Builder

  • Grade-by-grade skill lists: tick off every skill up to grade 7, and revisit any you cannot do from memory.
  • Custom paper: mixed subtopics on Medium and Hard. Mixing topics makes you decide which method to use, as in the real exam.
  • Mock exams: sit them timed, aiming to finish Paper 1 with time to check. For the Paper 2 practice set, write and run your code in a Python IDE.
  • Progress: work from the weakest subtopic up, and redo the questions you dropped marks on until they are secure.
  • Daily 5 and Flashcards: keep every topic fresh and your definitions word-perfect.
  • Notes and worksheets: use them to close gaps; the cheatsheets are for the final weeks.
  • Whiteboard: plan programs, trace algorithms and set out binary working on screen.
  • 1-to-1 tutoring with Chhetri Academy (free 30-minute trial lesson) helps if you need targeted feedback on your Paper 2 code or your Discuss answers.

Timing in the exam

  • Paper 1: aim to finish with 5 to 10 minutes to check. Give each extended Discuss answer about 1.2 minutes per mark, plus a moment to plan.
  • Paper 2: before coding a longer task, spend a minute or two listing its requirements, for example as comments at the top of the file.
  • Code and test in stages: get part of the program running, test it, then add the next requirement.
  • Don't polish a nearly finished task while another task is untouched. Get marks on every task first.
  • Keep the last 10 minutes to run every file and check the file names.

Traps at grade 7

  • Answers that are correct but not linked to the scenario, which miss the higher marks.
  • Discuss answers that are one-sided, or a list of points with no development.
  • Two's complement slips: forgetting that the leftmost bit of an 8-bit number is worth −128, or mixing up logical and arithmetic shifts.
  • Off-by-one errors in range() and loop conditions, and not handling the first or last item correctly.
  • Validation written with a single if instead of a while loop, so a second invalid entry gets through.
  • Output not in the format asked for: missing rounding, a different message or the wrong order.
  • Spending 15 minutes on one bug while easier marks are waiting elsewhere.

Stuck? Get 1-to-1 help. Chhetri Academy tutors GCSE and A level Maths and Science online, with a free 30-minute trial lesson.

Book a free trial