IB Computer Science (CS) SL Internal Assessment Example

You identify a specific client and realistic operating context and support it with detailed consultation evidence, which gives the project a strong authentic foundation.

Your rationale links major product choices to the client’s needs, especially the need for a desktop tool with persistent data storage and an interface suitable for tournament management.

You propose a broad and relevant set of success criteria that covers core tournament workflow, validation, storage, and usability.

The product rationale is stronger on tool choice than on fully justifying the product’s design decisions against the client’s needs.

A few success criteria are still too vague or subjective to be tested cleanly, such as general error handling and intuitive use.

Some explicit client needs, such as flexible group composition and alternative tournament structures, are not yet fully captured in the criteria.

The submission includes a broad and coherent design overview with flowcharts, interface mock-ups, UML-style structure, and pseudocode, which clearly shows the intended development process.

The test plan covers a good range of normal and abnormal cases, including validation, match ordering, score submission, and settings-related behaviour.

The work shows that the product design has been thought through as a system rather than as isolated screens.

The task record is more of a planned schedule than a true record of completed development, so it does not fully demonstrate what actually happened during implementation.

Some parts of the design are not perfectly consistent with the later implementation, which weakens the sense of a fully complete development blueprint.

The test plan is detailed, but some tests would benefit from more precise inputs and boundary conditions.