Code Sheets, Exam Technique & Mistakes: Writing Pseudocode That Matches Mark Scheme Language (Copy)
Writing Pseudocode That Matches Mark Scheme Language (Cambridge Standard – O Level 2210 + IGCSE 0478)
Why Mark Scheme Language Matters More Than “Correct Ideas”
- Cambridge marks what is written, not what you meant
- In Paper 2:
- Correct logic written in non-Cambridge style can lose marks
- Slight wording mismatches can cost method marks
- Examiners compare answers directly against:
- Mark scheme pseudocode
- Accepted Cambridge keywords and structures
- Goal:
- Make your pseudocode look like it came from the mark scheme itself
What Cambridge Means By “Pseudocode”
- Pseudocode is:
- Structured English
- With fixed keywords
- No language-specific syntax (no Python, C, Java)
- Cambridge pseudocode is:
- Case-insensitive (but consistent case preferred)
- Line-based
- Indentation-based for structure
- Mixing styles:
- Is a common reason for lost marks
Absolute Golden Rule
- If Cambridge has a standard keyword, you must use it
- Alternatives that are “logically correct” may not be rewarded
Core Cambridge Pseudocode Keywords (Must Memorise)
Input / Output
- INPUT
- OUTPUT
Correct:
- INPUT name
- OUTPUT total
Incorrect (penalised):
- READ name
- PRINT total
- DISPLAY total
Written and Compiled By Sir Hunain Zia (AYLOTI), World Record Holder With 154 Total A Grades, 7 Distinctions and 11 World Records For Educate A Change O Level And IGCSE Computer Science Full Scale Course
Assignment Statements (Very Strict)
Correct Cambridge Form
- variable ← value
Accepted alternatives:
- ←
- =
Preferred:
- ←
Examples:
- total ← 0
- count ← count + 1
Common Penalised Forms
- total == 0
- total := 0
- total += 1
These are programming language syntax, not Cambridge pseudocode.
Variable Naming Rules That Match Mark Schemes
- Use:
- Meaningful names
- Lowercase or camelCase
- Avoid:
- Single random letters unless loop counters
Accepted:
- totalMarks
- studentCount
- found
Accepted loop counters:
- i
- j
Risky:
- x1, y2 without meaning
- Using reserved keywords as variables
IF, ELSE IF, ELSE (Exact Structure Required)
Correct Structure
- IF condition THEN
- statements
- ELSEIF condition THEN
- statements
- ELSE
- statements
- ENDIF
Common Mark-Losing Mistakes
- Missing THEN
- Writing ELSE IF instead of ELSEIF
- Missing ENDIF
- Using braces { }
Incorrect:
- IF x > 5
- IF (x > 5) {
Written and Compiled By Sir Hunain Zia (AYLOTI), World Record Holder With 154 Total A Grades, 7 Distinctions and 11 World Records For Educate A Change O Level And IGCSE Computer Science Full Scale Course
WHILE Loop (Condition Placement Matters)
Correct Structure
- WHILE condition DO
- statements
- ENDWHILE
Common Mistakes
- Missing DO
- Writing condition after loop body
- Using UNTIL with WHILE logic
Incorrect:
- WHILE (condition)
- WHILE condition
REPEAT UNTIL Loop (Most Miswritten Structure)
Correct Structure
- REPEAT
- statements
- UNTIL condition
Critical Rules
- Condition is checked after loop body
- Loop runs at least once
- No DO keyword used
Common Errors
- Writing:
- REPEAT UNTIL condition DO
- Treating it like WHILE
Written and Compiled By Sir Hunain Zia (AYLOTI), World Record Holder With 154 Total A Grades, 7 Distinctions and 11 World Records For Educate A Change O Level And IGCSE Computer Science Full Scale Course
FOR Loop (Inclusive Bounds – Very Important)
Correct Structure
- FOR i ← start TO end
- statements
- ENDFOR
Optional:
- STEP value
Example:
- FOR i ← 1 TO 10 STEP 2
Common Examiner Traps
- Forgetting ENDFOR
- Assuming end value is exclusive
- Using < instead of TO
Incorrect:
- FOR i = 1; i < 10; i++
Boolean Conditions (Exact Keywords)
Correct Boolean Values
- TRUE
- FALSE
Correct Boolean Operators
- AND
- OR
- NOT
Penalised Alternatives
- &&
- ||
- !
- true / false
Written and Compiled By Sir Hunain Zia (AYLOTI), World Record Holder With 154 Total A Grades, 7 Distinctions and 11 World Records For Educate A Change O Level And IGCSE Computer Science Full Scale Course
Arrays: Declaration And Indexing Language
Correct Declaration Style
- DECLARE arrayName[1:10]
Or:
- DECLARE arrayName : ARRAY[1:10] OF INTEGER
Correct Indexing
- arrayName[i]
Common Errors
- Starting index at 0 without specification
- Using parentheses:
- arrayName(i)
- Missing DECLARE entirely
Procedures And Functions (Language Matters)
Procedure
- PROCEDURE name(parameters)
- statements
- ENDPROCEDURE
Call:
- CALL name(arguments)
Function
- FUNCTION name(parameters) RETURNS dataType
- statements
- RETURN value
- ENDFUNCTION
Call:
- result ← name(arguments)
Common Examiner Penalties
- Returning value from procedure
- Missing RETURN in function
- Calling function with CALL
Written and Compiled By Sir Hunain Zia (AYLOTI), World Record Holder With 154 Total A Grades, 7 Distinctions and 11 World Records For Educate A Change O Level And IGCSE Computer Science Full Scale Course
Comparison Operators (Use Cambridge Forms)
Accepted
- =
- ≠
- <
- ≤
- ≥
Risky / Penalised
- ==
- !=
Output Formatting Expectations
- Output values only
- No commentary unless asked
- Strings in quotation marks
Correct:
- OUTPUT “Valid”
Incorrect:
- OUTPUT Valid
- OUTPUT “The value is valid”
Indentation And Layout (Affects Marks Indirectly)
- Clear indentation:
- Helps examiners see structure
- Poor layout:
- Causes misinterpretation
- Can lose structure marks
Cambridge does not mark indentation directly, but:
- It affects clarity-based marking decisions
Mixing Programming Languages With Pseudocode (High-Risk)
Never write:
- if (x > 5)
- x++
- x += 1
- print(x)
Even if logic is correct:
- Marks may be lost
Written and Compiled By Sir Hunain Zia (AYLOTI), World Record Holder With 154 Total A Grades, 7 Distinctions and 11 World Records For Educate A Change O Level And IGCSE Computer Science Full Scale Course
How Examiners Decide If Language Is Acceptable
They ask:
- Is the intent unambiguous?
- Is Cambridge keyword used?
- Does structure match mark scheme?
If any answer is no:
- Mark may not be awarded
Safe Exam Strategy For Language Matching
- Memorise Cambridge templates
- Do not invent keywords
- Prefer longer, clearer structure over shorthand
- If unsure:
- Write full IF / ENDIF blocks
- Match wording from past paper mark schemes
Common Language-Based Mark Loss Summary
- READ instead of INPUT
- PRINT instead of OUTPUT
- Missing ENDIF / ENDWHILE / ENDFOR
- ELSE IF instead of ELSEIF
- Programming syntax instead of pseudocode
- Incorrect procedure/function usage
Final Quality Checklist
- Cambridge keywords only
- Correct structure endings
- No programming syntax
- Clear, readable layout
- Matches mark scheme phrasing
Final Lock-In Rules
- Logic earns marks only if language is acceptable
- Cambridge pseudocode is its own language
- Correct idea + wrong wording = lost marks
- Matching mark scheme language maximises Paper 2 scores