SHS2 Robotics · Semester 2 Week 17: Programming Robots

Lesson notes

Learning Objectives

Indicator: 2.3.3.LI.1 - Observe and identify flaws in an operational robot and trace them to either algorithm flaws, design flaws or coding errors.

By the end of the lesson, learners can:

Observe a non-functional or poorly performing robot and describe the difference between what it is designed to do and what it actually does.
Classify identified flaws into one of three categories: algorithm flaws, design flaws, or coding errors, with justification for each classification.
Trace a specific observed symptom (for example, a robot missing a turn) back to its root cause in the flowchart or the code.
Use a systematic debugging process: brainstorm questions, localize the problem, fix the error, and test the integrated robot.
Document findings and fixes in a structured error log that records the symptom, suspected cause, actual cause, and solution applied.

Sign in with your phone number to read the full note and download the GES plan - free.

Sign in with phone number

Curriculum details

Strand: Robot Construction and Programming (Strand 3)
Sub-strand: Programming Robots (3.3)
Content standard: 2.3.3.CS.2 - 2.3.3.CS.2 Demonstrate understanding of Program testing, debugging, verification and validation. 2.3.3.LO.2 Critically analyse and assess built robots for algorithmic, design and coding flaws.
Indicator: 2.3.3.LI.1 - Observe and identify flaws in an operational robot and trace them to either algorithm flaws, design flaws or coding errors.
Suggested placement: Semester 2, Week 17 (Week 37 of the year)
Our suggestion, laid out in curriculum order across three terms of twelve weeks. NaCCA does not fix the week, so follow your school's scheme of learning.
Curriculum reference: NaCCA curriculum document, p. 129

Exemplars (from the NaCCA curriculum)

Project-Based Learning:
- For a given non-functional robot designed and programmed to perform a known task, learners should review the codes and their corresponding flowcharts and fix identified errors. The following steps can be adopted: 1. Discuss and brainstorm on the following questions a. What is the robot used to do? b. What does it actually do? c. Are the identified errors likely algorithmic or programming flaws? d. Have you encountered these types of problems before? If yes, how did you fix it? e. Where and why do you think the errors occurred?

2. Localize the problem until the error has been tracked and fixed 3. Integrate and test the robot to see if the holistic system works. 4. Repeat steps A - D until all errors are fixed.

Assessment (2.3.3.AS.1). The document marks these depth-of-knowledge levels for this indicator: Level 4 Extended critical thinking and reasoning.

Teaching and Learning Resources:
- A computer with required programming tools
- Robots YEAR THREE
- Flipcharts
- Flowcharts
- Videos
- Online resources
- Group discussion