What the guide clarifies
- Success criteria are measurable outcomes derived from the requirements and are reused in planning, development and evaluation.
- The computational context is the specific area of computing used. About 300 words is recommended.
From May 2027 the IB Computer Science IA is a computational solution: you choose a problem and design and code a software product using computational thinking. It is marked on five criteria, A–E (problem specification, planning, system overview, development, evaluation), out of 30, with the same criteria at SL and HL. It counts for 30% at SL and 20% at HL.
Updated 2026-11-09
| Criterion | Marks | What it assesses |
|---|---|---|
| A. Problem specification | 4 | Whether you set out the problem scenario with measurable requirements and success criteria, and explain the choice of computational context. |
| B. Planning | 4 | How you decompose the problem into components and whether the plan addresses the success criteria. |
| C. System overview | 6 | Whether the system model, the algorithms for its components and the testing strategy are complete enough for a third party to recreate the product. |
| D. Development | 12 | How functional the product is, the techniques used to implement the algorithms, how you justify implementation choices, and how effective the testing was. The heaviest criterion. |
| E. Evaluation | 4 | How you evaluate the product against the success criteria and justify improvements. |
| Total | 30 |
Based on the IB Computer science guide (first assessment 2027), section “Task descriptors and criteria—SL and HL”. Band descriptions are summarised in our own words; follow the official guide your school provides.
Whether you set out the problem scenario with measurable requirements and success criteria, and explain the choice of computational context.
| Marks | What the work shows |
|---|---|
| 0 | Does not reach the 1–2 descriptors. |
| 1–2 | Outlines the scenario; states limited success criteria; outlines the computational context. |
| 3–4 | Describes the scenario in terms of measurable requirements; states appropriate success criteria; explains the choice of computational context. |
Reaching the top band: Write each success criterion as something testable, with a number or clear pass condition, and argue why this computational context fits better than the alternatives.
How you decompose the problem into components and whether the plan addresses the success criteria.
| Marks | What the work shows |
|---|---|
| 0 | Does not reach the 1–2 descriptors. |
| 1–2 | A partial decomposition; a plan addressing some success criteria. |
| 3–4 | A reasonable decomposition; a plan addressing the success criteria. |
Reaching the top band: Map every component in the decomposition to specific success criteria, and mark which criteria each stage of the plan delivers.
Whether the system model, the algorithms for its components and the testing strategy are complete enough for a third party to recreate the product.
| Marks | What the work shows |
|---|---|
| 0 | Does not reach the 1–2 descriptors. |
| 1–2 | Outlines a limited system model; identifies algorithms; identifies a testing strategy for at least one success criterion. |
| 3–4 | Constructs an incomplete model; algorithms giving partial functionality; outlines testing for at least three success criteria. |
| 5–6 | Constructs a complete model; algorithms enabling the product to perform; describes testing aligned with the success criteria. |
Reaching the top band: Use three linked pieces: a component diagram, pseudocode per component and a test table in which each row traces to a success criterion and includes boundary and invalid input.
How functional the product is, the techniques used to implement the algorithms, how you justify implementation choices, and how effective the testing was. The heaviest criterion.
| Marks | What the work shows |
|---|---|
| 0 | Does not reach the 1–3 descriptors. |
| 1–3 | Very limited functionality; no appropriate techniques; states the choices; states the testing strategy. |
| 4–6 | Limited functionality; at least one appropriate technique; outlines the choices; states the effectiveness of testing. |
| 7–9 | Partial functionality; some appropriate techniques; explains the choices; describes the effectiveness of testing. |
| 10–12 | Fully functional; appropriate techniques; evaluates the choices; justifies the effectiveness of testing. |
Reaching the top band: Pick three or four code excerpts that show your algorithmic thinking; for each, explain why it is written that way, what alternatives you considered and the trade-off, then use test results to show it is reliable and efficient.
How you evaluate the product against the success criteria and justify improvements.
| Marks | What the work shows |
|---|---|
| 0 | Does not reach the 1–2 descriptors. |
| 1–2 | States how far the success criteria were met; describes improvements. |
| 3–4 | Evaluates how far the success criteria were met; justifies improvements. |
Reaching the top band: Go through each success criterion with evidence (test results or user feedback) and a verdict, then propose specific, feasible improvements for the ones not fully met, with reasons.
For each criterion the teacher chooses the band that best matches the work overall. Not every point in a band has to be met; when the work sits in different bands on different points, the mark reflects the balance.
The upper mark goes to work that largely meets the band and is close to the next; the lower mark to work that meets it to a lesser extent. Only whole marks are given.
A high mark on one criterion does not imply high marks on the others. The top band does not require faultless work.
Your teacher marks the work against the published criteria, and the IB moderates a sample, which can move marks up or down.
Up to the November 2026 session the Computer Science IA was marked out of 34: A planning 6, B solution overview 6, C development 12, D functionality and extensibility 4, E evaluation 6, and it required a real client. The new IA is out of 30, drops the client requirement, adds A problem specification, builds testing into C and D, and gives recommended word counts per criterion.
| Current criteria (2027 on) | Marks | Old criteria (to 2026) | Marks |
|---|---|---|---|
| A Problem specification | 4 | A Planning | 6 |
| B Planning | 4 | B Solution overview | 6 |
| C System overview | 6 | C Development | 12 |
| D Development | 12 | D Functionality and extensibility | 4 |
| E Evaluation | 4 | E Evaluation | 6 |
Want your Computer Science IA read against these criteria? Contact us: a tutor will go through your plan or draft criterion by criterion and tell you where the marks are going.
From 2027 it is out of 30: A 4, B 4, C 6, D 12, E 4, with the same criteria at SL and HL. It is 30% at SL and 20% at HL.
2,000 words, excluding code excerpts, comments and diagrams. Recommended: A 300, B 150, C 150, D 1,000, E 400.
The new criteria do not require a client; you choose the problem, which can come from the world around you, another field or a current computing issue.
No. The video, up to 5 minutes, shows functionality and testing; code belongs in the documentation and appendix.