IB Computer Science (CS) HL Internal Assessment Example

Clear identification of an appropriate scenario (inefficient study-session tracking) and a relevant client (student user).

Reasonable rationale for choosing a custom GUI/DB tool over spreadsheets, highlighting automation and visualization benefits.

Well-defined success criteria covering data accuracy, UI responsiveness, persistence, chart rendering, and error handling.

Consultation evidence is limited—interview notes and iterative feedback are not thoroughly documented.

Product rationale lacks quantitative justification or comparison with alternative solutions.

Success criteria omit important aspects such as accessibility and cross-platform portability.

A coherent, date-stamped record of development tasks that illustrates the main stages of the process.

A comprehensive design overview—including a UML class diagram and MVC mapping—that clearly communicates the system architecture.

An outline test plan that addresses core functionalities and some edge cases.

The task log is incomplete in later stages, with summaries rather than detailed entries.

The test plan is rudimentary; several UI and boundary scenarios are not fully specified.

No pseudocode or activity diagrams are provided to supplement the narrative design.