A concept such as iteration is shared, but its notation and format belong to a profile: your code, exam year and paper arrangements. Tag each note with its profile so you practise the form your papers expect.
This lesson follows checking your centre and sits in digital versus paper route checking. For the notation itself, see pseudocode for the applicable syllabus.
What is the same, and what depends on the profile?
The idea does not change. A loop repeats steps, a variable keeps a running total, and a trace table shows each change. What can change is how you write it, which keywords are used and what the question asks you to do.
Your syllabus document and your centre decide the notation and format for your papers. Check them for your exam year before you commit to one form.
How do you tag a note step by step?
- Name the concept in plain words, for example “counting loop with a running total”.
- Write it in the form you are studying, pseudocode or Python.
- Add the profile tag: code, exam year, notation confirmed or unconfirmed.
- Trace it to prove you understand it.
- Rewrite it in the other form only if you need to read that form too.
Worked example
The concept is “add the first four even numbers using a loop”.
In pseudocode:
Total ← 0
FOR Count ← 1 TO 4
Total ← Total + Count * 2
NEXT Count
OUTPUT TotalIn Python:
total = 0
for count in range(1, 5):
total = total + count * 2
print(total)| Count | Total before | Count * 2 | Total after |
|---|---|---|---|
| 1 | 0 | 2 | 2 |
| 2 | 2 | 4 | 6 |
| 3 | 6 | 6 | 12 |
| 4 | 12 | 8 | 20 |
Both versions output 20. Check: 2 + 4 + 6 + 8 = 20.
Now the tag.
The concept is “counting loop with running total”. The note is written in pseudocode. Profile: “0478, exam year 2027, notation to confirm in syllabus document”.
If the student later confirms that papers use pseudocode, the tag changes to “confirmed”. If papers use Python, they rewrite the note and practise that form.
What mistake should you avoid?
Mistaken approach: a student studies only Python because their video course used it, and never checks which form their papers use.
If the papers use pseudocode, the student has practised the wrong notation. The idea transfers, but the exam wording, keywords and layout may not.
Correction: confirm the notation your papers use from your syllabus document and centre, then spend most practice time on that form.
A smaller slip in this example is writing range(1, 4) in Python. That runs only 1, 2 and 3, giving Total 12, not 20. The upper bound in Python stops before the number you write.
Check yourself
1. Trace this and give the output.
Total ← 10
FOR Count ← 1 TO 3
Total ← Total - Count
NEXT Count
OUTPUT TotalShow answer
Count 1: Total = 9. Count 2: Total = 7. Count 3: Total = 4. Output 4. Check: 10 - 1 - 2 - 3 = 4.
2. How many passes does for i in range(2, 6): make?
Show answer
It runs i = 2, 3, 4, 5, so 4 passes. The 6 is not included.
3. Write the profile tag for a note on “counting loop”, code 0478, year 2028, notation not yet confirmed.
Show answer
For example: “Counting loop. 0478, 2028, notation: to confirm.” Any tag that holds code, year and notation status is correct.
Where this leads next
Next, treat future 0265 availability as source-gated shows how to handle announcements about another code. Practise both forms in the pseudocode trace trainer and the Python sandbox.
If you want a teacher to check which form to drill, our online one-to-one Computer Science tuition can help.