Computer systems: OxfordAQA IGCSE Computer Science Complete Notes

The stuff underneath every app you use

Every time you open an app, stream a video or send a message, there is a whole system of hardware and software working together underneath, and most of the time you never have to think about it. That is kind of the point of good engineering: it hides the complexity. This part of the specification is where you get to lift the lid and see what is actually going on. This oxfordaqa igcse computer science computer systems guide covers hardware and software, Boolean logic, software classification and systems architecture, and honestly, once it clicks, it changes the way you look at your own laptop or phone.

Hardware and software

Hardware is the physical stuff you can actually touch: the processor, the memory chips, the screen, the keyboard. Software is the instructions that tell that hardware what to do. Neither one is much use on its own; hardware without software is just an expensive paperweight, and software without hardware has nowhere to run. Getting comfortable explaining that relationship in your own words, rather than reciting a definition, is genuinely most of what this small topic asks for.

Boolean logic

This is the bit that trips people up at first and then suddenly makes complete sense. Boolean logic works with just two values, true and false, and three gates matter here: NOT, AND and OR. NAND, NOR and XOR are not needed for this course, so do not spend time on those.

Worked example: a truth table with two inputs

Take the Boolean expression A AND (NOT B). Build the truth table by working through every combination of A and B systematically:

A=0, B=0: NOT B=1, A AND (NOT B)=0
A=0, B=1: NOT B=0, A AND (NOT B)=0
A=1, B=0: NOT B=1, A AND (NOT B)=1
A=1, B=1: NOT B=0, A AND (NOT B)=0

You should be able to build a truth table like this for up to three inputs, build a simple logic circuit diagram using the NOT, AND and OR symbols, read a circuit diagram back into a Boolean expression, and go the other way too, drawing a circuit that matches a given expression. It is really just translation practice between three different ways of describing the same logical rule: words, a truth table, and a diagram.

Software classification

Software splits into two broad categories: system software and application software. System software manages the computer itself; application software is what a person actually uses to get something done, like a word processor, a game or a messaging app.

The operating system is the most important piece of system software, and it is worth knowing exactly what it manages, because exam questions like to test this in a fairly specific way. The operating system handles the processor or processors, memory, input and output devices, the applications running on top of it, and security. Utility programs are the other type of system software worth knowing, sitting alongside the operating system to handle specific maintenance tasks, such as file compression or disk cleanup.

Systems architecture

This is the biggest topic in the computer systems section, and it is where a lot of the exam marks in this area actually live, so give it proper time.

Von Neumann architecture and the CPU

Von Neumann architecture describes the basic layout most computers follow: a processor connected to main memory, with instructions and data stored together and moved around using buses, which are simply collections of wires carrying data between components. Inside the central processing unit, three parts matter: the arithmetic logic unit, which carries out calculations and comparisons; the control unit, which directs the operation of the whole processor; and the clock, which times everything so operations happen in a coordinated sequence rather than chaos.

What affects CPU performance

Three factors matter here, and you should be able to explain the effect of each one.

• Clock speed, how many cycles the clock produces per second: a higher clock speed generally means more instructions can be processed per second.
• Number of processor cores: more cores can allow more instructions to be worked on at the same time, though not every task can actually take advantage of extra cores.
• Cache size: a bigger cache lets the processor keep more frequently used data close by, reducing how often it has to fetch from slower main memory.

The fetch-execute cycle

This is basically the heartbeat of a computer, repeating constantly while a program runs.

Fetch: the next instruction is fetched from main memory to the CPU
Decode: the instruction is decoded to work out what it actually means
Execute: the instruction is carried out, which may include reading from or writing to main memory

Being able to name these three stages in order and explain what happens at each one is a reliably examined skill, so it is worth being able to write this out from memory without hesitation.

Memory and storage

Main memory is anything directly accessible by the CPU, apart from cache and registers, and it is volatile, meaning its contents disappear when the power is switched off. Secondary storage is non-volatile and not directly accessible by the CPU; it is what actually holds your files, programs and photos between one power-on and the next. RAM and ROM are both examples worth comparing directly: RAM is volatile and can be written to during normal use, while ROM is non-volatile and typically holds instructions that should not change, such as basic startup routines.

Three types of secondary storage are named on this specification: solid state, optical and magnetic. You should be able to explain how each one physically works, at least in outline, and be able to compare their advantages and disadvantages against each other, including which one suits a given real-world scenario better. Cloud storage is worth knowing too: it uses magnetic and increasingly solid state storage, but located at a remote data centre rather than inside your own device, which brings its own advantages, like access from anywhere, and disadvantages, like depending on a working internet connection.

Embedded systems

An embedded system is a computer system built into a larger device to perform one specific, dedicated job, rather than running a wide range of general-purpose software like a laptop does. Think of a washing machine's control system, or a car's engine management unit; both contain a computer, but neither one is going to run a web browser. You should be able to explain how that differs from a non-embedded, general-purpose system, and give real examples of each.

Bringing hardware and Boolean logic together

It is worth pausing on how the two halves of this topic actually connect, because they are more related than they first appear. Every logic gate you draw a truth table for is, underneath, a tiny physical circuit built from transistors, and millions of those circuits combined are what make up the arithmetic logic unit inside a real CPU. So when you calculate an AND expression on paper, you are essentially predicting what a real piece of hardware does electrically. That link is a genuinely useful thing to mention in an exam answer that asks you to connect Boolean logic to systems architecture, since it shows you understand the topic as one coherent picture rather than four separate lists of facts to memorise.

Common mistakes to avoid

• Mixing up NAND or NOR with the actual required gates, NOT, AND and OR, which are the only three you need.
• Describing RAM and ROM without mentioning volatility, which is usually the exact distinction the question is testing.
• Listing what the operating system manages incompletely; make sure processor, memory, input and output devices, applications and security are all covered.
• Getting the fetch-execute cycle stages out of order, or muddling decode with execute.
• Forgetting that cache size, clock speed and number of cores are three separate factors, each needing its own explanation rather than a single blended answer.

Self-check questions

1. Build a truth table for the expression NOT A OR B.
2. Explain the difference between system software and application software, giving one example of each.
3. List the five things an operating system manages according to this specification.
4. Name and describe, in order, the three stages of the fetch-execute cycle.
5. Give one advantage and one disadvantage of cloud storage compared with local secondary storage.

This whole area rewards being able to explain things in your own words rather than repeating a definition word for word, so try explaining the fetch-execute cycle, or the difference between RAM and ROM, out loud to a friend or family member who has never studied this. If you can make it make sense to them, you have genuinely understood it. These oxfordaqa igcse computer science revision notes on computer systems are written with exactly that kind of understanding in mind, not just recall.

Keep this one close to hand

Systems architecture connects to almost everything else in the course, from how a program actually runs during the fetch-execute cycle to why certain data representation choices affect performance, so this topic guide is worth revisiting even while you are studying other sections. Bookmark it as your igcse 9210 computer systems reference, and pull it back out before attempting any oxfordaqa igcse computer science practice questions on hardware or architecture. Anyone searching computer systems oxfordaqa igcse content is usually trying to get the fetch-execute cycle and the CPU components straight in their head, and that is exactly what the sections above are built around; consider it oxfordaqa igcse computer science explained the way it actually needs to click, not just memorised, and it belongs alongside your other oxfordaqa igcse computer science notes for quick reference before the exam.