The most damaging case study exam pitfalls are usually avoidable: students give generic computer science answers, neglect the Visionary Studios scenario, misread command terms, or reproduce memorized research without applying it. These mistakes matter because Paper 1 Section B tests whether you can use technical knowledge and independent research to reason within a specific situation, not merely recall facts about generative AI.
For the first assessment in 2027, the case study is examined in Paper 1 for both SL and HL. The 2027 scenario concerns Visionary Studios and generative AI for image creation, so effective preparation must connect technical concepts, practical decisions, stakeholders, and ethical issues to that company throughout each response.
What Paper 1 Section B requires in 2027
The revised IB Computer Science course has two external examination papers. According to the official IB Computer Science subject brief, Paper 1 focuses on Theme A: Concepts of computer science and includes questions related to the annually issued case study.
The IB curriculum update for Computer Science confirms an important change: the former HL Paper 3 has been removed, and the case study is now part of Paper 1 for both levels. All Paper 1 questions are compulsory.
| Feature | SL | HL |
|---|---|---|
| Paper 1 duration | 1 hour 15 minutes | 2 hours |
| Paper 1 weighting | 35% | 40% |
| Total Paper 1 marks | 50 | 80 |
| Case study section | 12 marks | 24 marks |
| Challenge questions studied | 2 | 4 |
| Expected depth | Focused application and supported explanation | Deeper research, synthesis and extended evaluation |
The challenge questions guide preparation, but they are not scripts for predicting the exact examination questions. Students must understand the underlying technology well enough to adapt their research to unfamiliar wording.
1. Giving a generic answer instead of using Visionary Studios
The most common mark loss occurs when an answer could have been written without reading the case study. A student might explain that generative AI can increase productivity, for example, but never identify what productivity means for Visionary Studios.
A contextualized answer would explain that faster image generation could allow the studio’s designers to produce more initial concepts, test several visual directions, or respond more quickly to client revisions. It might then qualify that benefit by considering inconsistent outputs, copyright uncertainty, or the time required for human review.
Use this simple pattern:
- State the relevant computer science idea.
- Connect it to a named feature, stakeholder, or decision in Visionary Studios.
- Explain the resulting consequence.
- Add a limitation or condition when the command term requires analysis.
Do not force the company name into every sentence. Context comes from specific application, not repeated naming.
2. Treating the case study as a memory test
Knowing definitions is necessary, especially for short-response questions, but definitions alone rarely complete an applied answer. If asked to explain a problem caused by biased training data, defining bias without tracing its effects on generated images leaves the reasoning unfinished.
A stronger response establishes a causal chain:
unrepresentative training data → recurring patterns in model outputs → stereotypical or exclusionary images → reputational and commercial risk for Visionary Studios
This chain shows why the technical issue matters. When revising, build similar chains for copyright, hallucination, prompt interpretation, computational resources, model transparency, privacy, output quality, and human oversight.
The RevisionDojo machine learning Questionbank can help students practise moving from definitions to applied analysis rather than stopping after factual recall.
3. Ignoring the command term
A technically accurate answer can still lose marks if it performs the wrong task. Identify, outline, explain, compare, discuss, evaluate, and justify require different forms of response.
| Command term | What the response should do | Frequent mistake |
|---|---|---|
| Identify | Give the requested name, feature, or point | Adding an unnecessary paragraph |
| Outline | Give a brief account or summary | Providing only a one-word label |
| Explain | Show how or why, usually through linked reasoning | Listing disconnected facts |
| Compare | Address similarities or differences using common criteria | Describing each option separately |
| Discuss | Present a considered, balanced review | Giving only advantages |
| Evaluate | Judge strengths and limitations against relevant criteria | Ending without a judgment |
| Justify | Support a choice or conclusion with evidence | Stating a preference without reasons |
Circle or underline the command term before writing. Then use the mark allocation to estimate the number and depth of developed points required, rather than assuming that one correct idea will earn every mark.
4. Blurring SL and HL expectations
Both SL and HL students study the case study, but they should not prepare as though the demands are identical. SL students investigate the two common challenge questions, while HL students also address two additional HL challenges and are expected to research the case study in greater depth.
An SL student does not need to fill an answer with advanced material simply because it appeared in an HL resource. Irrelevant complexity can obscure a direct answer. Conversely, an HL student who prepares only definitions and broad ethical points is unlikely to demonstrate the synthesis and depth expected in extended responses.
Use clearly labelled notes:
- SL core: terminology, scenario facts, two common challenges, relevant Theme A concepts, and concise applied explanations.
- HL extension: all SL material plus the two additional challenges, wider technical research, competing approaches, limitations, stakeholder trade-offs, and justified conclusions.
The RevisionDojo Computer Science resources for first assessment 2027 allow students to keep syllabus revision aligned with the correct course rather than accidentally relying on legacy Paper 3 materials.
5. Repeating research without integrating it
Independent research should strengthen an argument. Dropping a memorized company name, statistic, or article into an answer without explaining its relevance does not demonstrate meaningful understanding.
For each research example, prepare four elements:
- What happened or what the source established
- Which technical or ethical concept it illustrates
- How it relates to Visionary Studios
- What limitation prevents the example from proving too much
For example, a real dispute concerning AI-generated training material may illustrate copyright risk. The answer should then explain how uncertainty over training data or output ownership could influence Visionary Studios’ choice of model, client contracts, record keeping, or approval procedures.
Research notes should also distinguish reliable evidence from marketing claims. Prefer original documentation, reputable research, court or regulatory material, and technically credible reporting, while recording enough source information to recall the example accurately.
6. Writing one-sided evaluation
Students often interpret evaluate as “list advantages and disadvantages.” That creates two lists but not necessarily an evaluation. A strong response selects criteria, weighs evidence, and reaches a conclusion suited to the scenario.
Useful criteria for Visionary Studios could include:
- output quality and consistency
- speed and computational cost
- control over generated content
- copyright and licensing exposure
- bias and representation
- data privacy
- suitability for client requirements
- degree of human oversight required
A defensible conclusion might recommend adopting a model only for early concept generation, subject to human review and documented licensing conditions. This is stronger than claiming that one model is simply “best” because it recognizes that suitability depends on how the studio intends to use it.
7. Using terminology inaccurately
Technical vocabulary earns value only when it is correct. Students commonly blur training data with prompts, validation data with test data, generative models with conventional image-editing software, or bias with any output they personally dislike.
Create a terminology bank that contains three parts for every term:
- a precise definition
- a Visionary Studios example
- a related term with which it could be confused
For instance, a prompt is input supplied to guide generation, whereas training data is material used during model development to adjust learned parameters. Confusing them can undermine an otherwise thoughtful discussion of copyright or output control.
Use the RevisionDojo Computer Science study notes to review syllabus concepts, then test whether you can explain each term without copying the wording.
8. Mismanaging time and answer length
Some students spend too long reproducing case study facts and then rush the higher-value reasoning. Others write an extended essay for a short command term, using time that should have been reserved for another compulsory question.
Before writing, inspect three signals:
- the command term
- the mark allocation
- the scope of the question
For longer responses, spend a short period planning claims, counterarguments, evidence, and the final judgment. Paragraphs should each advance the analysis rather than restate the scenario.
Timed practice is essential because Paper 1 also contains Theme A questions. The RevisionDojo Computer Science Predicted Papers and Questionbank with Jojo AI feedback can be used to practise allocating time across a complete paper and identifying where answers become repetitive.
9. Preparing predicted answers instead of adaptable arguments
A memorized essay is fragile. A change in command term, stakeholder, proposed model, or decision criterion can make the prepared response only partly relevant.
Prepare argument modules instead. Each module should contain a claim, technical mechanism, Visionary Studios application, evidence, limitation, and possible judgment. You can then select and reshape the modules required by the actual question.
A useful practice method is to rewrite the same issue for three tasks: explain it, evaluate its significance, and justify a response to it. This reveals whether you understand the issue or have merely memorized one answer.
10. Failing to review why marks were lost
Completing many questions does not automatically improve technique. After each response, classify every lost mark as a knowledge gap, context gap, command-term error, unsupported assertion, terminology error, weak conclusion, or timing problem.
Keep an error log with one corrective action beside each entry. If the problem was generic application, rewrite the paragraph with two concrete Visionary Studios details. If it was weak evaluation, add explicit criteria and a conditional judgment.
Jojo AI can help identify recurring patterns, but feedback is useful only when followed by another attempt. The goal is to change the next response, not merely read comments on the previous one.
A final checklist for avoiding common mark loss
Before finishing a case study response, ask:
- Have I answered the exact command term?
- Have I used the mark allocation to control depth?
- Is my reasoning explicitly connected to Visionary Studios?
- Are my technical terms accurate?
- Have I explained consequences rather than listed facts?
- Is my research integrated into the argument?
- Have I considered limitations or competing perspectives where required?
- Does my conclusion follow from the analysis?
- Have I stayed within SL or HL expectations?
Conclusion
The largest source of common mark loss is not an absence of facts. It is the failure to turn knowledge into a relevant, technically accurate, and balanced response to the Visionary Studios scenario.
Prepare terminology carefully, organize research around the challenge questions, and practise adapting evidence to different command terms. RevisionDojo’s Study Notes, Questionbank, Predicted Papers, and Jojo AI feedback are most useful when combined in a repeated cycle of learning, timed application, diagnosis, and rewriting.
Sources and referenced URLs
- Official IB Computer Science subject brief for first assessment 2027
- Official IB Computer Science curriculum updates
- Official IB Diploma Programme Computer Science overview
- Overview of the 2027 IB Computer Science case study
- RevisionDojo Computer Science resources for first assessment 2027
- RevisionDojo Computer Science study notes
- RevisionDojo machine learning Questionbank
- RevisionDojo Questionbank
- RevisionDojo Computer Science Predicted Papers
- RevisionDojo guide to preparing for Computer Science Paper 1 and Paper 2
