Q: Opening or closing text files without enclosing literal filenames in quotation marks, e.g. writing OPENFILE Stock.txt instead of OPENFILE "Stock.txt".

Treat literal filenames as strings in all file pseudocode blocks. Always write OPENFILE "filename.txt" FOR READ/WRITE.

Q: Declaring class fields as public during Paper 4 OOP tasks, ignoring the requirement that attributes must be private.

Always declare class attributes as private (e.g., using two leading underscores in Python '__AttributeName' or using private modifier in Java/VB). Access them solely via getter and setter methods.

Q: Failing to implement index wrap-around in circular queue functions, leading to linear out-of-bounds pointer increments.

Apply modular arithmetic when incrementing the head or tail pointers of circular queues: Pointer <- (Pointer + 1) MOD MaxQueueSize.

Q: Omitting conditional loop terminators (such as ENDWHILE, ENDIF, and ENDPROCEDURE) in Paper 2 handwritten pseudocode.

Develop a structured habit of writing the terminating keyword (e.g., ENDIF) at the same time you write its opening keyword (e.g., IF), keeping formatting indented and balanced.

Q: Conflating direct and indirect addressing modes in assembly language tracing, loading actual addresses rather than target pointers.

Remember that LDI (indirect load) looks up the value inside the memory address, treats that value as a new target address, and then loads data from that target address.

Q: Failing to specify parent-class constructors using 'super().__init__()' when constructing derived subclass objects in Python during Paper 4.

In OOP inheritance, always make sure to call parent constructor explicitly from the child class constructor using super().__init__(parameter1, parameter2).

Question 1

Using procedural language 'OUTPUT' or print commands inside functions instead of utilizing the 'RETURN' keyword.

Accepted Answer

Always check the subroutine header. If it is a FUNCTION, it must use RETURN to send back a value. Use OUTPUT only for procedures or when explicitly asked to print directly.

Question 2

Attempting to use the string concatenation operator '+' in pseudocode instead of the standard ampersand '&' operator.

Accepted Answer

Remember that pseudocode is language-agnostic. Use the ampersand '&' for all string concatenations (e.g., ResultString <- String1 & String2).

Question 3

Opening or closing text files without enclosing literal filenames in quotation marks, e.g. writing OPENFILE Stock.txt instead of OPENFILE "Stock.txt".

Accepted Answer

Treat literal filenames as strings in all file pseudocode blocks. Always write OPENFILE "filename.txt" FOR READ/WRITE.

Question 4

Declaring class fields as public during Paper 4 OOP tasks, ignoring the requirement that attributes must be private.

Accepted Answer

Always declare class attributes as private (e.g., using two leading underscores in Python '__AttributeName' or using private modifier in Java/VB). Access them solely via getter and setter methods.

Question 5

Failing to implement index wrap-around in circular queue functions, leading to linear out-of-bounds pointer increments.

Accepted Answer

Apply modular arithmetic when incrementing the head or tail pointers of circular queues: Pointer <- (Pointer + 1) MOD MaxQueueSize.

Question 6

Omitting conditional loop terminators (such as ENDWHILE, ENDIF, and ENDPROCEDURE) in Paper 2 handwritten pseudocode.

Accepted Answer

Develop a structured habit of writing the terminating keyword (e.g., ENDIF) at the same time you write its opening keyword (e.g., IF), keeping formatting indented and balanced.

Question 7

Conflating direct and indirect addressing modes in assembly language tracing, loading actual addresses rather than target pointers.

Accepted Answer

Remember that LDI (indirect load) looks up the value inside the memory address, treats that value as a new target address, and then loads data from that target address.

Question 8

Failing to specify parent-class constructors using 'super().__init__()' when constructing derived subclass objects in Python during Paper 4.

Accepted Answer

In OOP inheritance, always make sure to call parent constructor explicitly from the child class constructor using super().__init__(parameter1, parameter2).

試験	時間	配点	問題数	配点比率	出題形式
Paper 1 Theory Fundamentals	1時間 30分	75	8	25%	Short Answer / Definition, Logic Circuit and Truth Table Drawing, SQL and Database Definition, Assembly Logic Tracing
Paper 2 Fundamental Problem-solving and Programming Skills	2時間	75	8	25%	Tracing Logic and Dry Run Tables, Structure Charts and State Diagrams, Syllabus Pseudocode Writing
Paper 3 Advanced Theory	1時間 30分	75	13	25%	Advanced Math Representation / Float and K-Maps, Architecture Explanations & Protocols, RPN Evaluation / Dijkstra calculations, Syllabus Stack Declarations / Initialisations
Paper 4 Practical	2時間 30分	75	3	25%	OOP Class Structure / Inheritance Declaring, Linear / Queue manipulation logic implementation, Recursive iteration counting code block, String Custom Processing Engine without split()

Computer Science (9618) 試験対策

試験の概要

電卓プログラム

Table mode for roots & turning points

Statistics mode (mean, SD & regression)

Carry exact values with Ans & memory

Equation solver — to CHECK your working

よくあるミス

コツを高得点につなげよう