O Level Computer Science: Software (Cambridge 2210)

Software is every program a computer runs, and Topic 4 of Cambridge O Level Computer Science (2210) asks you to sort it into two families, explain what the operating system does, follow an interrupt from signal to service routine, and explain how program code is turned into instructions a processor can carry out. Questions on Paper 1 are mostly short and definition-based, so the aim of this guide is to give you the exact ideas and the vocabulary examiners credit.

Where Topic 4 sits in 2210

Topic 4 is part of the “Computer systems” half of the syllabus (Topics 1–6), which is assessed by Paper 1, a 1 hour 45 minute written paper worth 75 marks, taken without a calculator. Cambridge built 2210 on the same subject content as Cambridge IGCSE Computer Science (0478), so the learning outcomes below are identical in both syllabuses. Topic 4 has two sub-topics: 4.1 Types of software and interrupts, and 4.2 Types of programming language, translators and integrated development environments (IDEs). It links back to Topic 3 (the processor checks for interrupts during the fetch–decode–execute cycle) and forward to Topics 7 and 8, where you write the code that translators process.

4.1 Two families of software

The syllabus separates software by who it serves.

• System software provides the services the computer itself requires. The syllabus names the operating system and utility software. Without system software, the hardware would have no way to load programs, store files or talk to devices.
• Application software provides the services the user requires — the jobs people turn on a computer to do, such as writing a report, editing a video, browsing the web or playing a game.

A quick test: imagine a computer with no user at all. Would this program still need to exist to keep the machine working? If yes, it is system software.

What the operating system does

The operating system (OS) is the most important piece of system software. The 2210 syllabus lists nine functions. Rather than memorising them as a list, connect each one to something you can see happening on a laptop or phone:

OS function	What it looks like in practice
Managing files	Saving a document into a folder, renaming it, deleting it
Handling interrupts	The pointer moves the instant the mouse moves, even mid-download
Providing an interface	The home screen, icons, menus or a command prompt
Managing peripherals and drivers	A new printer works after its driver is installed
Managing memory	Two open apps do not overwrite each other’s data in RAM
Managing multitasking	Music keeps playing while you type an essay
Providing a platform for running applications	Apps request storage, memory and screen access from the OS
Providing system security	Locking the screen; asking for a password before installing software
Managing user accounts	Each family member logs in to their own desktop and files

Hardware, firmware and the operating system

Learning outcome 4.1.3 describes a stack. Each layer can only run because the layer below it is already running:

1. The hardware is switched on.
2. The bootloader, which is firmware (software held permanently in the hardware), runs on the hardware and loads the operating system.
3. The operating system runs on the firmware.
4. Applications run on the operating system.

This explains why an app cannot run on a computer with no OS, and why the OS cannot start without the bootloader.

Interrupts

An interrupt is a signal sent to the processor to say that something needs attention. The syllabus wants three things: how an interrupt is generated, how it is handled using an interrupt service routine (ISR), and what happens as a result.

• Hardware interrupts are generated by devices — for example, pressing a key on the keyboard or moving the mouse.
• Software interrupts are generated by programs — for example, an instruction that tries to divide by zero, or two processes trying to access the same memory location.

When an interrupt is generated it is placed in a queue with a priority. The processor checks for interrupts as part of its cycle. If the new interrupt has a higher priority than the current task, the processor saves the current task’s state, runs the ISR for that interrupt, then restores the saved state and continues. The result might be a character appearing on screen, the pointer moving, or — for a serious software error — the program being stopped with an error message.

4.2 Programming languages and translators

High-level and low-level languages

A high-level language (such as Python, Java or Visual Basic) uses English-like keywords. A low-level language is either machine code (binary) or assembly language. The syllabus asks for advantages and disadvantages under four headings:

Heading	High-level language	Low-level language
Ease of reading and writing	Easier; statements look like English	Hard to read; mnemonics or binary
Ease of debugging	Easier to spot and fix errors	Harder
Machine independence	Portable to different processors	Tied to one processor type
Direct manipulation of hardware	Not possible	Possible — registers and memory locations can be controlled directly

Assembly language is a low-level language that uses mnemonics (short codes such as LDA for “load” or ADD). An assembler translates it into machine code.

Compilers and interpreters

Both translate high-level code into machine code, but in different ways.

• A compiler translates the whole code at once before it is executed and produces an executable file. If there are errors, it provides an error report for the whole code.
• An interpreter translates and executes the code line by line. When it finds an error it stops execution, so the error can be fixed before continuing.

The syllabus states the typical use: an interpreter is mostly used while a program is being developed, and a compiler is used to translate the final program. The executable from a compiler can be run again and again without the translator; the interpreter must be present every time the program runs.

Integrated development environments

An IDE brings the tools for writing programs into one package. The syllabus lists: code editors, a run-time environment, translators, error diagnostics, auto-completion, auto-correction and prettyprint. In an exam, pair each named function with what it does for the programmer — for example, error diagnostics highlight where an error is so it can be found quickly.

Worked example 1: what happens when a smart TV is switched on?

Explain how the hardware, firmware and operating system allow a streaming app to run on a smart TV. [3]

• When the TV is switched on, the bootloader, stored as firmware, runs on the TV’s hardware. [1]
• The bootloader loads the operating system, which runs on the firmware. [1]
• The streaming app is then run on the operating system, which gives it access to memory, the network and the screen. [1]

Worked example 2: two interrupts at once

While a user moves the mouse, a background program tries to write to a memory location already in use by another process. Classify each interrupt and say what happens.

The mouse movement is a hardware interrupt; the memory clash is a software interrupt. Both are sent to the processor with a priority. The processor handles the higher-priority interrupt first: it saves the current task, runs the ISR, and returns. The other interrupt waits in the queue and is then serviced the same way. The memory clash may cause the OS to stop one of the processes to protect the other’s data.

Worked example 3: choosing a language for a fitness tracker

A company is writing the code that reads the heart-rate sensor in a wristband with a small, fixed processor. Explain why a low-level language might be chosen.

Low-level code can directly manipulate the hardware, so the programmer can read the sensor’s registers and control memory exactly. Because the wristband’s processor will never change, the lack of machine independence does not matter here. The trade-off is that the code is harder to write and debug.

How to approach it

Learn the nine OS functions with a real example for each, because Paper 1 often asks you to apply them to a scenario. For interrupts, practise writing the sequence — generate, prioritise, save, run ISR, restore — in four or five short sentences. For translators, always compare both: one point about the compiler and the matching point about the interpreter.

Frequently asked questions

Is the 2210 Software topic the same as in IGCSE 0478? Yes. Cambridge uses the same subject content for 2210 and 0478, so the learning outcomes for Topic 4 are identical.

Is a device driver application software? No. A device driver lets the operating system manage a peripheral, so it is system software.

Why is an interpreter preferred while testing? It stops at the first error it meets and shows where it is, so the programmer can fix that line and run the code again straight away.

What counts as a software interrupt in 2210? The syllabus gives two examples: division by zero, and two processes trying to access the same memory location.

Official syllabus

Cambridge International, Cambridge O Level Computer Science (2210) syllabus for examination in 2026, 2027 and 2028: official syllabus PDF, Subject content, section 4 “Software” (4.1 and 4.2). Checked 2026-11-08.

Next steps: revise from the Software revision notes, then test yourself with the Software practice questions.