Cambridge IGCSE ICT: Types and Components of Computer Systems (0417)

This guide covers Topic 1 Types and Components of Computer Systems, the first of 21 named topics in Cambridge IGCSE ICT (0417), for examination 2026-2028. This is the plain A*-G IGCSE, distinct from the numeric-grade Cambridge IGCSE (9-1) ICT 0983 sibling syllabus.

Where this fits in 0417

Topic 1 opens the syllabus, followed directly by Input and output devices and Storage devices and media, before moving into applied topics like Networks, ICT applications, Safety and security, and a substantial run of practical software topics (Document production, Databases, Spreadsheets, Presentations, Website authoring and more).

Syllabus coverage

CAMBRIDGE IGCSE ICT (0417) — TOPIC 1 TYPES AND COMPONENTS OF COMPUTER SYSTEMS

Topic 1 covers the different types of computer system (desktop, laptop, tablet, smartphone and embedded systems) and their typical uses, along with the core components that make up a computer system – distinguishing hardware from software and identifying the main internal and peripheral components candidates need to recognise throughout the rest of the syllabus.

How to approach it

Because this topic sets up vocabulary used continuously across all 21 topics, get comfortable distinguishing hardware from software and naming components precisely – vague answers here tend to cost marks throughout the paper, not just in Topic 1 questions. Comparing computer types by their suitability for different tasks (why a tablet suits one scenario and a desktop another) is a common exam angle, so practise justifying device choice for a given scenario rather than only describing device features in isolation. Since ICT exam questions are frequently scenario-based, practising past-paper questions that embed this topic’s vocabulary in real-world contexts is more useful revision than memorising definitions alone.

Official syllabus

Cambridge IGCSE ICT (0417) syllabus for examination 2026-2028 — cambridgeinternational.org.

Hardware and software

Hardware is the physical components; software is the programs that run on them.

Software divides into system software — the operating system, utilities, device drivers and compilers, which manage the computer itself — and application software, which performs tasks for the user: word processors, spreadsheets, browsers, databases.

The operating system manages memory, files, processes, input and output devices, and provides the user interface.

Main components

Component	Role
CPU	Processes instructions; contains the control unit, ALU and registers
RAM	Volatile, holds data and programs currently in use
ROM	Non-volatile, holds the boot instructions
Secondary storage	Non-volatile, permanent storage of files
Input devices	Get data into the system
Output devices	Present results

The distinction between RAM and ROM is examined constantly: RAM is volatile so its contents are lost when power is removed, and it can be written to freely; ROM is non-volatile and normally read-only.

Embedded systems are computers built into another device — a washing machine, a car engine management system — dedicated to one task, with the program usually held in ROM.

User interfaces

• Command line interface — the user types commands. Efficient and powerful for experts, but requires memorising commands and is unforgiving of typing errors.
• Graphical user interface — windows, icons, menus and pointers. Intuitive for beginners, but uses more memory and processing power.
• Dialogue and gesture-based interfaces — voice control and touch gestures, useful where hands or sight are occupied, but less reliable in noisy environments.

Storage

Magnetic storage (hard disk drives) uses magnetised platters: high capacity and low cost per gigabyte, but has moving parts and is vulnerable to shock.

Optical storage (CD, DVD, Blu-ray) uses a laser reading pits and lands: cheap and portable, but low capacity and easily scratched.

Solid state storage (SSD, memory cards, USB drives) uses flash memory with no moving parts: fast, silent, robust and low power, but dearer per gigabyte and with a finite number of write cycles.

Choosing storage in an exam answer means matching the property to the scenario — a laptop used in the field needs robustness, an archive needs capacity and cost.

Worked example

A school is buying tablets for fieldwork. Recommend a storage type and justify it.

Solid state (flash)

- no moving parts -> survives being carried and dropped in the field
- low power        -> longer battery life away from mains
- fast access      -> quick loading of apps and data
- lightweight      -> suitable for portable devices

Trade-off: higher cost per GB than a hard disk, but capacity needs are
modest for fieldwork data.

Naming the property and linking it to the scenario is what earns the marks; naming the technology alone does not.

Comparing computer types

Type	Typical strength
Desktop	Most powerful and upgradeable per unit cost, but not portable
Laptop	Portable with a built-in screen/keyboard, moderate power
Tablet	Very portable, touch-based, longer battery life, but limited processing power for heavy tasks
Smartphone	Most portable, always with the user, but smallest screen and least processing power
Embedded system	Built into another device for one fixed task, invisible to the user as a “computer”

An exam question asking you to “recommend a suitable device” for a described scenario is testing whether you can match these strengths to the scenario’s specific requirements (portability, processing power, screen size, battery life) rather than simply naming the most expensive or most modern option.

Common mistakes

Saying ROM stores “the operating system” — it holds the boot instructions that start loading it. Describing RAM as permanent storage. Confusing system software with application software. Listing interface types without advantages and disadvantages. Recommending a storage medium without justifying it against the specific scenario.

Quick revision checklist

• Distinguish hardware from software, and system from application software.
• State the role of the CPU, RAM, ROM and secondary storage, and contrast RAM with ROM.
• Define an embedded system and give examples.
• Compare command line, graphical and gesture-based interfaces.
• Compare magnetic, optical and solid state storage, and justify a choice for a given scenario.