JSS 3 First Term

Lesson objectives

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

1. Write a program using variables, arithmetic and printing.
2. State why high-level languages suit school teaching.
3. Distinguish interpreters from compilers in behaviour.
4. Trace a simple program predicting the expected output.
5. Compare high-level languages on ease and readability.

Key vocabulary

• Programming language: a structured notation telling the computer what to do.
• Variable: a named container holding a value.
• High-level language: closer to human speech than machine code.
• Interpreter: converts and executes line by line.
• Compiler: converts the whole program into executable code at once.
• Trace: predicting results by stepping through code.
• Readability: how easily a human can read source code.
• Ease: how simple writing the program feels.

Common misconceptions

• "Programming is only for geniuses." Programming is a craft improved through practice like any other.
• "Interpreters and compilers never differ." They behave fundamentally differently in error reporting.
• "Every language runs identically under the hood." Low-level and high-level languages map differently to machine code.

Teacher activities

1. Starter: run a PRINT statement and display the result without revealing the code.
2. Name programming concepts and demonstrate writing a simple program.
3. Explain why high-level languages suit school teaching on readability.
4. Describe interpreter versus compiler behaviour on a live system.
5. Trace a simple program line by line and predict the output.
6. Close with the readability comparison and exit question.

Student activities

1. Guess the PRINT command from the starter RUN.
2. Write a simple program using variables, arithmetic and PRINT.
3. Explain why high-level languages suit school teaching in one paragraph.
4. Describe interpreter versus compiler behaviour briefly.
5. Trace a simple program and write the predicted output.
6. Compare high-level and assembly languages on readability.
7. Answer the exit question in one sentence about why high-level suits schools.

Practical / learning evidence

A recorded program plus documented expected output, a traced prediction and a high-level versus assembly comparison. Submit all three for marking.

Resources and preparation

A computer with a BASIC interpreter installed, blank windows and sample tracing cards. Keep the interpreter in a read-only folder for learners lacking install capability. Disable Caps Lock before typing. Verify the computer starts reliably.

Assessment for learning

Inspect the typed program for correct variable assignment and PRINT syntax. Compare the traced output with the actual interpreter output. Ask a learner to explain why high-level languages suit schools better than assembly. Flag any learner who confuses interpreter and compiler roles.

Inclusion and access

Prebuild the interpreter folder with Welcome and sample programs. Provide a tracing template with output lines preprinted. Extend confident learners with two tracing tasks and a second readability comparison. Homework: write a second program differing only in operators and compare the outputs.