IB Computer Science (CS) HL Internal Assessment Example

Clear identification of a real client and problem context with multiple email exchanges showing authentic consultation

Extensive, specific and measurable success criteria mapped directly to client requirements

Narrative remains largely descriptive and does not explore constraints or alternative solutions in depth

Rationale lists technologies with basic pros and cons but lacks explicit comparison with alternatives or strong linkage to client priorities

Inconsistent formatting of citations and missing URLs reduces documentary rigor

Comprehensive design overview including wireframes, data-structure tables and flowcharts that clearly explain component interactions

A basic but coherent test plan with normal and abnormal data cases, expected outcomes and rationales

Chronological record of tasks with dates and criterion links that shows development progression

Record of tasks remains generic, lacks evidence of iteration status or reflections on outcomes

Some dates overlap and planned outcomes are vague, reducing clarity of the timeline

Absence of an ER diagram limits understanding of data relationships