SHS2 Robotics · Semester 2, Week 18

Programming Robots

Lesson notes

Learning Objectives

Indicator: 2.3.3.LI.2 - Use a series of iterations to fix the identified flaws or improve the performance of solutions.

By the end of the lesson, learners can:

  • Explain the iterative process of testing, debugging and retesting a robot program.
  • Identify at least three distinct categories of flaws (algorithmic, design and coding) in a given robot project and justify their classification.
  • Apply a systematic debugging procedure to correct errors in a robot’s code and flowchart.
  • Evaluate whether a fix has improved robot performance by re-running tests after each iteration.
  • Document each debugging iteration, recording the flaw identified, the fix applied and the outcome observed.

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.2 - Use a series of iterations to fix the identified flaws or improve the performance of solutions.
Suggested placement
Semester 2, Week 18 (Week 38 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:
- 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?
- Localize the problem until the error has been tracked and fixed
- Integrate and test the robot to see if the holistic system works.
- Repeat steps A - D until all errors are fixed.

Assessment (2.3.3.AS.2). 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