Cambridge IAL Computer Science study plan
Cambridge IAL Computer Science · Give each week a clear focus.
8 weeks · About 6 hours per week
Computational thinking & Computer architecture and hardware
Decompose three past-paper algorithm scenarios into inputs, processes and outputs before writing any pseudocode
Write and trace pseudocode for linear and binary search, stating the precondition binary search requires and the worst-case comparison counts for n = 8, 16 and 1000
Build a one-page table mapping each stage of the fetch-decode-execute cycle to the registers and buses involved
Draw the stored-program von Neumann model from memory and label the address bus, data bus and control bus with their direction and width
Your checkpoint
A hand-traced workbook of five algorithms (two searches, two sorts, one recursive routine) with comparison counts and register/bus annotations, marked against mark-scheme wording
Computational thinking & Computer architecture and hardware
Convert five prose problems into flowcharts or pseudocode and justify the chosen data structures
Compare bubble sort, insertion sort and quicksort on time complexity, stability and best/worst case, giving a worked trace of each on the same eight-item list
Explain how pipelining, cache and clock speed affect performance, using a concrete numeric example for each
Distinguish RISC and CISC with at least three architectural differences and one consequence for instruction length
Your checkpoint
A 900-word comparison sheet on sorting algorithms and processor performance, plus a timed 45-minute past-paper question set scored against the mark scheme
Programming paradigms & Computational thinking
Write the same small task (for example, summing a list and filtering even values) in imperative, object-oriented and functional styles, annotating what each style makes easy or awkward
Define class, object, encapsulation, inheritance and polymorphism and show each in a short code fragment
Describe the role of a compiler, interpreter and assembler, then explain how a compiler translates high-level code through lexical analysis, syntax analysis, code generation and optimisation
Trace a recursive function by hand, showing the call stack at each step, and state the base case and the risk of stack overflow
Your checkpoint
A three-style code portfolio for one task with a 400-word reflective comparison, plus one hand-traced recursion showing the full call stack
Programming paradigms & Computational thinking
Distinguish procedural, object-oriented and declarative paradigms with a use case justifying each choice
Write and debug a program of at least 60 lines that reads input, validates it and handles at least two error cases
Explain the difference between a syntax error, a runtime error and a logic error, and describe one debugging technique for each
Describe how abstraction and decomposition reduce complexity in a program you have written
Your checkpoint
A working 60-line program with validation and error handling, a test log of at least six cases including two invalid inputs, and a 300-word design justification
Communication & Data representation and structures
Compare circuit switching and packet switching, naming two advantages of each and where each is used in practice
Explain the TCP/IP four-layer model and place at least six protocols (HTTP, HTTPS, FTP, SMTP, DNS, IP) at the correct layer with their purpose
Convert between binary, denary, hexadecimal and BCD for five values, showing each step
Explain how a bitmap image's file size is calculated from resolution and colour depth, and compute the size for three given images
Your checkpoint
A network and data-representation revision pack: one labelled protocol table, one switching comparison, and ten fully worked conversion and file-size calculations checked against answers
Communication & Data representation and structures
Describe how a URL is resolved by DNS and how an HTTPS request reaches a web server, naming each step in order
Explain the purpose of a MAC address, an IP address and a port number, and state one difference between IPv4 and IPv6
Perform two's complement subtraction on three pairs of 8-bit numbers and identify overflow in each case
Explain how sound is sampled and reconstructed, and compute the file size of a sound clip given sample rate, resolution and duration
Your checkpoint
A 12-question self-test on networking and number/sound representation, completed under timed conditions, with every wrong answer rewritten as a corrected one-line rule
Data representation and structures & Computational thinking
Implement a stack, a queue and a linked list in code and state one realistic use for each
Compare an array and a linked list on access time, insertion time and memory overhead, with reasons
Perform insertion and search on a binary search tree of at least ten nodes and state the traversal order produced by pre-order, in-order and post-order
Apply a hashing function to five keys and explain how collisions are resolved by chaining or open addressing
Your checkpoint
A data-structures implementation file containing stack, queue, linked list and BST code with a short test output for each, plus one hand-drawn tree with all three traversal orders
Computational thinking & Programming paradigms & Communication & Computer architecture and hardware & Data representation and structures
Complete two full past papers under exam timing and mark them strictly against the published mark scheme
List every recurring error from the marked papers and rewrite each as a rule you can recall in the exam
Re-derive from memory the calculations you are most likely to be asked: image size, sound size, two's complement, and search comparison counts
Rehearse mark-scheme phrasing for explanation questions by rewriting three of your weakest answers in precise technical language
Your checkpoint
Two completed and self-marked past papers with a one-page error log and corrected model answers for every lost mark
Milestones
Week 2: You can trace a binary search and a sort on unfamiliar data and state the number of comparisons without referring to notes
Week 4: You have a working, validated program of at least 60 lines and can explain your design choices in 300 words
Week 6: You score at least 70% on the timed networking and representation self-test and can state why each wrong answer was wrong
Week 8: You score at least 75% on both timed past papers, with the error log showing no repeated mistake across the two papers