IB Computer Science HL study materials
IB Computer Science HL study resources

IB Computer Science HL study plan

IB Computer Science HL · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Internal assessment: computational solution

  • Decompose the IA computational solution into a problem statement, success criteria, and a testable client or user need, then get it signed off by your supervisor

  • Draft a project plan with dated milestones covering design, iterative development, testing, and evaluation, and map each milestone to the IB assessment criteria

  • Set up a version-controlled repository with a README, folder structure, and a running skeleton program that accepts input and produces output

  • Write the first design record: UML class or data-flow diagram plus a short justification of the chosen approach and its alternatives

Your checkpoint

A one-page IA project plan with signed-off success criteria, repository link, and a running skeleton program

Week 2

Internal assessment: computational solution & Abstract data structures (HL extension)

  • Implement the core data model of your IA solution using at least one abstract data structure, and document why that structure was chosen over an array or list

  • Write unit tests for the core data model before extending features, and record pass/fail results in a test log

  • Code a working implementation of a stack, queue, and binary search tree from scratch without library helpers, then compare your implementation against a library version

  • Trace insertion, deletion, and traversal algorithms on a hand-drawn tree of at least 10 nodes and verify the traces against your code

Your checkpoint

A test log with at least 15 unit tests, plus a working ADT implementation committed to the repository

Week 3

Abstract data structures (HL extension)

  • Implement and compare recursive and iterative versions of at least two algorithms, and measure their performance on increasing input sizes

  • Analyse the time complexity of each ADT operation you have written, and justify each Big-O claim with a counting argument

  • Implement a hash table with collision handling and evaluate its behaviour under a deliberately poor hash function

  • Solve five past-paper-style ADT trace questions under timed conditions and mark them against the mark scheme

Your checkpoint

A complexity analysis table covering every ADT operation, with measured timings supporting the Big-O claims

Week 4

Computational thinking, problem-solving and programming & Internal assessment: computational solution

  • Write pseudocode for every remaining IA feature and convert each into tested code, keeping the pseudocode in the documentation

  • Refactor the solution to separate logic from input/output, and add error handling for invalid user input

  • Complete a full pass of the programming fundamentals question style: trace loops, evaluate boolean expressions, and convert between pseudocode and a high-level language

  • Run a usability test with at least two real users and record their feedback verbatim

Your checkpoint

A feature-complete version 1.0 of the IA solution with a usability test report

Week 5

System fundamentals & Computer organization

  • Diagram the fetch-decode-execute cycle and explain the role of the program counter, instruction register, MAR, MDR, and ALU in a written answer of exam length

  • Compare von Neumann and Harvard architectures, and explain the purpose of the cache, buses, and clock in determining performance

  • Describe the function of primary and secondary storage, and evaluate at least three storage media against criteria such as speed, capacity, and durability

  • Explain how logic gates combine into half-adders and full-adders, and construct a truth table for a given circuit

  • Answer 10 short-answer questions on system fundamentals and computer organization, then mark them strictly

Your checkpoint

A hand-drawn CPU and memory diagram with a 400-word written explanation, plus a marked 10-question set with a list of gaps

Week 6

Networks & Control (HL extension)

  • Explain the OSI and TCP/IP models layer by layer, and map at least four protocols to the correct layers

  • Describe how a packet travels from a client to a server, including IP addressing, subnetting basics, routing, and DNS resolution

  • Compare network topologies and transmission media, and justify a network design for a given scenario

  • Explain the role of the operating system in process scheduling, memory management, and resource allocation, and compare at least two scheduling policies with worked examples

  • Describe how a virtual machine and a sandbox isolate processes, and evaluate the trade-offs of virtualization

Your checkpoint

A network design proposal for a small organisation, including topology diagram, protocol choices, and a 300-word justification

Week 7

Resource management (HL extension) & Control (HL extension)

  • Explain how the OS manages primary memory, including paging, virtual memory, and thrashing, and work through a page-replacement trace

  • Analyse the causes and detection of deadlock, and evaluate at least two prevention or avoidance strategies

  • Explain the purpose and mechanisms of control systems in the syllabus sense, including sensors, actuators, and feedback loops, and give a concrete example

  • Describe how concurrent processes are managed, including interrupts and polling, and compare their trade-offs

  • Answer 10 timed questions on resource management and control, and correct every error against the mark scheme

Your checkpoint

A worked page-replacement and deadlock scenario set with full solutions, plus a marked 10-question set

Week 8

Internal assessment: computational solution & Computational thinking, problem-solving and programming

  • Complete the IA evaluation criterion: critically evaluate the solution against the success criteria, and propose specific further improvements

  • Record and annotate a 5-minute video demonstrating the solution against each success criterion

  • Run two full timed mock papers covering all seven examined domains, and log every lost mark by domain

  • Revise only the two weakest domains identified by the mock papers, and re-test those topics the next day

Your checkpoint

A submission-ready IA package: code, documentation, video, and evaluation, plus a mock-paper mark log with a revision action list

Milestones

Week 2: IA repository contains a running skeleton with a documented data model, and you can trace a BST insertion and deletion by hand without notes

Week 4: IA solution is feature complete and has been tested by two real users; you score at least 60% on a timed programming-fundamentals question set

Week 6: You can draw the fetch-decode-execute cycle and the TCP/IP stack from memory, and explain a packet's journey end to end in under 5 minutes

Week 8: IA package is submission ready and both mock papers are completed under time, with a per-domain mark log showing improvement in your two weakest domains