IB CS SL: The Content HL Papers Skip Entirely

Most IB Computer Science revision guides treat SL as "HL minus a few topics" and stop there. That's true for content, but it's not true for exam structure, IA expectations, or how the Case Study gets tested. If you're only doing SL, there are a handful of things that never show up when you're studying from HL-focused materials, because those materials assume you'll sit Paper 3 and go deeper into HL-only topics. This guide covers the parts that actually matter for the SL exam and moderation, not the shared syllabus content everyone already reviews.

Paper 1 vs Paper 2 weighting nobody explains clearly

SL students sit Paper 1 (multiple choice, 45 minutes, all topics plus the pre-released Case Study) and Paper 2 (structured questions, 1 hour 15 minutes, covering Topics 1-4 plus the Case Study). There is no Paper 3 at SL — that's HL-only and covers the extra HL topics (abstract data structures, resource management, control, and the extended Case Study material). A lot of confusion comes from students studying HL-only sample papers and wondering why the questions don't match what they've seen in class. If you're SL, ignore Paper 3 mark schemes entirely; they test content you're not responsible for.

The Case Study is worth more attention than most students give it. It's released months before the exam (usually around March for a May session) and forms roughly 25% of Paper 1 and a full compulsory section of Paper 2. Read the Case Study document at least three times before exams: once for comprehension, once annotating for technical vocabulary (specific system names, stakeholders, hardware/software mentioned), and once purely to memorize names and roles because Paper 2's Case Study section expects you to reference the scenario precisely, not generically.

The IA is graded differently than people assume

The Internal Assessment for SL and HL uses the same criteria (A through E: Planning, Solution Overview, Development, Functionality, and Evaluation) but SL students are expected to produce something with less complexity. Examiners aren't looking for a fewer number of features — they're looking at whether the complexity matches your actual skill level demonstrated in class work. A common mistake: SL students attempt an overly ambitious app with a database backend and multiple user roles, then can't explain their own code in the required screencast, tanking Criterion C (Development, worth 6 marks) and D (Functionality, worth 4 marks).

A better approach for SL: pick a client-facing problem you can fully explain in under 2000 words for the write-up, with a solution that has 3-5 clear, testable features. Video and audio evidence (Criterion C) needs to actually show the IDE, the running code, and your voice narrating decisions — not a slideshow after the fact. Moderators can tell the difference immediately.

Topic 4 (Computational Thinking and Program Design) gets underweighted in revision

Topics 1-3 (System Fundamentals, Networks, and Computer Organization) get the bulk of study time because they feel more "textbook." Topic 4 covers algorithms, pseudocode, and program design — dry-run tables, flowcharts, recursive vs iterative thinking, and Big-O style efficiency reasoning (though IB doesn't require formal Big-O notation at SL, just relative efficiency comparisons). This topic shows up constantly in Paper 2's structured questions because it's easy to write a scenario-based question around it.

Practice writing pseudocode by hand under time pressure. IB pseudocode conventions (using loop, end loop, if, then, else, end if) are specific and examiners deduct marks for inconsistent syntax even if the logic is correct. Do at least five past-paper Topic 4 questions from N19, M19, N18, and N17 sessions (avoid post-2020 papers if your syllabus changed, since the current guide dates from the 2014 syllabus first examined 2016, with the current version examined through 2024 sessions before the new syllabus took over).

Networks (Topic 2) questions favor specific vocabulary over general understanding

s SL students often understand networking conceptually but lose marks because Paper 2 wants named terms: circuit switching vs packet switching, specific protocol layers, or the difference between a MAC address and IP address stated precisely. Build a one-page glossary of Topic 2 terms with one-sentence definitions in IB phrasing, pulled directly from the subject guide's glossary section, and quiz yourself on it separately from your conceptual notes.

If you want more structured breakdowns of syllabus content, algorithm walkthroughs, or IA planning support, check the other Computer Science and Tutoring segments on Korra Studio.