Cambridge International A Level Information Technology Student book

If you are sitting Cambridge International A Level IT, this is the syllabus in book form, mapped chapter by chapter. It matters because IT questions reward precise vocabulary and method, not vibes; knowing what 'discuss' or 'evaluate' demands can swing whole grades. Teachers and self-study students get worked examples, practice questions, and exam technique in one place.

1. 1Chapter 1

   Spreadsheets do the maths so you can see the story

   Open the book and you are staring at a grid. Chapter 1 walks you through building a spreadsheet: entering data, writing formulas, and watching a single cell recalculate the whole sheet. The stakes are real because one wrong formula silently corrupts every number downstream. By the end you can format, sort, and chart the data, turning raw rows into something a reader can actually interpret.

   The idea

   A spreadsheet is not a calculator, it is a model. Change one input and every dependent value updates, which is exactly why businesses trust them for planning and exactly why errors propagate so dangerously. The skill examiners reward is knowing which function fits which task, and being able to explain your formula in words, not just type it.

   Try this: Build a small budget sheet this week: three columns, one SUM formula, one chart, then change an input and watch the chart move.

2. 2Chapter 2

   Databases: structure first, queries second

   Chapter 2 hands you a pile of related facts and asks how you would store them. The answer is a relational database: tables split sensibly, keys linking them, no duplicated data. You then learn to interrogate it with queries and produce reports. The payoff is a system where one record lives in one place, and every question you ask pulls from that single source of truth.

   The idea

   Good database design is about avoiding redundancy and keeping integrity, which sounds dry until you meet the alternative: the same customer's address stored in five places, updated in three. Normalisation is the discipline that prevents that. Examiners look for the vocabulary of primary keys, foreign keys, and validation, so learn the terms precisely.

   Try this: Take a club membership list and split it into two linked tables with a key, then write a query that joins them.

3. 3Chapter 3

   Sound, video, and images are all just numbers

   Chapter 3 opens the file formats drawer. You learn how bitmap images store pixels, how vector graphics store instructions, how sound is sampled, and how video frames stack up. Compression enters as the hero: lossy methods shrink files by discarding detail, lossless methods keep every bit. The outcome is that you can name a format, justify it, and estimate what quality it will deliver.

   The idea

   Every media file is a trade-off between size and fidelity, and the exam wants you to argue that trade-off explicitly. Knowing that lossy compression discards data permanently, while lossless reconstructs the original exactly, lets you answer 'why this format?' questions with confidence. File size calculations are a favourite exam task, so practise them until they are automatic.

   Try this: Save one photo as JPEG and as PNG, compare the file sizes, and write two sentences explaining the difference.

4. 4Chapter 4

   Two's complement and the binary world

   Chapter 4 goes under the hood: how computers represent numbers, text, and instructions in binary. You learn two's complement for negative numbers, how character sets like ASCII and Unicode map letters to codes, and how bit patterns mean different things depending on context. The stakes are that every file, every pixel, every keystroke is ultimately a binary pattern, and misreading the context corrupts it.

   The idea

   Representation is the layer where 'it's all just ones and zeros' stops being a cliché and becomes a working tool. Two's complement is the trick that makes subtraction free in hardware, and Unicode is why emoji survive a copy-paste. Exam questions love conversions and bit-depth calculations, so drill them by hand.

   Try this: Convert three negative numbers to 8-bit two's complement by hand, then check your answers with a calculator.

5. 5Chapter 5

   Networks: from one cable to the internet

   Chapter 5 builds a network from scratch in your head. You start with LANs and WANs, then the hardware: routers, switches, and the protocols that let them talk. The internet itself is framed as a network of networks, with IP addressing and DNS translating names into routes. The outcome is that you can trace, in principle, what happens when you type a URL and press enter.

   The idea

   Networking is layered abstraction: each piece of hardware and each protocol solves one problem and hands off to the next. That is why you can add a device to a Wi-Fi network without understanding the physics of radio. For exams, the skill is matching the correct device or protocol to the correct layer, and explaining data flow in order.

   Try this: Draw the path of a web request from your laptop to a server, naming every device and protocol along the way.

6. 6Chapter 6

   The effects of IT: jobs, health, and the digital divide

   Chapter 6 steps back from circuits to consequences. Automation changes which jobs exist; new roles appear while others shrink. Health risks like repetitive strain and eye strain come with the territory, and the digital divide separates those with access from those without. The chapter's outcome is a set of balanced arguments you can deploy in the 'discuss the effects' questions that examiners love.

   The idea

   The effects of IT are never purely good or bad, and the marks go to candidates who can argue both sides with specific examples. Equal access, changing employment patterns, and health and safety are the three pillars. Practise writing one paragraph for and one against, then a reasoned conclusion, because that structure scores.

   Try this: Pick one technology, write two paragraphs: one on its benefits, one on its harms, then a one-sentence judgement.

7. 7Chapter 7

   Databases at scale: SQL and the data warehouse

   Chapter 7 returns to databases with sharper tools. You learn SQL, the standard language for querying relational data, and how large organisations consolidate data into warehouses for analysis. Data mining then looks for patterns humans would miss. The outcome is that you can write a basic SELECT query and explain why businesses bother centralising their data at all.

   The idea

   SQL is worth learning because it is declarative: you describe what you want, not how to fetch it, and the engine optimises the rest. Warehousing exists because operational databases are optimised for transactions, not analysis, so you need a separate copy structured for questions. Exam questions often ask you to write or interpret simple SQL, so practise the syntax.

   Try this: Write a SELECT statement with a WHERE clause and an ORDER BY on any dataset you can find, and check the results.

8. 8Chapter 8

   Spreadsheets, modelling, and 'what if?'

   Chapter 8 pushes spreadsheets from record-keeping into simulation. You build models with goal seek and scenarios, asking 'what if sales drop 10%?' or 'what if interest rates rise?'. The stakes are decision-making: a good model lets a manager test options cheaply before committing money. The outcome is that you can build, test, and justify a model, which is a favourite exam practical task.

   The idea

   A model is only as good as its assumptions, and the exam wants you to identify both the power and the limits of spreadsheet modelling. Goal seek reverses the question: instead of calculating an outcome, you set a target and find the input that achieves it. Learn to name the tool and describe the scenario, because 'I would use goal seek' alone scores little.

   Try this: Use goal seek on a simple profit formula to find the sales figure that breaks even.

9. 9Chapter 9

   Authoring: getting a system built

   Chapter 9 follows a new system from idea to installation. You meet the system life cycle: analysis, design, development, testing, implementation, maintenance. Different approaches to development are compared, and documentation is written for both users and maintainers. The outcome is that you can describe each stage and say why skipping one, especially testing, is expensive.

   The idea

   The life cycle is the spine of the second half of the course, and examiners ask about it constantly. The insight is that maintenance is not an afterthought but the longest and costliest phase, because systems outlive the people who built them. Learn the stages in order and be ready to explain what artefact each one produces.

   Try this: Pick an app you use and sketch which life cycle stage it is probably in right now, with one sentence of evidence.

10. 10Chapter 10

    Hardware: input, output, storage, and the right tool

    Chapter 10 tours the physical kit. Input devices from keyboards to sensors, output from screens to actuators, and storage from magnetic to optical to solid state. The chapter's real question is selection: which device suits which task and why. The outcome is a decision framework you can apply to any scenario the exam invents.

    The idea

    Hardware questions are rarely 'what is a printer?' and usually 'which device, for this user, in this context, and justify it'. That justification is where marks live: speed, cost, capacity, durability, and suitability for the user's needs. Build the habit of naming at least two criteria in every hardware answer.

    Try this: Choose hardware for three scenarios: a warehouse, a graphic designer, and a visually impaired user, justifying each pick.

11. 11Chapter 11

    Security: keeping data safe from people and accidents

    Chapter 11 is the threat model. Malware, phishing, unauthorised access, and plain human error all get their moment, alongside the defences: firewalls, authentication, encryption, backups, and physical security. The stakes are that a single breach can destroy both data and trust. The outcome is a layered defence picture you can describe and evaluate.

    The idea

    Security is defence in depth: no single measure suffices, so you layer technical, physical, and procedural controls. Encryption protects confidentiality, backups protect availability, and authentication protects integrity of access. Exam questions often present a scenario and ask which measures apply, so practise matching controls to specific threats rather than listing everything.

    Try this: List the security measures protecting your own email account, and identify one layer you are missing.

12. 12Chapter 12

    Project management: planning the work, then working the plan

    Chapter 12 treats IT work as projects with deadlines and budgets. You meet Gantt charts, critical paths, and the vocabulary of milestones and dependencies. Risks are identified and mitigated before they bite. The outcome is that you can read a project plan, spot the critical path, and explain what happens if a task on it slips.

    The idea

    Project management formalises the difference between busy and productive. The critical path matters because a delay there delays everything, while a delay elsewhere may cost nothing. For exams, be ready to interpret a Gantt chart and explain why a task is or is not critical, using the language of dependencies.

    Try this: Plan a small task this week with three dependent steps, and identify which one is on your critical path.

13. 13Chapter 13

    Exam craft: command words and mark schemes

    The final chapters turn to the exam itself. You learn what command words like 'state', 'explain', 'discuss', and 'evaluate' actually demand, and how mark schemes reward structure. Worked examples show a weak answer and a strong answer side by side. The outcome is that you stop writing everything the same length and start matching depth to the marks available.

    The idea

    Command words are instructions, not decoration: 'state' wants one point, 'discuss' wants both sides, 'evaluate' wants a judgement. Candidates lose marks by answering 'discuss' with a list or 'state' with an essay. The fix is mechanical: read the command word, count the marks, and plan the shape of the answer before writing.

    Try this: Take three past-paper questions and, before answering, write down what each command word requires in one sentence.

14. 14Chapter 14

    Practical skills: the coursework and the paper

    The book closes with the practical assessment. You are walked through what the exam expects: extracting data, building a working solution, testing it, and documenting it. Time management is treated as a skill, not luck. The outcome is a checklist you can rehearse so the real assessment feels like a rehearsal you have already done.

    The idea

    Practical papers reward candidates who test as they go, not at the end, because errors found early are cheap and errors found late are fatal. Documentation is not an optional garnish; it is where method marks hide. Rehearse the whole sequence under time pressure at least once before the real thing.

    Try this: Do one timed practice task this week: build, test, and document a small solution in a single sitting.

Students preparing for Cambridge International A Level Information Technology, and teachers planning the course. Self-study candidates get the full syllabus plus exam technique in one volume.

FAQ