Lesson Notes By Weeks and Term v4 - SHS 3
Robots & Society
Download the Lessonotes Mobile Ghana app for faster lesson access on Android and iPhone.
Robots & Society
Download the Lessonotes Mobile Ghana app for faster lesson access on Android and iPhone.
Subject: Robotics
Class: SHS 3
Term: 1st Term
Week: 14
Grade code: 3.1.1.LI.2
Strand code: 1
Sub-strand code: 1
Content standard code: 3.1.1.CS.2
Indicator code: 3.1.1.LI.2
Theme: Principles of Robotic Systems
Subtheme: Robots & Society
This page supports the lesson note with a companion video and a short classroom-ready summary.
For class groups and homework, share this lesson page so learners also get the summary, objectives, and full lesson context.
This lesson focuses on a crucial professional skill in science and technology: communicating our ideas clearly and helping others improve theirs. In the world of robotics, building a great robot is only half the battle. We must also be able to explain how it works, what problem it solves, and why it is important. This is done through a technical report. Just as importantly, we must learn to evaluate the work of our peers and provide constructive feedback that helps them improve. In Ghana, as we look for innovative solutions to challenges in agriculture, health, and industry, the ability to clearly document and collaboratively refine our technological ideas is essential for progress.
This lesson is built on two main pillars: understanding what a technical report is, and learning how to critique one effectively. Concept 1: The Structure of a Technical Report
A technical report is a formal document that describes the process, progress, or results of a technical or scientific research project. It is structured to be clear, logical, and easy for others to understand and replicate the work. While formats can vary, a typical report for a robotics project includes these sections:
| Section | Purpose | Example (For a "Robotic Yam Mound Maker" Project) | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | | Title Page | States the project title, author(s), date, and institution. | "Design and Prototyping of an Automated Yam Mound Maker for Small-Scale Farmers in the Bono Region" | | Abstract / Summary | A brief overview (150-250 words) of the entire report: the problem, the method, the key results, and the conclusion. | "This report details a project to create a low-cost robotic yam mounder... It uses a sensor-guided plough... Results show a 50% reduction in labour time... The prototype is a viable solution..." | | Introduction | Provides background information, states the problem you are solving (the "problem statement"), and outlines the report's objectives. | "Yam farming in Ghana is labour-intensive... This project aims to reduce farmer fatigue by automating mound creation." | | Methodology / Design| Explains *exactly* what you did. What materials did you use? What was your design process? What software or code was involved? | "The chassis was built with mild steel. An Arduino Uno controls two DC motors for movement and a servo motor for the hoe. A soil moisture sensor... The control algorithm was written in C++..." | | Results / Findings | Presents the data and observations from your tests. This section should be objective, using tables, graphs, and figures. | "In 5 test runs on a 10x10m plot, the robot created an average of 25 mounds per hour. The manual average is 12 mounds per hour. (See Table 1 for battery life data)." | | Discussion | Interprets the results. What do they mean? Were there any unexpected outcomes or problems? How do your findings compare to your goals? | "The 50% efficiency gain shows the concept is successful. However, the battery life of 45 minutes is a limitation that needs to be addressed in the next design iteration." | | Conclusion & Recommendations | Summarises the key takeaways of the project and suggests the next steps. What should be done in the future? | "The robotic yam mounder successfully automates a key farming task. We recommend developing a solar-powered version and using stronger materials for the plough." | | References | Lists all sources (books, websites, articles) you cited in your report. | Citing sources for motor specifications, Arduino tutorials, or agricultural data. | Concept 2: The Art of Constructive Peer Review
Peer review is not about finding fault; it is about finding potential. Its goal is to improve the final work. Bad feedback is vague and unhelpful (e.g., "Your report is confusing"). Good feedback is Specific, Actionable, and Respectful.