Cambridge A-Level ICT: Hardware and Software (9626)

This guide covers Section 2 Hardware and Software, for Cambridge International AS & A Level ICT (9626), 2025–2027 series. It is the second of 21 sections in the syllabus; AS Level candidates study Sections 1–11, of which this is one, and the full A Level adds Sections 12–21.

Where this fits in 9626

Having introduced data, information and the data-processing cycle in Section 1, Section 2 moves to the physical and logical machinery that processes that data — from the largest classes of computer (mainframes and supercomputers) down to the software layer that makes any computer usable, including the operating systems, utilities and interfaces a candidate will already have encountered informally.

Syllabus coverage

CAMBRIDGE A-LEVEL ICT (9626) — SECTION 2 HARDWARE AND SOFTWARE

• 2.1 Mainframe computers and supercomputers — characteristics including longevity, reliability/availability/serviceability (RAS), security, performance metrics (MIPS and FLOPS), volume of input/output/throughput, fault tolerance, operating system, number of processors and heat maintenance; uses of mainframes (census, transaction processing, industry and consumer statistics) and supercomputers (weather forecasting, climate research, quantum mechanics); advantages and disadvantages of each
• 2.2 System software — types and functions of system software (compilers, interpreters, linkers, device drivers, operating systems, utilities); how a high-level language is translated to run on different computer systems using interpreters and cross compilers; advantages and disadvantages of different types of system software
• 2.3 Utility software — the need for utility software including anti-virus, back-up, data compression, disk defragmentation (including the structure of hard disk storage), formatting (low-level, partitioning and high-level), file copying and deleting files; types of utility software (file management systems, disk management systems, data compression utilities) and their uses and trade-offs
• 2.4 Custom-written and off-the-shelf software — uses by individuals and organisations of each; advantages and disadvantages including degree of testing, level of support, cost and adaptability; proprietary versus open-source software
• 2.5 User interfaces — types including command line, graphical, dialogue and gesture-based interfaces; their uses and their advantages and disadvantages

How to approach it

Section 2 rewards knowing not just what each category of hardware or software is, but why an organisation would choose one option over another — nearly every sub-topic ends in “advantages and disadvantages,” which is where exam marks concentrate. Build revision around comparison tables (mainframe vs supercomputer, interpreter vs compiler, proprietary vs open-source, GUI vs command line) rather than isolated definitions.

The mainframe/supercomputer distinction is a common source of confused answers: both are large-scale systems, but mainframes are built for reliability and high-volume transaction throughput (census processing, banking), while supercomputers are built for raw processing speed on computation-heavy problems (weather modelling, quantum simulation). Keep the use case attached to each term when revising, not just the name.

RAS (reliability, availability and serviceability) is worth learning as a named term rather than three loose ideas: reliability is how rarely a system fails, availability is how much of the time it is usable (accounting for planned maintenance as well as failures), and serviceability is how quickly and easily it can be repaired when something does go wrong. Mainframes are built to score highly on all three because the transaction processing they run — census systems, banking — cannot tolerate long unplanned outages; fault tolerance (the ability to keep running, often in a degraded state, when a component fails) is a closely related idea worth distinguishing from simple reliability.

For system and utility software, be precise about the difference between the two: system software (2.2) manages and translates for the computer itself — operating systems, compilers, device drivers — while utility software (2.3) performs a specific maintenance task for the user, such as backing up or compressing files. Confusing the two categories in an exam answer loses marks even when the factual content about what the software does is otherwise correct.

Worked example: comparing software types

A question might ask candidates to justify whether a small design studio should buy off-the-shelf graphics software or commission custom-written software.

Off-the-shelf: lower cost, available immediately, well tested by a large
user base, but may include unneeded features and cannot be tailored
exactly to the studio's workflow.

Custom-written: matches the studio's exact requirements and can be
changed as needs evolve, but costs far more, takes time to develop and
test, and depends on ongoing support from the developer who built it.

A strong answer weighs both sides against the studio’s specific situation (budget, timescale, how unusual its workflow is) rather than asserting one option is simply “better.”

Common mistakes

Describing what a type of software or hardware does without giving its advantages and disadvantages, when the command word requires evaluation. Confusing system software with utility software, or a compiler with an interpreter (a compiler translates and stores an entire program before execution; an interpreter translates and executes line by line, which is why development-stage code is often run through an interpreter first). Treating “mainframe” and “supercomputer” as interchangeable terms rather than distinguishing reliability/throughput-focused systems from raw-processing-speed systems. Naming a user interface type without matching it to a suitable real-world use, such as a command line interface for a systems administrator versus a graphical interface for a general consumer device.

Quick revision checklist

• Match each hardware/software category to a real use case, not just a definition.
• Keep system software (2.2) and utility software (2.3) clearly separated by function.
• Be ready to justify a choice between custom-written and off-the-shelf software for a given scenario.
• Know the four named interface types and one advantage and one disadvantage of each.

Official syllabus

Cambridge International AS & A Level Information Technology (9626) syllabus for 2025, 2026 and 2027 — cambridgeinternational.org.