IB Computer Science (CS) HL Internal Assessment Example

Consider adding a legend for symbols and explicitly marking the start and end nodes to improve the flowchart’s readability.

The flowchart lacks a standardized start/end symbol and legend, which can confuse readers about entry and exit points.

The flowchart provides a comprehensive overview of the system’s processes, showing user actions and decision points clearly.

Add association lines with multiplicities (e.g., 1-to-many) to show cardinality and strengthen the model’s clarity.

The UML class diagram lists attributes and methods thoroughly, demonstrating careful consideration of system functionality.

Relationships and cardinalities between classes are missing, making it hard to see how entities interact within the database.

Data flow arrows are not shown between components, which reduces visibility of inter-module interactions.

Consider annotating the diagram with data flow arrows or numbering to show how information moves between modules.

The structure diagram effectively decomposes the system into modules, clarifying high-level organization.

The sign-up prototype specifies field validation rules clearly, aiding future implementation.

Add mock-ups for key error conditions (e.g., duplicate username) and specify layout adaptations for mobile screens.

The mock-up omits examples of error states (e.g., invalid email or mismatched passwords), which are crucial for UX design.

The login screen mock-up clearly identifies input fields and navigation elements, supporting usability.

Failure and loading states are not represented, leaving ambiguity about user feedback during authentication.

Include mock-ups showing invalid credential messages and spinner animations to capture a complete UX flow.

The submenu for “Play Game” is well organized, grouping related options logically.

Illustrate real-time updates to trophies and certificates in the incentives mock-up to reflect system behavior.

The incentives screen mock-up shows rewards but lacks demonstration of how counters dynamically update.

The questions list lacks sorting or filtering controls, which would improve the user’s ability to find specific items.

Use distinct styling (e.g., italics or color) for hint sections to improve readability and user guidance.

Incorporate dropdown filters by topic or difficulty and allow column sorting to enhance manageability.

The quiz details screen presents all question properties, including hints and level, in a clear layout.

Hint text is not visually distinguished, which may confuse users about its purpose versus main content.

The specific question view neatly displays answer keys and hints, aiding teachers in evaluation.

Menu items are not annotated with required permission levels, risking ambiguity in access control.

The login history table displays comprehensive fields for auditing user sessions.

Propose adding search filters and pagination to the history screen to maintain performance as data scales.

The teacher main menu mock-up clearly differentiates educator functions from student views.

Annotate which menu options require teacher privileges versus those open to all users.

No filtering or pagination controls are shown, which could limit usability when history records grow.

Consider adding an export button to allow teachers to download performance data for offline analysis.

No graph visualizations or trend lines are shown, missing an opportunity to depict performance over time.

Include a mock-up of a chart (e.g., line graph) to illustrate performance trends over multiple sessions.

The performance screen mock-up succinctly aggregates student scores and progress.