Introduction to the IA — IB Computer Science

Welcome to the Computer Science Internal Assessment!

I'm going to start with a controversial statement: The Computer Science Internal Assessment can be fun! For the nerd in you, it is a good excuse to build a programming project where you learn new things, and create something that you can be really proud of. Past students regularly cite their CS IA extensively in their personal statements, and have commented to me that it was the thing they were most proud of and enjoyed the most from their time in CS.

You are going to get a couple of months of class time to make something cool of your own choosing!

Yes, it is an assessment. Yes, some of the documentation requirements can be a little onerous. But it can also be enjoyable. Embrace it, ensure you stay organised, and it will be ok. Mindset matters.

The IA is split into a few key phases:

Research and project choice
Initial planning and designing (Criterion A, B and C)
Programming a minimal viable product
Expanding on your MVP, taking it as far as you can
Documenting your development process and evading your achievement (Criterion D and E)

This pack has been designed to help guide you through the process, addressing many of the issues I've seen appear over the years. Please use it in conjunction with maintaining close collaboration with me.

Paul Baumgarten