IB Computer Science (CS) SL Internal Assessment Example

The student provides a clear, well-contextualized scenario with a specific client and detailed household context, demonstrating thorough consultation evidence.

The rationale section states the desktop app solution but conflates SQL with SQLite. Clarify why SQLite is preferred over a full SQL server to fully justify the database choice.

Benchmarking existing apps is effective: the comparison to Tidy AI and Nipto highlights specific functional gaps and justifies the bespoke solution.

The rationale text mentions SQL generically; refine the explanation to distinguish SQL language features from the embedded SQLite engine.

The initial success criteria table lists six items but omits later criteria. Ensure all 15 success criteria appear together to demonstrate completeness.

Success criteria list covers a comprehensive range of CRUD, navigation, validation, notifications and gamification, all measurable and testable.

Record of tasks table is highly detailed and links actions to rubric strands, but row 8 lacks time estimate and target completion date. Fill in missing cells.

The task log clearly demonstrates a full development process with time estimates, dates and criterion references, evidencing meticulous planning.

Design overview figure is comprehensive, but adding a legend or key would improve clarity for non-technical stakeholders.

Design methodology explanation succinctly justifies an iterative, component-based approach aligned with modular requirements.

UI wireframes are comprehensive, but adding element labels or a legend would clarify interactive areas (buttons, tabs).

The entity-relationship schema is well laid out, but consider adding the task “status” field in the MEMBERS entity or explicitly describing its handling.

Leaderboard pseudocode clearly outlines the intended pyramid structure, but the loop lacks a currentRow increment and has minor syntax flaws.

Include automated unit tests for critical functions like email notification to strengthen the test plan beyond manual and visual checks.

The test plan meticulously maps every success criterion to specific test cases and methods, providing strong coverage.

In get_eligible_members, the query string uses an unmatched brace and misplaced placeholders; correct formatting to safely bind parameters.

The MVC architectural description is clear, justifying separation of concerns and maintainability effectively.

Tool choices are well justified: Python and Tkinter suit cross-platform GUI needs, and SQLite offers lightweight local persistence.

add_task code section has typos—“randome.choice” and misnamed variables—which will cause runtime errors. Correct naming to ensure functionality.

Time and space complexity analysis for member filtering is well explained as O(n), demonstrating solid understanding of algorithmic efficiency.

Excellent use of atomic transactions in mark_task_complete to maintain data integrity under error conditions.

Adaptive pyramid leaderboard code misuses “count - = i i := 1”; refine the loop logic and syntax for correct row construction.

The three-tier architecture separation of presentation, logic, and data layers supports straightforward extensibility and maintainability.

Evaluation table systematically assesses each success criterion and includes client feedback, demonstrating thorough product evaluation.

Recommendations are realistic and client-linked but could be strengthened by discussing resource and technical feasibility.