IB Computer Science IA - Student Guide

IB Computer Science Internal Assessment - Student Guide

What this page is based on

This guide is based directly on the official IB Computer Science Guide internal assessment section.
The aim here is to make the requirements quicker to read and easier for students to act on.

1. Purpose of the internal assessment

What the IA is

A compulsory computational solution
It brings together the two main themes of the syllabus
It should be woven into normal classroom learning, not treated as a separate unrelated task

What you must do

Select a topic within computer science
Specify a problem of your own choosing
Create a computational solution showing decomposition, pattern recognition, algorithmic thinking, programming, debugging, and testing

Weighting

SL: 30% of final grade
HL: 20% of final grade

Recommended time

35 hours in total
This includes teacher explanation, class work, consultations, progress monitoring, and authenticity checks

Key terms

Solution = the documentation plus video you submit
Product = the completed software only

2. Choice of problem and nature of the solution

What a good IA problem looks like

The problem should need a software solution with enough complexity and innovation for DP Computer Science level.
You must show organisational skills, algorithmic thinking, and the ability to code your own algorithms.
The IA should be of personal interest to you.

Allowed forms of solution

New system

OOP program
Interactive web app with database
Computer game
Mobile app
Simulation
Stand-alone application

Add functionality to an existing system

Connecting web pages to a database
Writing a Moodle plug-in
Adding meaningful new features to an existing system

Non-negotiable point

The solution must be coded by you
You must explicitly demonstrate and document algorithmic thinking

Inappropriate products

Copied or template-based work

Copied code with no significant modification
Website built from a template that predetermines the structure or layout
Use of exemplar products or templates such as the Northwind database in Access

Insufficiently original development

Copied computer game without major, properly documented modifications
Builder, wizard, or drag-and-drop tools with no real code development

Ethics problem

Any product that does not meet ethical requirements
Minor cosmetic changes to a template are not acceptable

3. Submission requirements

You must submit three files

Documentation

Single PDF file
Five separate sections: A-E
Maximum 2,000 words
Code excerpts, comments, and diagrams do not count
Write the overall word count clearly on the first page

Video

Separate file in mp4, avi, or wmv
Maximum 5 minutes
Must demonstrate the full functionality of your product
Must show examples of your testing strategy

Appendices

Single PDF file
Include the full source code of your product
Include any other resources you developed and referred to in the documentation
Not marked directly, but required for full marks in Criterion D

4. Guidance, authenticity, ethics, and teacher support

Authenticity and teacher support

The work must be entirely your own.
Your teacher can read and give advice on one draft only, either orally or in writing.
They will not edit it. The next version you hand in is the final version for submission.
You must not use the same piece of work for both the IA and the Extended Essay.

Ethical guidelines

Permissions

Obtain consent from anyone involved before starting
Obtain written consent if using an existing system

Data handling

Store all data securely
Maintain confidentiality
Use original data wherever possible
Collected data can only be used for this IA

School rules

Follow your school's health and safety guidelines
Make sure your process can survive authenticity checks

Authenticity checks may include

Your initial proposal
Your first draft
Your references
Your writing style
Plagiarism software

5. Assessment criteria - full breakdown

Overview

Criterion	Marks	Recommended words	Main focus
A: Problem specification	4	300	Problem scenario, success criteria, computational context
B: Planning	4	150	Decomposition and a plan linked to success criteria
C: System overview	6	150	System model, algorithms, and testing strategy
D: Development	12	1,000	Functionality, techniques, decisions, and testing
E: Evaluation	4	400	How well the success criteria were met and what should improve

Criterion A: Problem specification

Marks: 4
Recommended word count: 300 words

Marks	Level descriptor
0	Does not reach the standard below
1-2	Outlines a problem scenario States limited success criteria Outlines the nature of the solution in a computational context
3-4	Describes the problem scenario in terms of its measurable solution requirements States appropriate success criteria Explains the choice of computational context for the solution

Problem scenario means a clear description with measurable requirements.
Success criteria are measurable outcomes showing whether the product is successful.
These success criteria must be reused in Criteria B, D, and E.

Criterion B: Planning

Marks: 4
Recommended word count: 150 words

Marks	Level descriptor
0	Does not reach the standard below
1-2	Constructs a partial decomposition Constructs a plan that addresses some success criteria
3-4	Constructs a reasonable decomposition of the problem scenario Constructs a plan that addresses the success criteria of the solution

Decomposition means breaking the problem into smaller manageable components, often using diagrams.
The plan should show the chronology of planning, designing, developing, testing, and evaluating.
Common formats include Gantt charts and Agile charts.
You can include research such as code libraries you plan to use.

Criterion C: System overview

Marks: 6
Recommended word count: 150 words

Marks	Level descriptor
0	Does not reach the standard below
1-2	Outlines a limited system model Identifies algorithms for components Identifies a testing strategy for at least one success criterion
3-4	Constructs a system model that is not complete Constructs algorithms that lead to partial functionality Outlines a testing strategy that aligns with at least three success criteria
5-6	Constructs a complete system model Constructs algorithms that enable the product to perform Describes a testing strategy that aligns with the success criteria

System model means diagrams showing components, relationships, and the user interface. It does not include algorithms.
Algorithms can be shown in natural language, flowcharts, or pseudocode for each component.
Testing strategy is a systematic plan, often shown as a table of test data and expected outcomes.

Criterion D: Development

Marks: 12
Recommended word count: 1,000 words
This is the largest section.

Marks	Level descriptor
0	Does not reach the standard below
1-3	Very limited functionality No appropriate techniques to implement algorithms States choices made States the testing strategy used
4-6	Limited functionality At least one appropriate technique Outlines choices made States effectiveness of testing strategy
7-9	Partial functionality Uses some appropriate techniques Explains choices made Describes effectiveness of testing strategy
10-12	Fully functional product Uses appropriate techniques to implement algorithms Evaluates the choices made Justifies the effectiveness of the testing strategy

The video must show full functionality and testing examples.
Highlight key code elements with comments in the documentation and reference the full code in the appendices.
Techniques might include loops, data structures, libraries, or integration of tools.
Testing should cover correctness, reliability, and efficiency.

Criterion E: Evaluation

Marks: 4
Recommended word count: 400 words

Marks	Level descriptor
0	Does not reach the standard below
1-2	States the extent to which success criteria were met Describes improvements to the product
3-4	Evaluates the extent to which success criteria were met Justifies improvements to the product

6. Common student questions

FAQ

Can I use any programming language or only Python and Java?

Any language is allowed, including Python, Java, JavaScript, C++, C#, Swift, and others.
What matters is that you write the code yourself and clearly demonstrate algorithmic thinking.

Can I use existing libraries or code?

Yes, you may use libraries, but you must document and justify their use.
You cannot submit copied code or templates without major, properly documented modifications.

Can I make a web app, mobile app, database project, or game?

Yes. All are explicitly acceptable.
They must still be coded by you and meet the required complexity level.

Do I have to use OOP?

No. OOP is one valid approach, but it is not compulsory.

How complex does it need to be?

It must be commensurate with DP Computer Science level.
It should allow you to show innovation and clear algorithmic thinking.

Is the 2,000-word limit strict?

Yes. The limit is strict.
Code excerpts, comments, and diagrams are excluded from the count.
State the word count on the front page.

What must be in the video?

The full functionality of the final product
Clear examples of your testing strategy
Maximum length: 5 minutes

Can I work with others?

Collaboration is allowed in the broad sense, but the final product and documentation must be your own individual work.
Collusion is malpractice.

Can my teacher help me?

Yes. You are encouraged to discuss ideas and ask questions.
Your teacher gives feedback on one draft only.

What if I use AI tools?

All work must still be your own.
Any use of AI must follow your school's academic integrity policy and be referenced properly if used as a research tool.
The final code and documentation must be authentically yours.

7. Practical tips for success

What usually helps most

Start with a clear, measurable problem and success criteria. Everything else flows from this.
Use diagrams generously for decomposition, system models, and planning.
Keep the video focused and under 5 minutes. Plan exactly what you will show.
In Criterion D, justify why you chose particular structures and techniques, then evaluate them.
Link everything back to your success criteria.
Submit the full source code in the appendices if you want full marks in D.
Proofread for authenticity, word count, and clarity before submission.

Read the official PDF

Full document

If you want the full official wording, open the IA details PDF.