Introduction
The IB Computer Science IA isn’t just about coding — in fact, much of your mark comes from how well you document your process. Strong documentation shows examiners how you identified a problem, designed a solution, developed it step by step, tested it thoroughly, and reflected on the outcome. Many students lose marks because their documentation is incomplete or rushed.
In this guide, we’ll walk through how to structure your IA documentation, what the IB rubric expects, and how RevisionDojo helps you present your work clearly for maximum marks.
Quick Start Checklist
When writing IA documentation, make sure to include:
- Problem Identification – Describe the client’s needs and why your solution matters.
- Design – Flowcharts, diagrams, and planning documents that map your approach.
- Development – Annotated code snippets with explanations.
- Testing – A test plan with evidence of results and client feedback.
- Evaluation – Honest analysis of strengths, weaknesses, and future improvements.
Breaking Down the IA Documentation
1. Problem Identification
Start by introducing your client and the issue they face. Clearly explain why your project is necessary. This sets the foundation for your solution.
2. Design Section
Include:
- Flowcharts or UML diagrams
- Data structure choices
- Success criteria (linked to the client’s needs)
This section proves you planned before coding.
