Skip to content
9618Paper 3 · Advanced Theory§16.1, §16.2

16. System Software

Operating system internals — process management, scheduling algorithms, memory management (paging, segmentation, virtual memory) — and how compilers work (lexical, syntax, code generation, optimisation, RPN).

Read the Smart Notes Watch lectures (22)
Statometer63CoreNext Paper 392%
Marks a paper12.2 · 16%Rank#5 of 8 · #3 on P3Trend · last 12→Oct/Nov 24 · 31: 16 marksOct/Nov 24 · 32: 14 marksOct/Nov 24 · 33: 16 marksMay/Jun 25 · 31: 16 marksMay/Jun 25 · 32: 17 marksMay/Jun 25 · 33: 16 marksOct/Nov 25 · 31: 14 marksOct/Nov 25 · 32: 13 marksOct/Nov 25 · 33: 13 marksMay/Jun 26 · 31: 9 marksMay/Jun 26 · 32: 13 marksMay/Jun 26 · 33: 9 marks9 in 10 chance in the next paper

Everything for this topic — study hub

A2 Level · 9618 · Paper 3

Statometer — what 32 real papers say about this topic and each of its 3 syllabus bullets

Core · #5 of 8 in A2 Level · recomputed with every new session

63CORE
Core#5 of 8 in A2 Level#3 on Paper 3→ Steady

A regular, well-paid topic — you cannot afford a gap here.

Next Paper 3
92%
9 in 10 chance it is set
Marks a paper
12.2 / 75
16% of Paper 3 · fair share 17%
Appeared in
31 / 32
Paper 3 sittings 2021–2026
Last set
May/Jun 2026
9618/33 · Q7 · 9 marks · 11-series streak
Marks in each of the last 12 Paper 3 sittingsOct/Nov 24 → May/Jun 26
Oct/Nov 24 · 31: 16 marksOct/Nov 24 · 32: 14 marksOct/Nov 24 · 33: 16 marksMay/Jun 25 · 31: 16 marksMay/Jun 25 · 32: 17 marksMay/Jun 25 · 33: 16 marksOct/Nov 25 · 31: 14 marksOct/Nov 25 · 32: 13 marksOct/Nov 25 · 33: 13 marksMay/Jun 26 · 31: 9 marksMay/Jun 26 · 32: 13 marksMay/Jun 26 · 33: 9 marks

What the papers say

  • Set in 31 of 32 Paper 3 sittings on the current syllabus — treat it as certain.
  • Worth about 12.2 marks a paper (16% of Paper 3).
  • Last set May/Jun 2026 · 9618/33 · Q7 for 9 marks — in the most recent series.
  • Set in each of the last 11 series without a miss.
  • Steady at around 12.4 marks a paper year on year.
  • Lives on “Write” and “Explain” — 71% of its questions: you must produce something — code, a diagram, a table — practise doing it, not reading it.
  • Its biggest question so far: 13 marks (May/Jun 2022 · 9618/32 · Q4).
  • Inside the topic, §16.2 Translation software carries the most marks (72%) and §16.1 Memory management the least (7%).
  • It is examined mostly as AO1 (Knowledge & understanding, 59%), the rest AO2 (41%) — definitions and descriptions in syllabus words score.
  • The examiner has commented on 26 of its questions — read “What the examiner said” before you practise.

Command words

Share of questions using the word (a question can use several). What each wants →

Question shapes

  • ≤ 6 mk23
  • 7–9 mk29
  • 10–12 mk2
  • 13–15 mk1
  • 16+ mk0

Average 7 marks a question · 29% with a figure or table · 20% with code · biggest 13 marks

Assessment objectives — how it is examined

Every part of every current-syllabus question filed under Cambridge's AO1 / AO2 / AO3 (from its command word and what it asks you to do), so you know whether this topic pays for definitions, for applying, or for judging and building.

  • AO1 Knowledge & understanding
  • AO2 Apply & analyse
  • AO3 Design, program & evaluate

Paper 3 as a whole

Paper 3SyllabusMeasured
AO1 Knowledge & understanding60%54%
AO2 Apply & analyse40%46%
AO3 Design, program & evaluate0%0%

Syllabus = Cambridge's grid; measured = the bank's current-syllabus papers.

Inside the topic — every syllabus bullet, measured

Each part of each question is filed under the bullet it examines; the numbers are per Paper 3 sitting, exactly like the topic's. Open a bullet for its own Statometer.

  • 16.1Purposes of an operating system#11 of 14 on Paper 3Regular · 3949% next paper2.6 marks14/32 sittings→ May/Jun 2026

    Set most sessions for a few marks; know the definition and one example.Syllabus: maximising resource use; hiding hardware complexity; multi-tasking and process states; scheduling (round robin, SJF, FCFS, SRT); the kernel as interrupt handler

    Next Paper 3
    49%
    2 in 4
    Marks a paper
    2.6
    4% of the paper · 21% of the topic
    Asked in
    14 / 32
    Paper 3 sittings · 14 questions
    Last asked
    May/Jun 2026
    9618/32 · Q5 · 4 marks · 4-series streak
    • Asked in 14 of 32 Paper 3 sittings — roughly one paper in 2.
    • About 2.6 marks a paper (4% of Paper 3; 21% of the topic's marks across its 3 bullets).
    • Last asked May/Jun 2026 · 9618/32 · Q5 (4 marks) — in the most recent series.
    • Asked in each of the last 4 series.
    • Usually “Explain” or “Describe”: full sentences with a reason, not one-word answers.
    • Biggest chunk of marks so far: 9 in Oct/Nov 2022 · 9618/32 · Q9.
    • It is examined almost entirely as AO1 (Knowledge & understanding, 100%) — definitions and descriptions in syllabus words score.
    Last 12 sittings→ Steady
    Oct/Nov 24 · 31: 0 marksOct/Nov 24 · 32: 5 marksOct/Nov 24 · 33: 0 marksMay/Jun 25 · 31: 6 marksMay/Jun 25 · 32: 7 marksMay/Jun 25 · 33: 6 marksOct/Nov 25 · 31: 6 marksOct/Nov 25 · 32: 5 marksOct/Nov 25 · 33: 4 marksMay/Jun 26 · 31: 0 marksMay/Jun 26 · 32: 4 marksMay/Jun 26 · 33: 0 marks

    Assessment objectives

    • AO1 Knowledge & understanding
    • AO2 Apply & analyse
    • AO3 Design, program & evaluate
    • Explain57%
    • Describe50%
    • Identify29%
    • State29%
    Practise its 14 questionsBiggest: 9 marks · Oct/Nov 2022
  • 16.1Memory management#14 of 14 on Paper 3Occasional · 1318% next paper0.8 marks5/32 sittings→ Oct/Nov 2024

    Rotated in occasionally — the bullet students skip and then meet.Syllabus: paging, segmentation and virtual memory; the difference between paging and segmentation; page replacement; disk thrashing

    Next Paper 3
    18%
    1 in 5 or less
    Marks a paper
    0.8
    1% of the paper · 7% of the topic
    Asked in
    5 / 32
    Paper 3 sittings · 5 questions
    Last asked
    Oct/Nov 2024
    9618/33 · Q8 · 7 marks · 3 series ago
    • Asked in only 5 of 32 Paper 3 sittings — rare, which is exactly why it catches candidates out.
    • About 0.8 marks a paper (1% of Paper 3; 7% of the topic's marks across its 3 bullets).
    • Last asked Oct/Nov 2024 · 9618/33 · Q8 (7 marks), 3 seriess ago.
    • Usually “Explain” or “Describe”: full sentences with a reason, not one-word answers.
    • Biggest chunk of marks so far: 7 in Oct/Nov 2024 · 9618/31 · Q8.
    • It is examined almost entirely as AO1 (Knowledge & understanding, 100%) — definitions and descriptions in syllabus words score.
    Last 12 sittings→ Steady
    Oct/Nov 24 · 31: 7 marksOct/Nov 24 · 32: 0 marksOct/Nov 24 · 33: 7 marksMay/Jun 25 · 31: 0 marksMay/Jun 25 · 32: 0 marksMay/Jun 25 · 33: 0 marksOct/Nov 25 · 31: 0 marksOct/Nov 25 · 32: 0 marksOct/Nov 25 · 33: 0 marksMay/Jun 26 · 31: 0 marksMay/Jun 26 · 32: 0 marksMay/Jun 26 · 33: 0 marks

    Assessment objectives

    • AO1 Knowledge & understanding
    • AO2 Apply & analyse
    • AO3 Design, program & evaluate
    • Explain100%
    • Describe40%
    • State40%
    • Outline20%
    Practise its 5 questionsBiggest: 7 marks · Oct/Nov 2024
  • 16.2Translation software#1 of 14 on Paper 3Banker · 9692% next paper8.3 marks31/32 sittings→ May/Jun 2026

    Asked in nearly every paper — the bullet to know cold.Syllabus: how an interpreter executes code; compilation stages (lexical analysis, syntax analysis, code generation, optimisation); BNF and syntax diagrams; Reverse Polish Notation

    Next Paper 3
    92%
    9 in 10
    Marks a paper
    8.3
    11% of the paper · 72% of the topic
    Asked in
    31 / 32
    Paper 3 sittings · 39 questions
    Last asked
    May/Jun 2026
    9618/33 · Q7 · 9 marks · 11-series streak
    • Asked in 31 of 32 Paper 3 sittings — nearly every paper.
    • About 8.3 marks a paper (11% of Paper 3; 72% of the topic's marks across its 3 bullets).
    • Last asked May/Jun 2026 · 9618/33 · Q7 (9 marks) — in the most recent series.
    • Asked in each of the last 11 series.
    • Usually “Write” or “Show”: you must produce something — code, a diagram, a table — practise doing it, not reading it.
    • Biggest chunk of marks so far: 12 in May/Jun 2022 · 9618/31 · Q5.
    • It is examined mostly as AO2 (Apply & analyse, 59%), the rest AO1 (41%) — you must apply it to the given data or scenario — work it out, trace it, explain it in context.
    Last 12 sittings→ Steady
    Oct/Nov 24 · 31: 9 marksOct/Nov 24 · 32: 7 marksOct/Nov 24 · 33: 9 marksMay/Jun 25 · 31: 8 marksMay/Jun 25 · 32: 9 marksMay/Jun 25 · 33: 9 marksOct/Nov 25 · 31: 8 marksOct/Nov 25 · 32: 8 marksOct/Nov 25 · 33: 9 marksMay/Jun 26 · 31: 9 marksMay/Jun 26 · 32: 9 marksMay/Jun 26 · 33: 9 marks

    Assessment objectives

    • AO1 Knowledge & understanding
    • AO2 Apply & analyse
    • AO3 Design, program & evaluate
    • Write59%
    • Show44%
    • State31%
    • Explain28%
    Practise its 39 questionsBiggest: 12 marks · May/Jun 2022

4% of the topic's marks sit in question parts that belong to another topic (scenario questions cross sections) or that no bullet claims; they count for the topic, not for a bullet.

Marks a paper, year by year

212223242526

By exam series

  • May/Jun17/18 · 11.7 mk
  • Oct/Nov14/14 · 12.5 mk
Practise 55 real questions Smart Notes Quiz Flashcards Every topic on the Statometer

What you need to know3syllabus §16.1, §16.2

  1. 16.1Purposes of an operating system — maximising resource use; hiding hardware complexity; multi-tasking and process states; scheduling (round robin, SJF, FCFS, SRT); the kernel as interrupt handler
  2. 16.1Memory management — paging, segmentation and virtual memory; the difference between paging and segmentation; page replacement; disk thrashing
  3. 16.2Translation software — how an interpreter executes code; compilation stages (lexical analysis, syntax analysis, code generation, optimisation); BNF and syntax diagrams; Reverse Polish Notation

Video lectures22ZAK's YouTube channel · play here

  • ASA220231.0K views

  • A22023229 views

  • A22023275 views

  • A220231.5K views

  • A22023470 views

  • A220213.4K views

Open in the video library ZAK's channel

Infographics4draw these the way the examiner expects · download as PNG

How a compiler translates your codeFour stages — exam questions ask what each stage does and what it produces.Lexical analysissource → tokensstrip whitespace & commentsbuild symbol tableSyntax analysistokens checked against grammar (BNF)parse treesyntax errorsCode generationparse tree → object / machine codeOptimisationremove redundant code, reorder for speed / sizeInterpreter: translates and runs one statement at a time, stops at the first error. Compiler: whole program first.cswithzak.com

Compiler pipeline

A2
Process states & CPU schedulingA process = a program being executed, with its PCB (process control block). The scheduler decides whichREADY process runs next.READYwaiting for the CPURUNNINGusing the CPUBLOCKEDwaiting for I/O / eventdispatched by schedulertime slice ends / pre-emptedwaits for I/OI/O completesnew process admitted ↓finishes → terminatedA RUNNING process cannot go straight to BLOCKED→RUNNING: it must become READY first.Low-level scheduler: READY → RUNNING. High-level scheduler: which jobs are admitted to READY.AlgorithmIdeaFCFSfirst come first served; simpleSJFshortest job first; needs estimatesSRTshortest remaining time; pre-emptiveRound robintime slice each, in turn; fairPriorityhighest first; low may starvePre-emptive = the OS can interrupt a runningprocess (timer interrupt). Non-pre-emptive = itruns until it blocks or finishes.Why multitasking needs interruptsA clock interrupt ends the time slice; the kernel saves the registers in the PCB, picks the next READY process, restores its state.I/O interrupts move BLOCKED processes back to READY. Deadlock: two processes each wait for a resource the other holds.OS purposes: hide hardware complexity, manage resources (CPU, memory, I/O), provide a user interface, run applications.cswithzak.com

Process states & scheduling

A2
Memory management: paging, segmentation & virtual memoryRAM is shared by many processes. The OS maps each process's logical addresses onto physical frames — ordisk when RAM is full.Process (logical pages)page 0page 1page 2page 3Page tablepageframe05122disk37Physical RAM (frames)frame 0: otherframe 1: otherframe 2: P page 1frame 3: otherframe 4: OSframe 5: P page 0frame 6: otherframe 7: P page 3page 2 (swapped out)Disk — page filepage in on demandPagingMemory and process split into fixed-size pages/frames.Any frame will do → no external fragmentation, butthe last page is partly wasted (internal fragmentation).Pages are physical divisions, invisible to the programmer.SegmentationProcess split into variable-size logical segments (code,stack, data). Segment table holds base + limit. Naturalfor sharing/protection, but leaves gaps between segments(external fragmentation).Virtual memoryOnly the pages in use sit in RAM; the rest live in the page file on disk. A page fault loads the missing page,evicting another (page replacement: FIFO, LRU…). Benefit: programs bigger than RAM, more processes at once.Cost: disk is slow — disk thrashing when the OS spends its time swapping pages in and out instead of running code.“Describe how paging works” = pages, frames, page table, logical → physical mapping, swapped to disk when needed.cswithzak.com

Paging, segmentation & virtual memory

A2
BNF, syntax diagrams & Reverse Polish NotationBNF and syntax diagrams define what is legal (syntax analysis). RPN lets a compiler evaluate expressionswith a stack.Backus-Naur Form<digit> ::= 0|1|2|3|4|5|6|7|8|9<unsigned> ::= <digit>|<digit><unsigned><integer> ::= <unsigned>|-<unsigned>::= “is defined as” · | “or” · <…> = non-terminalRecursion (<unsigned> inside itself) allows any length.Syntax diagram for <unsigned>digitloop = one or more digitsCircles = terminals (literal symbols). Rectangles = non-terminals.Follow the arrows; any path through the diagram is valid.Reverse Polish Notation (postfix)(A + B) * C → A B + C *A + B * C → A B C * +Operator after its operands → no brackets or precedence needed.Evaluate 3 4 + 5 * with a stackreadstackaction33push43 4push+7pop 2, add, push57 5push*35pop 2, multiply, pushResult = the one value left on the stack. Convert infix → RPNwith the shunting-yard method or a binary tree (post-order walk).Where this sits in the compilerLexical analysis → tokens · Syntax analysis → parse tree, checked against BNF · Code generation → object code (RPN helps) · Optimisation.Optimisation: remove code that never runs, move loop-invariant calculations out of the loop, reuse computed values, use registers.“Is 123 a valid <integer>?” — walk the rules: 1 is a digit, 23 is an unsigned, so 123 is an unsigned → yes.cswithzak.com

BNF, syntax diagrams & RPN

A2

Browse all infographics →

Key terms12use these exact words in the exam

processschedulinground robinpagingsegmentationvirtual memorylexical analysissyntax analysisBNFsyntax diagramRPNoptimisation

Dotted terms are defined in the glossary.

Code help3referenced to the Cambridge pseudocode guide

Evaluate Reverse Polish Notation with a stack

pseudocode §3, §6.2 Run in Playground
DECLARE Tokens : ARRAY[1:5] OF STRING
DECLARE Stack : ARRAY[1:10] OF REAL
DECLARE Top, i : INTEGER
DECLARE A, B : REAL
Tokens[1] ← "3"
Tokens[2] ← "4"
Tokens[3] ← "2"
Tokens[4] ← "*"
Tokens[5] ← "+"      // 3 4 2 * +  ==  3 + 4 * 2
Top ← 0
FOR i ← 1 TO 5
   CASE OF Tokens[i]
      "+", "-", "*", "/" :
         B ← Stack[Top]
         A ← Stack[Top - 1]
         Top ← Top - 1
         CASE OF Tokens[i]
            "+" : Stack[Top] ← A + B
            "-" : Stack[Top] ← A - B
            "*" : Stack[Top] ← A * B
            "/" : Stack[Top] ← A / B
         ENDCASE
      OTHERWISE :
         Top ← Top + 1
         Stack[Top] ← STR_TO_NUM(Tokens[i])
   ENDCASE
NEXT i
OUTPUT "Result = ", Stack[1]

Round-robin scheduling simulation

pseudocode Run in Playground
DECLARE Burst : ARRAY[1:3] OF INTEGER
DECLARE i, Quantum, Clock : INTEGER
DECLARE Done : BOOLEAN
Burst[1] ← 5
Burst[2] ← 2
Burst[3] ← 4
Quantum ← 2
Clock ← 0
REPEAT
   Done ← TRUE
   FOR i ← 1 TO 3
      IF Burst[i] > 0 THEN
         Done ← FALSE
         IF Burst[i] >= Quantum THEN
            Clock ← Clock + Quantum
            Burst[i] ← Burst[i] - Quantum
         ELSE
            Clock ← Clock + Burst[i]
            Burst[i] ← 0
         ENDIF
         OUTPUT "t=", Clock, " ran P", i, " left ", Burst[i]
      ENDIF
   NEXT i
UNTIL Done

BNF for an integer

text
<digit>   ::= 0|1|2|3|4|5|6|7|8|9
<integer> ::= <digit> | <digit><integer>
<signed>  ::= <integer> | -<integer>

Playground examples1runnable program for this topic

  • Evaluate Reverse Polish Notation with a stack

    Operands are pushed; an operator pops two, applies itself and pushes the result — how a compiler evaluates RPN.

    A2PseudocodeStacks, queues, lists & trees 9618 §16.3
    Run

Test yourself

Ready to check you know it?

Every round is a fresh random draw, weak cards come back until you get them right, and past-paper questions come with their mark schemes. Marks earn XP on your dashboard.

Quiz: System Software (A2) (52)🃏 Flashcards: mix this topic (64)🖥️ OS — processes, scheduling & interrupts (25)🧠 OS — memory management (16)🔤 Compilation stages, BNF & RPN (23)Past-paper questions (55)⚙️ Reverse Polish & BNF (Compiler Lab)🗓️ Scheduling & paging simulator
Enroll nowOnline classes