SS 1 Second Term

Lesson objectives

By the end of the week, learners should be able to:

1. Define pseudocode as an informal notation close to programming.
2. Distinguish the pseudocode keywords such as IF THEN ELSE.
3. Translate a simple verbal instruction into pseudocode.
4. Describe why pseudocode helps bridge human thought and code.
5. Explain the difference between pseudocode and code execution.

Key vocabulary

• Pseudocode: an informal notation closer to human speech than machine code.
• Notation: the symbols and keywords used in a language style.
• Keyword: a reserved word such as IF or ELSE in pseudocode.
• Bridge: the link between human thought and executable code.
• Verbal instruction: a spoken or written description of what to do.
• Informal notation: pseudocode looks like speech but reads like structured code.
• Translation: converting a verbal idea into structured notation.

Common misconceptions

• "Pseudocode is real code." Pseudocode executes in thought only, not on a computer directly.
• "Every keyword matters like real code." Pseudocode uses familiar keywords for clarity.
• "Pseudocode replaces a flowchart." Pseudocode often follows the flowchart structure.

Teacher activities

1. Starter: read a short verbal instruction aloud and ask learners to translate it into flowchart symbols.
2. Define pseudocode and name the most common pseudocode keywords.
3. Translate a verbal instruction step by step with IF THEN ELSE and a LOOP.
4. Show how pseudocode mirrors a flowchart visually.
5. Explain the bridge role in helping humans think in code.
6. Close with the translation task and exit question about execution.

Student activities

1. Listen to the starter and translate the verbal instruction into symbols.
2. Define pseudocode in their own words and list three common keywords.
3. Translate a verbal instruction into pseudocode using IF THEN ELSE.
4. Describe how pseudocode mirrors a flowchart visually.
5. Explain why pseudocode helps bridge human thought and code.
6. Answer the exit question in one sentence about execution.

Practical / learning evidence

Two translated pseudocode snippets compared against their source verbal instructions, plus a one-paragraph definition statement. Hand in both the snippets and the definition for marking.

Resources and preparation

Blank pseudocode templates, keyword cards and sample verbal instructions. Offline route: paper templates and cards, no device needed. Keep examples clean and avoid pseudocode that looks too much like real programming syntax.

Assessment for learning

Inspect the translated snippets for correct keyword usage. Compare each snippet with its source instruction for faithful translation. Ask a learner to explain the bridge role in their own words. Flag any learner who calls pseudocode executable code.

Inclusion and homework

Provide keyword cards preprinted for learners who need scaffolding and allow oral completion. Extend confident learners with three snippets and a bridge explanation homework. Homework: rewrite one verbal instruction without pseudocode keywords.