Computer Science · Computational Solution documentation (IA)
IB Computer Science IA Grader
Upload your Computational Solution documentation (IA) and get criterion-by-criterion feedback against the IB assessment criteria in the official IB Computer Science internal assessment (computational solution) criteria (first assessment 2027). Whether you are at Higher Level (HL) and Standard Level (SL), iBacalao shows where your draft meets the mark scheme and what to improve before formative submission. Free to start in the Mac app; sign-in is required to keep reviews and usage limits tied to your account.
IB assessment criteria — 30 marks total
Your Computational Solution documentation (IA) is graded against 5 criteria in the official mark scheme. iBacalao scores each one and tells you exactly where to gain marks.
Problem Specification
The problem scenario described in terms of its measurable solution requirements, appropriate success criteria stated as measurable outcomes, and the choice of computational context for the solution explained. (~300 words.)
Planning
A reasonable decomposition of the problem scenario (e.g. structure chart or hierarchy diagram) and a plan — a chronology covering planning, designing, developing, testing and evaluating — that addresses the success criteria. (~150 words.)
System Overview
A complete system model that a third party could use to recreate the product, algorithms for the system's components that enable the product to perform, and a described testing strategy aligned with the success criteria. (~150 words excluding diagrams and algorithms.)
Development
The built product: a fully functional product constructed with appropriate techniques to implement the algorithms, the implementation choices evaluated, and the effectiveness of the testing strategy justified. (~1,000 words; full source code in appendices; functionality demonstrated in the video.)
Evaluation
An evaluation of the extent to which each success criterion was met (fully, partially, not at all) supported by evidence, and justified improvements to the product, each tied to gaps identified in the evaluation. (~400 words.)
Common mistakes to avoid
The most frequent reasons students drop marks on each criterion.
Problem Specification
- Success criteria that aren't measurable ("the app should be easy to use")
- Problem scenario described without solution requirements
- Computational context named but the choice never explained
- Success criteria disconnected from the stated requirements
Planning
- Decomposition missing or a single flat list of features
- Plan with no link to the success criteria
- Timeline without dependencies or realistic scheduling
- Phases (testing, evaluating) absent from the chronology
System Overview
- System model too incomplete for a third party to rebuild the product
- Algorithms missing for key components, or buried inside the model
- Testing strategy not aligned to the success criteria
- UI shown but data/logic components unmodelled
Development
- Implementation choices stated but never justified or evaluated
- Techniques listed without explaining why they fit the algorithms
- Testing mentioned but its effectiveness never assessed
- Documentation that narrates code line-by-line instead of explaining decisions
Evaluation
- A met/not-met table with no evaluative prose behind it
- Improvements unrelated to the gaps the evaluation found
- Success criteria assessed without evidence from testing
- New features proposed instead of justified improvements
Common questions
How is the IB Computer Science Computational Solution documentation (IA) marked?
Your Computational Solution documentation (IA) is marked against 5 criteria totalling 30 marks using the official IB Computer Science internal assessment (computational solution) criteria (first assessment 2027): Problem Specification (/4), Planning (/4), System Overview (/6), Development (/12), Evaluation (/4). Each criterion has its own mark bands, and your teacher's marks are moderated by the IBO.
What are the most common mistakes in the IB Computer Science Computational Solution documentation (IA)?
The two criteria worth the most marks are where students lose the most. On Development: Implementation choices stated but never justified or evaluated; Techniques listed without explaining why they fit the algorithms. On System Overview: System model too incomplete for a third party to rebuild the product; Algorithms missing for key components, or buried inside the model. The full list for every criterion is above.
Which criterion is worth the most marks in the IB Computer Science Computational Solution documentation (IA)?
The highest-weighted criterion is "Development" and is worth 12 marks. The top mark band for this criterion is the most detailed, so missing any element it mentions is the fastest way to lose marks.
What is the word limit for the Computer Science Computational Solution documentation (IA)?
Word and page limits for the Computational Solution documentation (IA) are set in the official IB Computer Science internal assessment (computational solution) criteria (first assessment 2027) rather than being the same across subjects, so check your subject guide for the exact figure. Going over the limit risks examiners stopping at the limit and not marking what follows.
Can I use AI to help with my Computer Science IA?
The IBO allows AI for research support and feedback, but the submitted work must be entirely your own. iBacalao gives criterion-by-criterion feedback on your draft — the same kind of comment your teacher would give — without generating any text for your IA.