Lesson Notes By Weeks and Term v4 - SHS 1
ENGINEERING DESIGN
Download the Lessonotes Mobile Ghana app for faster lesson access on Android and iPhone.
ENGINEERING DESIGN
Download the Lessonotes Mobile Ghana app for faster lesson access on Android and iPhone.
Subject: Engineering
Class: SHS 1
Term: 2nd Term
Week: 8
Grade code: 1.3.1.LI.2
Strand code: 3
Sub-strand code: 1
Content standard code: 1.3.1.CS.1
Indicator code: 1.3.1.LI.2
Theme: SYSTEMS DESIGN AND PROTOTYPING
Subtheme: ENGINEERING DESIGN
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 introduces the foundational step in all engineering projects: defining and documenting solution requirements. In Ghana, we are surrounded by problems waiting for innovative solutions—from managing plastic waste in our cities to improving agricultural output in our rural communities. Before any engineer can design a bridge, build an app, or create a new farming tool, they must first clearly understand and write down exactly what the solution needs to achieve. This process of documenting requirements acts as a map, guiding the entire design and building process to ensure the final product is successful, useful, and solves the right problem.
A. What is an Engineering Problem?
An engineering problem is a situation where there is a gap between the current state (the way things are now) and a desired state (the way we want things to be). Solving the problem means creating a system, product, or process to bridge that gap. Example: Current State: Students at our school have to walk 2km to the main road to get a tro-tro after school, which is tiring and unsafe in the rain. Desired State: Students have a safe and reliable way to get to the main road. The Problem: Lack of safe and convenient transport from the school gate to the main road. B. What are Solution Requirements?
Solution requirements are specific, measurable criteria that a final design or product must meet to successfully solve the problem. They are the "rules" of the project. If the final solution doesn't meet these requirements, it is considered a failure, even if it "works" in some other way.
Think of it like giving a carpenter instructions to build a table. If you just say "build me a table," you might get anything. But if you give requirements like: "The table must be 1 meter tall, made of odum wood, strong enough to hold a 50kg bag of rice, and cost less than GHS 300," you will get exactly what you need. C. Types of Requirements