Welcome to Your "Cheat Sheet" for the Case Study!

In the IB Computer Science course, the case study is a unique and exciting part of your journey. Unlike the rest of the exam where the questions are a surprise, the IB gives you the case study document several months before your final Paper \( 1 \) exam. This is your chance to become an expert on a specific real-world scenario before you even walk into the exam hall!

In this chapter, we will learn how to effectively read and tear apart the case study scenario so that you can predict what the examiners might ask. Whether you are an SL or HL student, these skills are essential because the case study now accounts for three specific questions in Paper \( 1 \).

Note: For details on how to link this to specific technical topics, see the next chapter, "Applying theme A concepts to the case study".

What exactly is the Case Study?

The case study is a document (usually a few pages long) published by the IB for each examination session (May and November). Its main purpose is to allow emerging technologies—things like new types of AI, smart cities, or advanced robotics—to be part of the course. Because technology moves so fast, the case study keeps the curriculum "future-facing."

Quick Review: Where does it appear?

  • Exam: Paper \( 1 \) (at both SL and HL levels).
  • Weight: There are \( 3 \) questions dedicated to the case study.
  • Focus: Evaluating the impact of technologies and applying computer science concepts to an unfamiliar situation.

Step-by-Step: How to Read the Case Study

Don't worry if the document looks intimidating or full of technical jargon at first. We are going to break it down using a simple three-pass method.

Step 1: The "Big Picture" Scan

Read the document from start to finish without taking notes. Try to answer these basic questions:

  • What is the main technology being discussed? (e.g., Is it about a database for a hospital or a machine learning model for weather?)
  • Who are the people involved? (These are your stakeholders).
  • Where is this happening? (A specific country, a business, or a global network?)

Step 2: Identifying the Stakeholders

In Computer Science, a stakeholder is any person or group affected by a system. When reading, use a highlighter to find every mention of a person or group.

Example: If the case study is about a new autonomous taxi service, the stakeholders might include:

  • The passengers (who want safety and ease of use).
  • The software engineers (who build the navigation algorithms).
  • The city council (who worry about traffic laws).
  • The local taxi drivers (who might lose their jobs—an economic impact).

Step 3: The "Terminology Hunt"

The IB loves to include specific technical terms in the case study. Some of these you will already know from Theme A (Concepts of computer science), but others might be new. Make a list of these terms and look up their definitions. If the case study mentions "Latency" or "Data Integrity," you can bet there will be a question asking you to define or apply them!

Key Takeaway: Treat the case study like a detective story. Every person mentioned and every technical word used is a clue for a potential exam question.

Analysing the Challenges and Constraints

No system is perfect. The case study will always hint at problems or limitations. These are often where the high-mark "evaluate" or "discuss" questions come from.

1. Technical Constraints

Look for limits in the hardware or software. Is the internet connection too slow (bandwidth issues)? Is the storage capacity too small? Does the machine learning model need more data to be accurate?

2. Ethical and Social Impacts

This is a favorite topic for the IB. Ask yourself:

  • Privacy: Is personal data being collected? How is it kept secure?
  • Equality: Does this technology leave some people behind (the "digital divide")?
  • Environment: Does the hardware use too much electricity or create e-waste?

Did you know? Under the new \( 2025 \) syllabus, the case study is designed to test your ability to "approach unfamiliar situations with creativity and resilience." This means you aren't just memorizing facts; you are learning how to think like a consultant!

A Simple Tool: The "PIES" Mnemonic

To make sure you've analysed the case study thoroughly, use the PIES acronym to categorize the impacts of the technology:

  • P - Personal/Social: How does it change people's daily lives or relationships?
  • I - Information/Technical: How does it handle data? Is it accurate and reliable?
  • E - Economic/Environmental: Does it save money? Does it hurt or help the planet?
  • S - Security/Ethical: Is it safe from hackers? Is it the "right" thing to do?

Common Mistakes to Avoid

  • Ignoring the "Small Print": Sometimes a single sentence about a backup system or a specific sensor is the key to a \( 4 \)-mark question.
  • Forgetting the Core Syllabus: Remember that the case study isn't a separate subject. The examiners will ask you to link the case study back to Theme A (Networks, Databases, etc.).
  • Over-researching: It is great to read around the topic, but don't memorize facts that aren't in the document. The exam questions will be based on the specific scenario provided by the IB.

Quick Review Box

1. What is the case study? A document reissued for every exam session focused on emerging tech.
2. Where is it tested? Paper \( 1 \), via \( 3 \) specific questions.
3. Who should you look for? Stakeholders (anyone affected by the system).
4. What should you look for? Terminology, technical constraints, and PIES impacts (Personal, Information, Economic, Security).

Remember: The case study is your friend! It’s the only part of the exam where you know the "topic" before you enter the room. Use that to your advantage!