Overall Examination Verdict

The May/June 2026 series for syllabus 9618 offers a comprehensive evaluation spanning foundational theory, algorithmic design, advanced computing paradigms, and hands-on coding. Across Papers 1, 2, 3, and 4, the demand is well balanced between standard textbook recall, algorithmic precision, and practical problem-solving.

Where the Marks Are Won and Lost

  • Paper 1 (Theory Fundamentals): Marks are heavily concentrated in relational database normalization and SQL queries (11 marks), image and sound representation (8 marks), and OS resource management (11 marks). Common mark losses occur when candidates confuse validation with verification techniques or neglect to specify table references when joining in SQL.
  • Paper 2 (Problem-solving & Pseudocode): High mark allocations are found in modular algorithm design (18 marks for string encryption and grid mapping) and stack operations (9 marks). Loss of marks often arises from boundary miscalculations in 1-based vs 0-based indexing and incorrect parameter passing modes (\(\text{BYVAL}\) vs \(\text{BYREF}\)).
  • Paper 3 (Advanced Theory): Essential marks reside in Dijkstra’s algorithm tracing (8 marks), Karnaugh map minimization and Boolean reduction (8 marks), and OOP class modeling (9 marks). Precision in notation (showing interim node weights and table states) is critical to capturing working marks.
  • Paper 4 (Practical Coding): Core marks stem from linked list maintenance using parallel/2D arrays (25 marks), OOP class implementation with validation loops (25 marks), and array searching/sorting routines (25 marks). Candidates forfeit easy marks by failing to include user-facing prompt strings or mismanaging exception blocks during file input/output.

Key Pitfalls and Strategy

Ensure rigorous differentiation between similar syllabus concepts (e.g., image vs screen resolution, serial vs sequential file organisation, symmetric vs asymmetric cryptography). In coding and pseudocode questions, pay meticulous attention to maintaining pointers when deleting or adding nodes in abstract data types, and ensure all specified parameter types and return contracts match the rubric precisely.