Teaching KS3 Computing when you're not a specialist
Many KS3 Computing lessons are taught by teachers whose main subject is something else: maths, science, business or design. If that's you, the good news is that KS3 Computing rests on a small number of big ideas, and you don't need to be a programmer to teach them well. This guide covers what's in the curriculum, the key words, the mistakes students make, and how to check what they remember.
What KS3 Computing covers
The National Curriculum for Computing at Key Stage 3 (Department for Education, 2013) sets out what students in Years 7 to 9 should be taught. In plain English, it comes down to six areas:
| Area | What it means in the classroom |
|---|---|
| Algorithms | Step-by-step instructions to solve a problem; sorting and searching; breaking a problem into smaller parts |
| Programming | At least two programming languages, at least one of them typed (usually Scratch, then Python) |
| Data and binary | How computers store numbers, text, pictures and sound as 1s and 0s; simple Boolean logic (AND, OR, NOT) |
| Hardware and software | The parts of a computer, what the CPU does, and how hardware and software work together |
| Creating digital content | Using software to make things for a real audience, such as spreadsheets, presentations and websites |
| Using technology safely | Online safety, privacy, passwords, and how to report concerns |
Your department will usually have a scheme of work that orders these. Ask for it, and ask which units are taught first in Year 7: they're the ones students need to know well before GCSE.
What the research says
- You're not alone. The Royal Society's (2017) report After the reboot found that many computing lessons in England are taught by teachers without a computing background, and called for more support for them.
- Read code before writing it. The PRIMM approach (Sentance and Waite, 2017) has students Predict what a program will do, Run it, Investigate it, Modify it and then Make their own. It suits non-specialists well because the class starts from working code rather than a blank screen.
- Use, then modify, then create. Lee and colleagues (2011) describe the same progression: students use a working program, change it, and only then create their own. It builds confidence and cuts down on lessons lost to errors.
- Knowledge first. Ofsted's (2022) research review of computing stresses that pupils need secure knowledge of the basics, taught clearly and revisited, before they can apply it in bigger projects.
Key words to teach
Much of KS3 Computing is vocabulary. If students know these words and can use them correctly, they're in good shape:
- Algorithm: a set of step-by-step instructions to solve a problem.
- Sequence, selection, iteration: doing steps in order, making a choice (if), and repeating (loops). These three ideas are the heart of programming.
- Variable: a named store for a value that can change, like
score. - Decomposition: breaking a problem into smaller parts.
- Abstraction: leaving out detail that doesn't matter (a London Underground map is a famous example).
- Debugging: finding and fixing mistakes in a program.
- Binary, bit, byte: the number system computers use; a bit is a single 1 or 0; a byte is 8 bits.
- CPU, RAM, storage: the part that processes instructions, the fast memory that's lost when the power goes off, and where files are kept.
- Input, output: data going into a computer and coming out of it.
Mistakes students often make
| The mistake | A quick fix |
|---|---|
| "RAM and storage are the same thing" | RAM is a desk (fast, cleared at the end of the day); storage is a filing cabinet (slower, kept) |
| "The internet and the World Wide Web are the same" | The internet is the roads; the web is one kind of traffic on them, alongside email and games |
| Thinking a loop runs one extra or one fewer time | Trace it on paper with a table: one row per time round the loop |
Reading x = x + 1 as a maths equation | Read it aloud as "x becomes x plus 1": the right side is worked out first |
| Thinking a computer "knows" what you meant | Act it out: a student follows instructions exactly as written, and the class sees the gap |
| Reading binary from the wrong end | Write the column values (8, 4, 2, 1) above the digits every time until it's automatic |
For a longer list aimed at GCSE, see 12 common misconceptions in GCSE Computer Science.
You don't have to know every answer
- Learn one step ahead. Try each programming task yourself before the lesson. If you can do it, you can teach it.
- Use unplugged activities. Many ideas (algorithms, binary, sorting, networks) are taught well with cards, string and people, no computers needed. They're also the easiest lessons to teach with confidence.
- "Let's find out" is a fine answer. When a student asks something you don't know, working it out together models exactly how programmers solve problems.
- Lean on your confident coders. Every class has a few. Let them help a neighbour, but make sure everyone writes their own code.
- Ask your department for model answers. Worked solutions to the programming tasks save you hours.
Checking what students remember
KS3 topics come round only once or twice a year, so students forget quickly unless they keep recalling them. The most effective habit is short, regular quizzing:
- A starter every lesson with questions from older topics, not just last lesson. See KS3 Computing starter ideas for 30 you can use.
- An exit ticket at the end of lessons that introduce something new. See How to use exit tickets in Computing lessons.
- Short self-marking homework rather than long projects. See Computing homework that works.
The research behind this is set out in Retrieval practice in Computing.
How RADevo helps
RADevo has quizzes for every KS3 Computing topic, each with a plain-English explanation of the right answer, so you can see what to say when students get it wrong. Homework marks itself, the Do Now builder picks the questions your class got wrong most, and Results shows which topics need going over again. Our free KS3 Computing revision pages are a good place to start.
References
- Department for Education (2013). National curriculum in England: computing programmes of study.
- Lee, I., Martin, F., Denner, J., Coulter, B., Allan, W., Erickson, J., Malyn-Smith, J. and Werner, L. (2011). Computational thinking for youth in practice. ACM Inroads, 2(1), 32–37.
- Ofsted (2022). Research review series: computing.
- Sentance, S. and Waite, J. (2017). PRIMM: exploring pedagogical approaches for teaching text-based programming in school. Proceedings of the 12th Workshop on Primary and Secondary Computing Education (WiPSCE '17).
- The Royal Society (2017). After the reboot: computing education in UK schools.